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
Remove atty dependency #33
Labels
internal-improvement
Refactoring, performance improvement, or other non-breaking change
Comments
anwarmamat
added
bug
Something isn't working
pending-review
Awaiting review by the core team
labels
May 22, 2023
For reference bheisler/criterion.rs#628 updated the dependency in criterion. Comments by a maintainer at the end of that thread indicate that we can expect a release on a reasonable timeline. |
john-h-kastner-aws
added a commit
that referenced
this issue
May 30, 2023
This removes the dependency on `atty` fixing #33.
john-h-kastner-aws
added a commit
that referenced
this issue
May 30, 2023
khieta
added
internal-improvement
Refactoring, performance improvement, or other non-breaking change
and removed
pending-review
Awaiting review by the core team
labels
Jun 6, 2023
john-h-kastner-aws
added a commit
that referenced
this issue
Jul 25, 2023
cdisselkoen
pushed a commit
that referenced
this issue
Aug 11, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Before opening, please confirm:
Bug Category
Other
Describe the bug
Our (transitive, through criterion) atty dependency is outdated. The version used has a security vulnerability. We aren't exposed to it but once a new version of criterion is released we should upgrade so we don't have the transitive atty dependency.
Expected behavior
No response
Reproduction steps
No response
Code Snippet
No response
Log output
No response
Additional configuration
No response
Operating System
No response
Additional information and screenshots
No response
The text was updated successfully, but these errors were encountered: