-
Notifications
You must be signed in to change notification settings - Fork 13.1k
New issue
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
flock creates executable file #102531
Labels
C-bug
Category: This is a bug.
Comments
Dylan-DPC
added a commit
to Dylan-DPC/rust
that referenced
this issue
Oct 15, 2022
Remove "execute" bit from lock file permissions Previously, flock would set the "execute" bit on Rust lock files. That makes no sense. This patch clears the "execute" bit on Rust lock files. See issue rust-lang#102531.
bors
added a commit
to rust-lang-ci/rust
that referenced
this issue
Oct 18, 2022
Remove "execute" bit from lock file permissions Previously, flock would set the "execute" bit on Rust lock files. That makes no sense. This patch clears the "execute" bit on Rust lock files. See issue rust-lang#102531.
This seems to be fixed on latest nightly, so this issue can be closed |
Aaron1011
pushed a commit
to Aaron1011/rust
that referenced
this issue
Jan 6, 2023
Remove "execute" bit from lock file permissions Previously, flock would set the "execute" bit on Rust lock files. That makes no sense. This patch clears the "execute" bit on Rust lock files. See issue rust-lang#102531.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I tried this:
I expected to see this happen: The only regular files with executable bit inside
target/
are the actual ELF executables.Instead, this happened: The lock files for the incremental build also have the executable bit set (for example
./target/debug/incremental/ex1-zjfb4s71is3b/s-ge02ugy8lg-ga9xze.lock
in acargo new
ed example).Meta
cargo 1.63.0-nightly (3f052d8ee 2022-05-12)
Same in current rust HEAD commit.
rustc --version --verbose
:The text was updated successfully, but these errors were encountered: