truststore injection timing and SSL context fixes

NousResearch/hermes-agent · cluster 126808 · agent

Data as of

5 open items. Fix attempted, not merged.

The short answer

1open issue
4open PRs
5items grouped
Known?
Yes. 5 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 4 PRs.

These issues and fixes address race conditions and ordering problems with platform truststore injection, ensuring the trust store is installed before SDKs capture ssl.SSLContext and that the pre-injection stdlib SSLContext remains usable afterward.

Open issues1

  • Issue#126808[Bug]: RecursionError: maximum recursion depth exceeded` calling AWS Bedrock, caused by truststore/botocore SSLContext import-order race (Python 3.14)

Open PRs4

  • PR#126820fix(agent): install the platform trust store when run_agent is imported
  • PR#126849fix(pm): route truststore injection through the shared install guard
  • PR#126881fix(agent): install platform trust at run_agent import, before any SDK can capture ssl.SSLContext
  • PR#127638fix(ssl): keep the pre-injection stdlib SSLContext usable after truststore injection (#126808)
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.00 means 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 Lab

At a glance

Subsystem
agent
Closed issues
0
Attempts
0 PRs closed without merging

For your agent

The same facts, typed.