Profile config changes lost or misread during rescans
Cluster 109398. Data as of
Nothing open on GitHub. Fix merged in #110203 on 13 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 #110203. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #110203. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and fixes concern secondary profile configuration saved during an adapter connection being incorrectly handled by subsequent rescans. The work addresses preserving profile config changes so they are neither missed nor incorrectly picked up at the wrong time.
Open issues0
Open PRs0
Fixes on record
-
#110203 Secondary profile config saved during an adapter connection is picked up by the next rescan (#109398, salvage #109399)
files:
gateway/run_adapters.py,gateway/run_profile_reconcile.py,tests/gateway/test_profile_signature_during_connect.py
1 PR closed without merging
From the close comments: done elsewhere 1
-
#109399 fix(gateway): preserve profile config changes during connection · done elsewhere →
a15b898,#110203
Closed issues · 1
- Closed#109398Secondary profile config saved during adapter connection is missed by later rescans
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
- #110203
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 13 Sep 2026