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

failure has been deprecated #284

Closed
tarcieri opened this issue May 2, 2020 · 3 comments · Fixed by #368
Closed

failure has been deprecated #284

tarcieri opened this issue May 2, 2020 · 3 comments · Fixed by #368

Comments

@tarcieri
Copy link
Member

tarcieri commented May 2, 2020

Discussion here:

https://internals.rust-lang.org/t/failure-crate-maintenance/12087/16?u=bascule

failure is a fairly pervasive crate and marking it as unmaintained immediately would be rather noisy.

On the discussion thread above I suggested waiting for some period of time for people to organically migrate to new crates, then filing an advisory.

Perhaps 3 months is enough time? (so August 2020)

@djc
Copy link
Contributor

djc commented Aug 27, 2020

It's the end of August. Let's do it?

Just pointed some colleagues at the deprecation, and they pointed out that it's not very obvious right now.

@tarcieri
Copy link
Member Author

Opened #368 which adds an unmaintained advisory with suggested alternatives of anyhow, eyre, snafu, and thiserror.

@tarcieri
Copy link
Member Author

Filed as RUSTSEC-2020-0036.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants