We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
While working on reproducible builds for openSUSE, I found that our python-ruff package varies from Address-Space-Layout-Randomization (ASLR).
python-ruff
I reproduced this with both 0.5.0 and 0.4.10.
It is a variation that happens with low-entropy - maybe just 1 bit, so occasionally, two identical ruff binaries are produced.
ruff
I uploaded two 0.5.0 binaries and a diff into http://rb.zq1.de/other/python-ruff/ - maybe something related to rust/llvm.
The text was updated successfully, but these errors were encountered:
Scanning through the diff, it seems that most (all?) are related to the libCST dependency.
libCST
Maybe a non-determinism in their macro?
Sorry, something went wrong.
grep ^- ruff-strings-diff.txt | grep -vi libcst also shows
grep ^- ruff-strings-diff.txt | grep -vi libcst
-anon.ea5251168591221b31fa999991ef59a1.39.llvm.6396498261944353430 -_ZN60_$LT$alloc..string..String$u20$as$u20$core..fmt..Display$GT$3fmt17hb6d27bec17dc24a4E.llvm.1673184941240675199
There is indeed an issue with rust/llvm LTO in libCST Instagram/LibCST#1213 - but not sure if this is the only issue here.
No branches or pull requests
While working on reproducible builds for openSUSE, I found that
our
python-ruff
package varies from Address-Space-Layout-Randomization (ASLR).I reproduced this with both 0.5.0 and 0.4.10.
It is a variation that happens with low-entropy - maybe just 1 bit, so occasionally, two identical
ruff
binaries are produced.I uploaded two 0.5.0 binaries and a diff into http://rb.zq1.de/other/python-ruff/ - maybe something related to rust/llvm.
The text was updated successfully, but these errors were encountered: