Whole file

iamsinghrajat/async-cache

The author described this change as fix: ensure that future exception is retrieved to avoid warnings (#30). It counts as a record because the check below fails on the code as it stood at 366c4d919 and passes on 27ad941de, with nothing else changed between the two runs.

Fix saved2026-04-17
Sharing licenceMIT · LICENSE
Change size+1 0

What the code was meant to do, written into the code itself as a save note

fix: ensure that future exception is retrieved to avoid warnings (#30)

The change

8989 return value
9090 except Exception as exc:
9191 fut.set_exception(exc)
92+ fut.exception()
9293 raise
9394 finally:
9495 # cleanup under lock

The check that tells the two apart

failpass·tests/test_edge_cases.py::TestErrorHandling::test_future_exception_retrival

Check file tests/test_edge_cases.py, taken without changes from the fix and copied onto the older code, so the exact same check runs against both versions.

Origin and history

The code before it366c4d919af9240db245a8863fb2e6cfb222a83e
Broken version dated2026-02-28
Modulecache.async_cache
Units changedAsyncCache
Fingerprint8cad04fc82ab6d27
Checked2026-08-18 by goldset/0.1

Every field above is generated by our program. None of it is written by hand.