Tatsuya Kawano

| | test? | retrieved value | return value from wrapper's `get_with` | log | |--:|:--|:--|:--|:--| | 1 | no | `None` | a new `V` | none | |...

| | test? | retrieved value | return value from wrapper's `get_with` | log | |--:|:--|:--|:--|:--| | 1 | no | `None` | a new `V` | none | |...

Hi. Thanks for looking into this. > Sorry for the late response. Recently it's the Chinese New Year holiday, I just returned from a vacation in Japan. (Maybe a bit...

> ```rust > cache_loader.insert( > my_entry.key, > my_entry.value, > None, // policy_weight, > Some(dt_to_duration(my_entry.last_modified))), > dt_to_duration(my_entry.last_accessed), > None // expiration_time > ); > ``` Rather than making `CacheLoader::insert` method to...

> 3. When `finish` is called, it will do the followings: > - ... > - Now the cache state has been restored. Invoke `run_pending_tasks` (moka v0.12.x) several times to...

> Kani v0.54.0 was ok. So we will pin it to v0.54.0 for now. Pinned it to `v0.54.0` via #458.

Thank you for reporting the issue with the repro. If I understand correctly, we cannot workaround the both cases at the cache side: 1. The dead-lock case: `get_with` only resolves...

As for the second case, maybe you can resolve the issue at the caller side by using `try_get_with`. I will create an example when I get back to my desk....

> I don't think there's anything stopping Request B and C from polling A's future while it's still working No, request B and C cannot poll it. > Request A...

Future A is owned by Request A. In Rust, `async fn` or `async` block creates an anonymous struct implementing `Future`. Request A's anonymous struct owns Future A. When Request A...