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.

Sign up for GitHub

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

Jump to bottom

RUSTSEC-2020-0036: failure is officially deprecated/unmaintained #1014

Closed
github-actions bot opened this issue Aug 28, 2020 · 5 comments
Closed

RUSTSEC-2020-0036: failure is officially deprecated/unmaintained #1014

github-actions bot opened this issue Aug 28, 2020 · 5 comments
Labels
C-technical-debt Category: This makes the code harder to read and modify, but has no impact on end users E-medium Effort: This requires a fair amount of work P-low Low priority issues S-blocked Status: marked as blocked ❌ on something else such as an RFC or other implementation work.

Comments

@github-actions
Copy link

failure is officially deprecated/unmaintained

Details
Status unmaintained
Package failure
Version 0.1.8
URL rust-lang-deprecated/failure#347
Date 2020-05-02

The failure crate is officially end-of-life: it has been marked as deprecated
by the former maintainer, who has announced that there will be no updates or
maintenance work on it going forward.

The following are some suggested actively developed alternatives to switch to:

See advisory page for additional details.
@jyn514
Copy link
Member

jyn514 commented Aug 28, 2020

I'm surprised it took this long to open an issue 😆

@jyn514 jyn514 added C-technical-debt Category: This makes the code harder to read and modify, but has no impact on end users E-hard Effort: This will require a lot of work P-low Low priority issues labels Aug 28, 2020
@Nemo157
Copy link
Member

Nemo157 commented Aug 28, 2020 •
edited
Loading

I have a commit switching over to anyhow from a while ago.

IIRC the blocker is waiting on Error::backtrace to stabilize because anyhow does not provide any way to polyfill it with the backtrace crate when not available (rust-lang/rust#53487).

@jyn514
Copy link
Member

jyn514 commented Aug 28, 2020

That sounds good to me, I would really hate to lose backtraces.

@jyn514 jyn514 added S-blocked Status: marked as blocked ❌ on something else such as an RFC or other implementation work. E-medium Effort: This requires a fair amount of work and removed E-hard Effort: This will require a lot of work labels Aug 28, 2020
@Stupremee
Copy link
Member

Stupremee commented Sep 25, 2020 •
edited
Loading

snafu also provides backtraces using the backtrace crate

@syphar
Copy link
Member

syphar commented Oct 21, 2024

fixed in rust-lang/rustwide#76 and #2538

@syphar syphar closed this as completed Oct 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
C-technical-debt Category: This makes the code harder to read and modify, but has no impact on end users E-medium Effort: This requires a fair amount of work P-low Low priority issues S-blocked Status: marked as blocked ❌ on something else such as an RFC or other implementation work.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@Nemo157 @syphar @jyn514 @Stupremee