Windows self-lock loop fix during update process
Cluster 86781. Data as of
Nothing open on GitHub. Fix merged in #86857 on 15 Aug 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 #86857. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #86782. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items address a bug where eager imports and premature deferral logic caused a circular self-lock loop on Windows during updates. The fixes involve lazy imports and conditional deferral tied to actual swap risk.
Open issues0
Open PRs0
Fixes on record
-
#86782 fix(update): lazy-import secrets_cli + defer secret_sources registry — prevent Windows self-lock loop
files:
hermes_cli/env_loader.py,hermes_cli/main.py,hermes_cli/secrets_cli.py,tests/test_lazy_secrets_dispatch.py,tests/test_lazy_secrets_import.py -
#86857 fix(update): self-lock deferral fires only when the swap is actually at risk
files:
hermes_cli/main.py,hermes_cli/update_cmd.py,tests/hermes_cli/test_update_self_lock.py
Closed issues · 1
- Closed#86781[Bug]: cryptography._rust.pyd loaded eagerly by main() — causes Windows self-lock loop on update (circular defer)
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 Lab