rosa/waifu-calendar
Watch
1
0
Fork
You've already forked waifu-calendar
 0
Code Issues 1 Pull requests Projects Releases Packages Wiki Activity Actions

chore(deps): update rust crate moka to v0.12.16 #19

Merged
rosa merged 1 commit from renovate/moka-0.x-lockfile into main 2026-08-20 14:29:56 +00:00
Conversation 1 Commits 1 Files changed 1 +2 -2
rosa commented 2026-08-17 04:07:43 +00:00
Owner
Copy link

This PR contains the following updates:

Package Type Update Change
moka dependencies patch 0.12.15 → 0.12.16

Release Notes

moka-rs/moka (moka)

v0.12.16

Compare Source

Fixed
  • Fixed a bug where cache eviction could stall permanently when the cache was
    configured with the non-default LRU eviction policy (EvictionPolicy::lru())
    by a race between insert and remove operations on the same key
    ([#​592][gh-pull-0592] by [@​kim-jhyeon][gh-kim-jhyeon], reported in
    [#​590][gh-issue-0590]):
    • This bug was introduced in v0.12.0 and affected sync::Cache,
      sync::SegmentedCache and future::Cache.
    • A race between applying a write recording for an entry and concurrently
      removing that entry from the internal concurrent hash table could leave an
      orphaned node at the front of the LRU queue. Once present, no entry was ever
      evicted again and the cache grew unboundedly past max_capacity.
    • The same race also affected the default TinyLFU eviction policy, but with
      a milder symptom: each occurrence permanently leaked one phantom entry
      slot, causing entry_count and weighted_size to over-report and the
      usable capacity to shrink by one entry per occurrence. Fixed by the same
      change.
Changed
  • Worked around a ThreadSanitizer false positive ([#​602][gh-pull-0602]):
    • Replaced the standalone fence(Acquire) in the internal MiniArc's drop
      path with an Acquire load of the reference count, so that downstream
      projects can now run ThreadSanitizer on code using Moka without hitting
      this false positive.
    • std::sync::Arc has a similar workaround.
  • Raised the minimum version of the crossbeam-epoch crate from v0.9.18 to
    v0.9.20 to avoid the following advisory ([#​603][gh-pull-0603]):
    • [RUSTSEC-2026-0204] crossbeam-epoch: invalid pointer dereference in
      fmt::Pointer for Atomic and Shared
    • Moka is not affected by this advisory because it never formats these
      pointer types. However, raising the minimum version prevents downstream
      lockfiles from resolving to an affected crossbeam-epoch version via
      Moka.

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate.

This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [moka](https://github.com/moka-rs/moka) | dependencies | patch | `0.12.15` → `0.12.16` | --- ### Release Notes <details> <summary>moka-rs/moka (moka)</summary> ### [`v0.12.16`](https://github.com/moka-rs/moka/blob/HEAD/CHANGELOG.md#Version-01216) [Compare Source](https://github.com/moka-rs/moka/compare/v0.12.15...v0.12.16) ##### Fixed - Fixed a bug where cache eviction could stall permanently when the cache was configured with the **non-default** LRU eviction policy (`EvictionPolicy::lru()`) by a race between insert and remove operations on the same key (\[[#&#8203;592](https://github.com/moka-rs/moka/issues/592)]\[gh-pull-0592] by \[[@&#8203;kim-jhyeon](https://github.com/kim-jhyeon)]\[gh-kim-jhyeon], reported in \[[#&#8203;590](https://github.com/moka-rs/moka/issues/590)]\[gh-issue-0590]): - This bug was introduced in v0.12.0 and affected `sync::Cache`, `sync::SegmentedCache` and `future::Cache`. - A race between applying a write recording for an entry and concurrently removing that entry from the internal concurrent hash table could leave an orphaned node at the front of the LRU queue. Once present, no entry was ever evicted again and the cache grew unboundedly past `max_capacity`. - The same race also affected the default TinyLFU eviction policy, but with a milder symptom: each occurrence permanently leaked one phantom entry slot, causing `entry_count` and `weighted_size` to over-report and the usable capacity to shrink by one entry per occurrence. Fixed by the same change. ##### Changed - Worked around a ThreadSanitizer false positive (\[[#&#8203;602](https://github.com/moka-rs/moka/issues/602)]\[gh-pull-0602]): - Replaced the standalone `fence(Acquire)` in the internal `MiniArc`'s drop path with an `Acquire` load of the reference count, so that downstream projects can now run ThreadSanitizer on code using Moka without hitting this false positive. - `std::sync::Arc` has a similar workaround. - Raised the minimum version of the `crossbeam-epoch` crate from `v0.9.18` to `v0.9.20` to avoid the following advisory (\[[#&#8203;603](https://github.com/moka-rs/moka/issues/603)]\[gh-pull-0603]): - \[RUSTSEC-2026-0204] crossbeam-epoch: invalid pointer dereference in `fmt::Pointer` for `Atomic` and `Shared` - Moka is *not* affected by this advisory because it never formats these pointer types. However, raising the minimum version prevents downstream lockfiles from resolving to an affected `crossbeam-epoch` version via Moka. </details> --- ### Configuration 📅 **Schedule**: (UTC) - Branch creation - At any time (no schedule defined) - Automerge - At any time (no schedule defined) 🚦 **Automerge**: Enabled. ♻ **Rebasing**: Whenever PR is behind base branch, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My4yODguMCIsInVwZGF0ZWRJblZlciI6IjQzLjI4OC4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJyZW5vdmF0ZSJdfQ==-->
chore(deps): update rust crate moka to v0.12.16
Some checks failed
renovate/stability-days Updates have met minimum release age requirement
Details
ci/woodpecker/push/test Pipeline failed
Details
ci/woodpecker/pr/test Pipeline failed
Details
f7a6af8f74
rosa scheduled this pull request to auto merge when all checks succeed 2026-08-17 04:07:43 +00:00
rosa commented 2026-08-17 04:07:43 +00:00
Author
Owner
Copy link

Branch automerge failure

This PR was configured for branch automerge. However, this is not possible, so it has been raised as a PR instead.

  • Branch has one or more failed status checks
### Branch automerge failure This PR was configured for branch automerge. However, this is not possible, so it has been raised as a PR instead. ___ * Branch has one or more failed status checks
rosa merged commit a3084999d6 into main 2026-08-20 14:29:56 +00:00
rosa deleted branch renovate/moka-0.x-lockfile 2026-08-20 14:29:56 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
rosa/waifu-calendar!19
No description provided.