Fix caching of transient None cloud provider value
Cluster 22324 · agent. Data as of
Nothing open on GitHub. Fix merged in #22794 on 9 May 2026. Check it covers your case.
The short answer
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #22794. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #22794. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and PRs address a bug where a None result from cloud provider detection is incorrectly cached, permanently forcing the process into local mode. Multiple fix attempts target the same root cause.
Open issues0
Open PRs0
Fixes on record
-
#22794 fix(browser_tool): do not cache transient None cloud provider resolution (salvage #22531)
files:
tests/tools/test_browser_cloud_provider_cache.py,tools/browser_tool.py
2 PRs closed without merging
From the close comments: done elsewhere 1 · merged via another change 1
Closed issues · 1
- Closed#22324[Bug]: _get_cloud_provider() caches transient None, pinning process to local mode forever
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.50: 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
- agent
- Merged PRs
- #22794
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 9 May 2026