Windows fcntl compatibility fixes in state lockguard
Cluster 118026. Data as of
Nothing open on GitHub. Fix merged in #118269 on 21 Sep 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 #118269. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #118269. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items address failures in hermes_state_lockguard.py on Windows, where missing or partial fcntl support causes backend startup issues. The work involves adjusting WAL guard behavior and tolerating fcntl shims rather than treating their absence as fatal.
Open issues0
Open PRs0
Fixes on record
-
#118269 fix(state): a partial fcntl must disable the WAL guard, not kill every importer
files:
hermes_state_lockguard.py,tests/hermes_state/test_lockguard_fcntl_tolerance.py
1 PR closed without merging
From the close comments: partial fix 1
-
#118040 fix(state): tolerate fcntl shims during Windows startup · partial fix →
9b028c7,#118026
Closed issues · 1
- Closed#118026[Bug][Windows] hermes_state_lockguard.py 未处理 fcntl.F_RDLCK 缺失，导致后端启动失败
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
- Merged PRs
- #118269
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 21 Sep 2026