chore(deps): update rust crate moka to v0.12.15

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
moka	dependencies	patch	0.12.13 → 0.12.15

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

moka-rs/moka (moka)

v0.12.15

Compare Source

Fixed

• Fixed a bug where re-inserting an expired entry could cause it to lose its
  expiration time and remain in the cache indefinitely when using a custom Expiry
  policy with per-entry expiration. ([#​582][gh-pull-0582] by [@​jiangzhe][gh-jiangzhe],
  [#​581][gh-pull-0581] by [@​atrocities][gh-atrocities], reported in
  [#​575][gh-issue-0575]):
  • This occurred when an entry that had expired but not yet been evicted was
    re-inserted, and expire_after_update returned None. This primarily
    affected users who only override expire_after_create, since the default
    expire_after_update returns duration_until_expiry, which is None for
    expired entries.
  • This bug was introduced by the changes in v0.12.13 ([#​549][gh-pull-0549] and
    [#​564][gh-pull-0564]).
  • Subtle behavior change:
    • Before this fix, re-inserting an expired entry was treated as an update,
      so Expiry::expire_after_update was called.
    • After this fix, re-inserting an expired entry is treated as a creation,
      so Expiry::expire_after_create is called instead.
    • This may change the expiration time of re-inserted entries, depending on
      your Expiry trait implementation.
• Fixed flaky tests cht::segment::tests::drop_many_values and
  drop_many_values_concurrent that were failing on high-core-count machines
  ([#​586][gh-pull-0586]):
  • These tests were using a CPU-dependent segment count, causing inconsistent
    bucket array shrinking behavior of the internal segmented hash map across
    different machines.
  • Changed these tests to use a fixed segment count (4) for consistent results.

Changed

• Disabled flaky GC-dependent tests by default using run_flaky_tests cfg
  ([#​584][gh-pull-0584]):
  • These tests rely on epoch-based garbage collection (crossbeam-epoch) timing
    that is not guaranteed, causing intermittent failures.
  • Fixed [#​539][gh-issue-0539] and [#​580][gh-issue-0580].
  • To run these tests, set RUSTFLAGS='--cfg run_flaky_tests'.

v0.12.14

Compare Source

Fixed

• Fixed a race condition in the and_compute_with method in the future::Cache.
  ([#​574][gh-pull-0574] by [@​Squadrick][gh-Squadrick]):
  • When multiple calls are made concurrently for the same key, the f closure may
    read a stale value, causing the first update to be lost when it is overwritten
    by a later one.

Changed

• Use dep: keyword in the crate features. ([#​577][gh-pull-0577] by
  [@​alexanderkjall][gh-alexanderkjall]).

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, 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 was generated by Mend Renovate. View the repository job log.