Skip to content

Releases: Byron/prodash

v20.2.0

20 Sep 05:33
f49f470
Compare
Choose a tag to compare

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 to counter(), 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

view details
  • Uncategorized
    • don't reset the shared counter value on init. (414bc71)
    • Add Progress::set_max() to set the highgest expected progress value. (4904065)
    • make more explicit what is cloned (without altering actual behaviour) (b023efd)

v20.1.1

20 Sep 03:17
d152701
Compare
Choose a tag to compare

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)

v20.1.0

20 Sep 01:44
6591872
Compare
Choose a tag to compare

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

view details
  • Uncategorized
    • fix compile warnings for some configurations (fe0ac06)
    • thanks clippy (deb7791)
    • Progress::counter() returns a shared step counter. (08be317)

v20.0.1

15 Sep 01:32
b98595b
Compare
Choose a tag to compare

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

view details
  • #12
    • Allow builds to succeed on Windows by not registering SIGWINCH signal. (80a4850)
    • only register SIGWINCH signal on unix (5de765b)
    • Adjust CI configuration to catch more cross-platform errors (b7e0f2c)
  • Uncategorized
    • Do away with unsafe code by using safe wrappers instead. (447aa0f)

v20.0.0

12 Sep 02:26
54e0a6a
Compare
Choose a tag to compare

New Features

  • line renderer adjusts when resizing the terminal.

Chore (BREAKING)

  • upgrade dependencies to tui 0.19 and crossterm 0.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

view details
  • Uncategorized
    • line renderer adjusts when resizing the terminal. (bab2ea0)
    • upgrade dependencies to tui 0.19 and crossterm 0.25 (a3b2678)

v19.0.1

20 Mar 11:34
a0c88b7
Compare
Choose a tag to compare

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

view details
  • Uncategorized
    • line renderer will clear previous lines if progress is lost (dbca35f)
    • fix benchmark compilation (39bc237)

v19.0.0

20 Mar 10:02
fda577e
Compare
Choose a tag to compare

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

view details
  • Uncategorized
    • Improve render-log performance greatly. (cba841c)
    • Allow rendererers to respond to dropped progress roots (b6d5245)
    • Actually, the correct dashmap version is 5.1 (6bdb7e8)

v18.0.2

07 Feb 01:13
69f4295
Compare
Choose a tag to compare

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

01 Feb 06:33
e9769dd
Compare
Choose a tag to compare

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

23 Jan 02:11
10531ae
Compare
Choose a tag to compare

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

Commit Details

view details
  • Uncategorized