feroxbuster
feroxbuster copied to clipboard
Bump indicatif from 0.15.0 to 0.17.1
Bumps indicatif from 0.15.0 to 0.17.1.
Release notes
Sourced from indicatif's releases.
0.17.1
2.5 months after the large 0.17 release, we (finally) have a release that addresses most of the regressions found in 0.17. There is ongoing work on changes in the estimation algorithm, tracked in #394, which has regressed for some users.
Note that we made some technically semver-breaking change of adding a missing
Sync
bound to theProgressTracker
bounds (#471). We're assuming that most users don't (yet) have customProgressTracker
impls, and that users who do have probably built one that isSync
anyway.Fixed regressions
- Fixed
unicode-width
feature spelling (#456)- Only tick if the ticker is disabled (#458)
- Rework
MultiProgress
zombie line handling (#460)- Fix incorrect link in documentation (#469, thanks to
@Jedsek
)- Take a reference for
ProgressBar::style()
(#476, thanks to@andrewchambers
)Other changes
- Add
HumanFloatCount
formatting option (#453, thanks to@jqnatividad
)- Add
Sync
bound toProgressTracker
(#471)- Update ProgressDrawTarget documentation (#472, thanks to
@AronParker
)- Correct mis-naming of variables in wrap_async_read (#473, thanks to
@octylFractal
)- Remove
write_all()
impl fromProgressBarIter
'sWrite
impl (#478, thanks to@hexagonal-sun
)- Document last char/string in tick style being the "final" state (#479, thanks to
@MarijnS95
)Thanks from
@djc
and@chris-laplante
to all contributors!0.17.0
indicatif is one of the most popular terminal progress bar libraries in the Rust ecosystem. More than a year after the 0.16.0 release, we're happy to finally release 0.17. In the past year, the indicatif team has grown to two maintainers, since
@chris-laplante
joined@djc
as a maintainer. We also now have a Discord channel.Apart from many small API additions and fixes, particular effort has gone into reducing the overhead for reporting progress. To this end, we've removed some of the explicit rate limiting APIs in favor of a single refresh rate in the
ProgressDrawTarget
. We now set a rate limit by default (50ms) that should drastically reduce overhead for most applications while being more than enough for most terminal applications. Additionally, position updates are now synchronized by using atomic integer APIs instead of a mutex. In a basic test the simplest possible progress bar is about 95x faster on 0.17.0 compared to 0.16.2.We've made many changes to the way
MultiProgress
collections work. You no longer need to explicitlyjoin()
theMultiProgress
, there are more ways to insert new progress bars into the collection, and many correctness improvements have been made, in part to more effort having gone into testing the crate.Additionally, we've reduced our dependency footprint, removing lazy_static and regex from our required dependencies.
Additions
- Add ability to add custom template keys (#301, thanks to
@redzic
)- Allow custom template keys to maintain state (#420, thanks to
@1Dragoon
)- Add
HumanCount
and template keys to print more humane position/length (#340, thanks to@dabreegster
)- Remove extra new line after progress bar (#338 with fixes in #343, #350 and #356, thanks to
@sigmaSd
)- Implement
ProgressBar::suspend()
(#333, thanks to@ishitatsuyuki
)- Add
ProgressIterator::progress_with_style()
(#306, thanks to@LeCyberDucky
)- Pass through
stream_position()
inProgressBarIter
(#309, thanks to@rlee287
)- Add
AsyncRead
/AsyncWrite
support forProgressBar
(#308, thanks to@x0f5c3
)- Add
AsyncBufRead
implementation forProgressBarIterator
(#315, thanks to@x0f5c3
)- Add builder methods for
ProgressBarIter
(#337, thanks to@chubei-oppen
)- Allow overriding
ProgressBar
elapsed time (#325, thanks to@zhaofengli
)- Add a space between numbers and their units (#345, thanks to
@firasuke
)- Add
ProgressBar::style()
to enable access to the current style (#396, thanks to@andrewchambers
)- Account for alignment when truncating (#402)
... (truncated)
Commits
791068c
Bump version to 0.17.1b65eb85
add new render tests that exercise zombie handlingd88fa2d
modify render tests to account for fixed MultiProgress::println/clear behaviord32eed5
rewrite zombie handlingbdf1890
clarify comment for MultiState::orphan_lines memberefc8558
No-op MultiState::draw if we are panickingb9dcd47
Document last char/string in tick style being the "final" statea466096
Removewrite_all
from wrap_write81cca1e
ProgressBar style() now takes a referenceb5de18c
Correct mis-naming of variables in wrap_async_read- Additional commits viewable in compare view
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase
.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
-
@dependabot rebase
will rebase this PR -
@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it -
@dependabot merge
will merge this PR after your CI passes on it -
@dependabot squash and merge
will squash and merge this PR after your CI passes on it -
@dependabot cancel merge
will cancel a previously requested merge and block automerging -
@dependabot reopen
will reopen this PR if it is closed -
@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually -
@dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) -
@dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) -
@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)