You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've spotted that a moka::future::Cache doesn't fire its eviction listener if an entry is manually invalidated with the blocking op, but I can fire the eviction listener if using .invalidate_all() or the sync cache. The below examples should repro this behaviour.
For these tests the eviction handler only fires for the first two:
running 3 tests
evicted key: foo, value: sync, cause: Explicit
test sync_triggers_listener ... ok
evicted key: foo, value: all, cause: Explicit
test invalidate_all_triggers_listener ... ok
test blocking_invalidate_should_trigger_listener ... ok
My understanding of invalidate is that it is a manually triggered cache eviction, is that correct? If so I think this may be a bug.
The text was updated successfully, but these errors were encountered:
I've spotted that a
moka::future::Cache
doesn't fire its eviction listener if an entry is manually invalidated with the blocking op, but I can fire the eviction listener if using.invalidate_all()
or the sync cache. The below examples should repro this behaviour.For these tests the eviction handler only fires for the first two:
My understanding of invalidate is that it is a manually triggered cache eviction, is that correct? If so I think this may be a bug.
The text was updated successfully, but these errors were encountered: