Releases: Byron/prodash
v20.2.0
New Features
- Add
Progress::set_max()
to set the highgest expected progress value.
Bug Fixes
- don't reset the shared counter value on
init
.
It's possible to re-initialize the progress, and when that's done
it would detach the counter from previous instances that might have
been observed by callers tocounter()
, which is surprising.
Commit Statistics
- 3 commits contributed to the release.
- 2 commits were understood as conventional.
- 0 issues like '(#ID)' where seen in commit messages
Commit Details
v20.1.1
Bug Fixes
- implement
Progress::counter()
for all utility types.
This was forgotten previously as there was a default implementation
right from the start.
Commit Statistics
- 1 commit contributed to the release.
- 1 commit was understood as conventional.
- 0 issues like '(#ID)' where seen in commit messages
Commit Details
view details
- Uncategorized
- implement
Progress::counter()
for all utility types. (a0e7da7)
- implement
v20.1.0
New Features
Progress::counter()
returns a shared step counter.
This is useful if multiple threads want to access the same progress, without the need
for provide each their own progress and aggregating the result.
Commit Statistics
- 3 commits contributed to the release.
- 5 days passed between releases.
- 1 commit was understood as conventional.
- 0 issues like '(#ID)' where seen in commit messages
Thanks Clippy
Clippy helped 1 time to make code idiomatic.
Commit Details
v20.0.1
Bug Fixes
- Allow builds to succeed on Windows by not registering SIGWINCH signal.
Without said signal, the render line will not automatically resize
anymore, which in theory can be compensated for by re-obtaining
the terminal dimensions every now and then (currently not done).
Commit Statistics
- 4 commits contributed to the release.
- 2 days passed between releases.
- 1 commit was understood as conventional.
- 1 unique issue was worked on: #12
Commit Details
v20.0.0
New Features
- line renderer adjusts when resizing the terminal.
Chore (BREAKING)
- upgrade dependencies to tui
0.19
and crossterm0.25
Commit Statistics
- 2 commits contributed to the release.
- 175 days passed between releases.
- 2 commits were understood as conventional.
- 0 issues like '(#ID)' where seen in commit messages
Commit Details
v19.0.1
Bug Fixes
- line renderer will clear previous lines if progress is lost
Previously it would just exit its main loop and leave lines on screen.
Commit Statistics
- 2 commits contributed to the release.
- 1 commit where understood as conventional.
- 0 issues like '(#ID)' where seen in commit messages
Commit Details
v19.0.0
New Features
-
Improve render-log performance greatly.
Previously it would check the current time each time somebody
wants to log on any logger, greatly reducing performance as
it would block on the mutex rust-std uses internally.Now we use a single thread to provide information about whether or not
we may log, whose lifetime is bound to all of the log instances it
governs.
New Features (BREAKING)
-
Allow rendererers to respond to dropped progress roots
Previously it needed extra effort to communicate that a the computation
was done and the renderer should stop rendering progress.Now they only obtain a weak progress instance so it can drop if the
computation is done, terminating it naturally and in time.Note that in case of the TUI, it would still be needed to respond
to the GUI having shut down due to user request.
Commit Statistics
- 3 commits contributed to the release over the course of 41 calendar days.
- 41 days passed between releases.
- 2 commits where understood as conventional.
- 0 issues like '(#ID)' where seen in commit messages
Commit Details
v18.0.2
Chore
- Upgrade dashmap to 5.0.1 (with security fix)
Commit Statistics
- 1 commit contributed to the release.
- 5 days passed between releases.
- 1 commit where understood as conventional.
- 0 issues like '(#ID)' where seen in commit messages
Commit Details
view details
- Uncategorized
- Upgrade dashmap to 5.0.1 (with security fix) (e4f2ab8)
v18.0.1
Bug Fixes
-
Downgrade to dashmap 4.0
While waiting for unoundness to be resolved.See the issue for details: xacrimon/dashmap#167
Commit Statistics
- 1 commit contributed to the release.
- 9 days passed between releases.
- 1 commit where understood as conventional.
- 0 issues like '(#ID)' where seen in commit messages
Commit Details
view details
- Uncategorized
- Downgrade to dashmap 4.0 (a1f8aa6)
v18.0.0
New Features (BREAKING)
- upgrade to tui 0.17
Commit Statistics
- 2 commits contributed to the release.
- 19 days passed between releases.
- 1 commit where understood as conventional.
- 0 issues like '(#ID)' where seen in commit messages