You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We override the cssparser crate, which is a dependency of some of our rust code, to use a forked version working around a linkage issue with glibc. This makes maintenance harder. We should migrate to the published upstream version, or if that remains infeasible, move to a fork under the brave organization and set up a better audit/update process for it.
source = "registry+https://github.com/rust-lang/crates.io-index" or at least something like source = "git+https://github.com/brave/rust-cssparser?branch=glibc#ad2f4d3c89e247ec1693a581ecace199e46f30fa".
Reproduces how often:
Always
Desktop Brave version:
1.35.27
Android Device details:
Install type (ARM, x86):
Device type (Phone, Tablet, Phablet):
Android version:
Version/Channel Information:
Can you reproduce this issue with the current release? yes
Can you reproduce this issue with the beta channel? yes
Can you reproduce this issue with the nightly channel? yes
Other Additional Information:
Does the issue resolve itself when disabling Brave Shields?
Does the issue resolve itself when disabling Brave Rewards?
Is the issue reproducible on the latest version of Chrome?
Miscellaneous Information:
The text was updated successfully, but these errors were encountered:
We were patching the rust cssparser crate to work around an issue
with `f64::powf` linking to symbols from the system glibc which
couldn't be satisfied by the sysroot the official builds link
against.
This has since been addressed by having cargo target the same
sysroot, I think by #6408,
so we can remove the diversion and use the upstream crate which
lets us update more easily and benefit from shared audits.
Resolvesbrave/brave-browser#20080
We were patching the rust cssparser crate to work around an issue
with `f64::powf` linking to symbols from the system glibc which
couldn't be satisfied by the sysroot the official builds link
against.
This has since been addressed by having cargo target the same
sysroot, I think by #6408,
so we can remove the diversion and use the upstream crate which
lets us update more easily and benefit from shared audits.
Resolvesbrave/brave-browser#20080
Description
We override the
cssparser
crate, which is a dependency of some of our rust code, to use a forked version working around a linkage issue with glibc. This makes maintenance harder. We should migrate to the published upstream version, or if that remains infeasible, move to a fork under the brave organization and set up a better audit/update process for it.Steps to Reproduce
$ grep git+http src/brave/build/rust/Cargo.lock
source
lines pointing to a personal repo.Actual result:
source = "git+https://github.com/AndriusA/rust-cssparser?branch=glibc#ad2f4d3c89e247ec1693a581ecace199e46f30fa"
Expected result:
source = "registry+https://github.com/rust-lang/crates.io-index"
or at least something likesource = "git+https://github.com/brave/rust-cssparser?branch=glibc#ad2f4d3c89e247ec1693a581ecace199e46f30fa"
.Reproduces how often:
Always
Desktop Brave version:
1.35.27
Android Device details:
Version/Channel Information:
Other Additional Information:
Miscellaneous Information:
The text was updated successfully, but these errors were encountered: