NousResearch/hermes-agent
Firecrawl waitFor lazy-loaded content fix
Cluster 106904 · agent. Data as of
1 open item. Fix attempted, not merged.
The short answer
1open issue
0open PRs
5items grouped
- Known?
- Yes. 5 related items grouped here, 0 issues already closed.
- Fix event
- No fix has been merged to main. 4 PRs closed without merging; see the attempts below.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- 1 issue and 0 PRs.
Next step: read the attempts below. Your case may extend or revive that work.
Pick up a Lab taskA bug was identified where web extraction snapshots pages before lazily loaded content arrives, and multiple fixes were proposed to pass Firecrawl's waitFor parameter to address this timing issue.
Open issues1
- Issue#106904[Bug]: web_extract snapshots before lazily loaded content arrives, and the provider cannot pass Firecrawl's waitFor
Open PRs0
4 PRs closed without merging
From the close comments: done elsewhere 2 · duplicate 1 · other 1
-
#106911 fix(web): pass Firecrawl waitFor for lazily loaded extracts · other →
#106904,#126215,#106927,#106912 -
#106912 fix(web/firecrawl): wait for lazy-loaded content before snapshotting scrape · done elsewhere →
#106911 -
#106927 fix(web): Firecrawl waitFor for lazily loaded extracts · duplicate →
#106911,#106904 -
#126215 fix(web): Firecrawl waitFor for lazily loaded extracts · done elsewhere →
7d19ac9
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.40: 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
- Closed issues
- 0
- Attempts
- 4 PRs closed without merging