Skip to content
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

fix: update MSRV to 1.78 to solve tv_nsec related panics #1342

Merged
merged 3 commits into from
Jan 23, 2025
Merged

Conversation

cafkafk
Copy link
Member

@cafkafk cafkafk commented Jan 23, 2025

This updated the rust MSRV to resolve a bug in the actual upstream rust
implementation that has been affecting eza for a while.

This obviously means new eza releases won't be available on all
distributions, but those distributions should move to a new version of
rust then, since this bug seems to indicate that there is an important
issue here.

Closes: #735

Refs: #666 rust-lang/rust@e69f14b

Signed-off-by: Christina Sørensen ces@fem.gg

@daviessm
Copy link
Contributor

Looks like the Windows automations aren't happy but I don't have a Windows PC to check them out any more, sorry!

@cafkafk
Copy link
Member Author

cafkafk commented Jan 23, 2025

Looks like the Windows automations aren't happy but I don't have a Windows PC to check them out any more, sorry!

Dw I'm on it :p

cafkafk added a commit that referenced this pull request Jan 23, 2025
Apparently, upstream rust decided to change the behavior of dead/unused
code detection in a way that causes a lot of false positives.

For some (yet known) reason, this only hit on the windows build, but
I've confirmed that these are indeed false positives, and removing this
"dead code" breaks the build.

Frustratingly, we only hit this to fix *another issue*[1] with upstream
rust... And this litters our code with directives where we "allow
unused" that isn't unused.

I coindicentally also saw this at dayjob today[2], and yes, this is
real, so we'll just have to do it.

Refs: [1] rust-lang/rust@e69f14b
Refs: [2] DBCDK/faythe#101
Refs: rust-lang/rust#88900
Refs: #1342

Signed-off-by: Christina Sørensen <ces@fem.gg>
This updated the rust MSRV to resolve a bug in the actual upstream rust
implementation that has been affecting eza for a while.

This obviously means new eza releases won't be available on all
distributions, but those distributions should move to a new version of
rust then, since this bug seems to indicate that there is an important
issue here.

Closes: #735
Refs: #666 rust-lang/rust@e69f14b

Signed-off-by: Christina Sørensen <ces@fem.gg>
Apparently, upstream rust decided to change the behavior of dead/unused
code detection in a way that causes a lot of false positives.

For some (yet known) reason, this only hit on the windows build, but
I've confirmed that these are indeed false positives, and removing this
"dead code" breaks the build.

Frustratingly, we only hit this to fix *another issue*[1] with upstream
rust... And this litters our code with directives where we "allow
unused" that isn't unused.

I coindicentally also saw this at dayjob today[2], and yes, this is
real, so we'll just have to do it.

Refs: [1] rust-lang/rust@e69f14b
Refs: [2] DBCDK/faythe#101
Refs: rust-lang/rust#88900
Refs: #1342

Signed-off-by: Christina Sørensen <ces@fem.gg>
@cafkafk
Copy link
Member Author

cafkafk commented Jan 23, 2025

I'll add the commit message here for visibility

Apparently, upstream rust decided to change the behavior of dead/unused
code detection in a way that causes a lot of false positives.

For some (yet known) reason, this only hit on the windows build, but
I've confirmed that these are indeed false positives, and removing this
"dead code" breaks the build.

Frustratingly, we only hit this to fix *another issue*[1] with upstream
rust... And this litters our code with directives where we "allow
unused" that isn't unused.

I coindicentally also saw this at dayjob today[2], and yes, this is
real, so we'll just have to do it.

@cafkafk cafkafk marked this pull request as ready for review January 23, 2025 15:07
For detailed explanation of this issue see d6ee81b

Refs: d6ee81b

Signed-off-by: Christina Sørensen <ces@fem.gg>
@cafkafk cafkafk changed the title fix: update MSRV to 1.78 to solve rust malfunction fix: update MSRV to 1.78 to solve tv_nsec related panics Jan 23, 2025
@cafkafk cafkafk merged commit 21d6024 into main Jan 23, 2025
26 checks passed
cafkafk added a commit that referenced this pull request Jan 23, 2025
Apparently, upstream rust decided to change the behavior of dead/unused
code detection in a way that causes a lot of false positives.

For some (yet known) reason, this only hit on the windows build, but
I've confirmed that these are indeed false positives, and removing this
"dead code" breaks the build.

Frustratingly, we only hit this to fix *another issue*[1] with upstream
rust... And this litters our code with directives where we "allow
unused" that isn't unused.

I coindicentally also saw this at dayjob today[2], and yes, this is
real, so we'll just have to do it.

Refs: [1] rust-lang/rust@e69f14b
Refs: [2] DBCDK/faythe#101
Refs: rust-lang/rust#88900
Refs: #1342

Signed-off-by: Christina Sørensen <ces@fem.gg>
@cafkafk cafkafk deleted the issue-735 branch January 23, 2025 15:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: ✅ Done
2 participants