Fix web extract cache keying by URL not position
Cluster 111803. Data as of
Nothing open on GitHub. Fix merged in #112245 on 16 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 #112245. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #112245. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items address a bug where batch web extraction cached page content under the wrong URL key due to indexing by position rather than the actual returned URL. The fix ensures each extracted page is cached under its own requested URL.
Open issues0
Open PRs0
Fixes on record
-
#112245 fix(web): web_extract caches each page under its own requested URL, never by batch position (#111803, #97378, salvage #111806)
files:
plugins/web/tavily/provider.py,tests/tools/test_web_tools_tavily.py,tools/web_tools_extract.py,website/docs/user-guide/features/web-search.md
1 PR closed without merging
From the close comments: merged via another change 1
-
#111806 fix(web): cache extracts by returned URL · merged via another change →
7935294,#112245
Closed issues · 1
- Closed#111803web_extract caches by POSITION: a partial-failure batch writes one page's content under another URL's cache key
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
- #112245
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 16 Sep 2026