Windows truststore get_ca_certs() NotImplementedError handling

NousResearch/hermes-agent · cluster 49014 · agent

Data as of

Nothing open on GitHub. Fix merged in #81631. Check it covers your case.

The short answer

0open issues
0open PRs
6items grouped
Known?
Yes. 6 related items grouped here, 3 issues already closed.
Fix event
A fix was merged to main in PR #81631. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this partially resolved, deciding PR #81631. That is separate from the fix event.
Still open
Nothing open on GitHub.

A bug where truststore (pip-system-certs) raises NotImplementedError from get_ca_certs() on Windows causes OpenAI client initialization to fail with an empty error. Multiple fix attempts address tolerating this unsupported method in the SSL/CA bundle guard.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #81631 fix(ssl_guard): tolerate truststore SSLContext.get_ca_certs() NotImplementedError on Windows

    merged to main

    files: agent/ssl_guard.py, tests/agent/test_ssl_ca_guard.py

2 PRs closed without merging

From the close comments: merged via another change 2

  • #49023 fix(ssl): tolerate truststore get_ca_certs gaps · merged via another change → #81631, #49945, #49023, #53970
  • #53970 fix(ssl): tolerate truststore's unsupported get_ca_certs() in CA bundle guard · merged via another change → #81631, #49945, #49023, #53970
Closed issues · 3
  • Closed#49014fix(ssl_guard): NotImplementedError from get_ca_certs() on Windows due to truststore
  • Closed#49937[Bug]: Failed to initialize OpenAI client: (empty error) for openai-codex provider on Windows — every fresh agent init fails (CLI, api_server, Desktop); gateway warm path unaffected
  • Closed#53967[Bug]: Empty "Failed to initialize OpenAI client:" error when truststore (pip-system-certs) is active
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.38: 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
Merged PRs
#81631
Closed issues
3
Attempts
2 PRs closed without merging
Fix link checked
8 Aug 2026

For your agent

The same facts, typed.