Skip to content
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

build(deps): update moka requirement from 0.11.2 to 0.12.3 #647

Closed
wants to merge 1 commit into from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jan 15, 2024

Updates the requirements on moka to permit the latest version.

Changelog

Sourced from moka's changelog.

Version 0.12.3

Added

  • Added the upsert and compute methods for modifying a cached entry (#370[gh-pull-0370]):
    • Now the entry or entry_by_ref APIs have the following methods:
      • and_upsert_with method to insert or update the entry.
      • and_compute_with method to insert, update, remove or do nothing on the entry.
      • and_try_compute_with method, which is similar to above but returns Result.

Fixed

  • Raised the version requirement of the quanta from >=0.11.0, <0.12.0 to >=0.12.2, <0.13.0 to avoid under-measuring the elapsed time on Apple silicon Macs (#376[gh-pull-0376]).
    • Due to this under-measurement, cached entries expire sightly later than expected on macOS arm64.

Version 0.12.2

Fixed

  • Prevent timing issues in writes that cause inconsistencies between the cache's internal data structures (#348[gh-pull-0348]):
    • One way to trigger the issue is that insert the same key twice quickly, once when the cache is full and a second time when there is a room in the cache.
      • When it occurs, the cache will not return the value inserted in the second call (which is wrong), and the entry_count method will keep returning a non zero value after calling the invalidate_all method (which is also wrong).
  • Now the last access time of a cached entry is updated immediately after the entry is read (#363[gh-pull-0363]):
    • When the time-to-idle of a cache is set, the last access time of a cached entry is used to determine if the entry has been expired.
    • Before this fix, the access time was updated (to the time when it was read) when pending tasks were processed. This delay caused issue that some entries become temporarily unavailable for reads even though they have been accessed recently. And then they will become available again after the pending tasks are processed.
    • Now the last access time is updated immediately after the entry is read. The entry will remain valid until the time-to-idle has elapsed.

Note that both of #348[gh-pull-0348] and #363[gh-pull-0363] were already present in v0.11.x and older versions. However they were less likely to occur because they had background threads to periodically process pending tasks. So there were much shorter time windows for these issues to occur.

... (truncated)

Commits
  • 9303de3 Merge pull request #376 from moka-rs/quanta-v0.12.2
  • 3c2e280 Update the change log
  • 087cf69 Raise the minimum version of the quanta to v0.12.2
  • 94a3558 Merge pull request #375 from moka-rs/ensure-waiter-map-is-empty-after-test
  • a5d0674 Compute API - Update the tests to ensure the internal waiter map
  • cc36d72 Merge pull request #370 from moka-rs/compute-api
  • 472addc Compute API - Brush up the documents
  • aee7ebe Compute API - Change the return type of the entry and_compute_with and
  • 6eff2d3 Compute API - Change the compute family methods to record a read
  • 3db436f Bump the version to v0.12.3
  • 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @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)

Updates the requirements on [moka](https://github.com/moka-rs/moka) to permit the latest version.
- [Changelog](https://github.com/moka-rs/moka/blob/main/CHANGELOG.md)
- [Commits](moka-rs/moka@v0.11.2...v0.12.3)

---
updated-dependencies:
- dependency-name: moka
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file rust Pull requests that update Rust code labels Jan 15, 2024
Copy link
Contributor Author

dependabot bot commented on behalf of github Jan 22, 2024

Superseded by #650.

@dependabot dependabot bot closed this Jan 22, 2024
@dependabot dependabot bot deleted the dependabot/cargo/moka-0.12.3 branch January 22, 2024 15:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file rust Pull requests that update Rust code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants