-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
chore(deps): Patch dependencies to remove dependency on time
v0.1
#9678
Conversation
Which is vulnerable to `RUSTSEC-2020-0071`. `chrono` seems to be no longer maintained so #9675 will be the real solution for that. The other dependencies should be able to be unpatched once they have a release removing the dependency. Signed-off-by: Jesse Szwedko <[email protected]>
✔️ Deploy Preview for vector-project canceled. 🔨 Explore the source changes: 2589cc9 🔍 Inspect the deploy log: https://app.netlify.com/sites/vector-project/deploys/61b1100c67467b000780bcf8 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Neat! Much smaller than I figured.
Since they merged in the `time` upgarde Signed-off-by: Jesse Szwedko <[email protected]>
Signed-off-by: Jesse Szwedko <[email protected]>
Soak Test ResultsBaseline: 96128a0 ExplanationA soak test is an integrated performance test for vector in a repeatable rig, with varying configuration for vector. What follows is a statistical summary of a brief vector run for each configuration across SHAs given above. The goal of these tests are to determine, quickly, if vector performance is changed and to what degree by a pull request. Test units below are bytes/second/CPU, except for 'skewness'. The further 'skewness' is from 0.0 the more indication that vector lacks consistency in behavior, making predictions of fitness in the field challenging.No statistically interesting changes with confidence 90.00%. Fine details of change detection per experiment.
Fine details of each soak run.
|
Which is vulnerable to
RUSTSEC-2020-0071
.chrono
seems to be no longer maintained so#9675 will be the real
solution for that.
The other dependencies should be able to be unpatched once they have
a release removing the dependency.