Stale bytecode and cache clearing during updates
Cluster 60242 · hermes cli. Data as of
Nothing open on GitHub. Fix merged in #72525 on 27 Jul 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #72525. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #72525. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items concern stale Python bytecode (__pycache__) causing import errors or incorrect behavior after updates, and attempts to fix the timing and completeness of cache clearing during the update process.
Open issues0
Open PRs0
Fixes on record
-
#72525 fix(update): close the stale-bytecode class with a launch-time checkout-fingerprint sweep
files:
.gitignore,hermes_cli/main.py,hermes_cli/plugins_cmd.py,tests/hermes_cli/test_bytecode_sweep.py,tests/hermes_cli/test_update_autostash.py
1 PR closed without merging
From the close comments: merged via another change 1
-
#60276 fix(update): refresh runtime modules before lazy backends · merged via another change →
d76d0d6,#72525
Closed issues · 1
- Closed#60242Post-update lazy-backend refresh fails on stale __pycache__ — cache cleared one update too late
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.67: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the LabAt a glance
- Subsystem
- hermes cli
- Merged PRs
- #72525
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 27 Jul 2026