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

view details

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

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

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

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

Commit Details

view details

• Uncategorized
  • prepare changelog (a7a58c0)
  • upgrade to tui 0.17 (482b54f)

v17.0.0

New Features (BREAKING)

• Add MessageLevel parameter to Progress::show_throughput_with(…, level)
  This allows to use message level for highlighting of certain
  throughputs and results.

Commit Statistics

• 1 commit contributed to the release.
• 1 commit where understood as conventional.
• 0 issues like '(#ID)' where seen in commit messages

Commit Details

view details

• Uncategorized
  • Add MessageLevel parameter to Progress::show_throughput_with(…, level) (46214a3)

v16.1.3

Bug Fixes

• Progress::init(None, None) now resets the progress entirely

Commit Statistics

• 1 commit contributed to the release.
• 1 commit where understood as conventional.
• 0 issues like '(#ID)' where seen in commit messages

Commit Details

view details

• Uncategorized
  • Progress::init(None, None) now resets the progress entirely (2fe3eeb)

v16.1.2

Bug Fixes

• reset the shared value on init to avoid keeping the previously set value.

Commit Statistics

• 1 commit contributed to the release.
• 1 commit where understood as conventional.
• 0 issues like '(#ID)' where seen in commit messages

Commit Details

view details

• Uncategorized
  • reset the shared value on init to avoid keeping the previously set value. (aa70a27)

v16.1.1

Bug Fixes

• correct signature of new 'running()' method

Commit Statistics

• 1 commit contributed to the release.
• 1 commit where understood as conventional.
• 0 issues like '(#ID)' where seen in commit messages

Commit Details

view details

• Uncategorized
  • correct signature of new 'running()' method (ca5f544)

v16.1.0

New Features

• Setting the progress value is now 9x faster
  This is accomplished at the cost of not autoamtically setting the
  progress to 'running' anymore when the progress is set.

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
  • Setting the progress value is now 9x faster (3886754)
  • An experiment to show we don't want to rely on dashmap for this (4f527c1)