ffmpeg crash on Windows causing blocking failures

NousResearch/hermes-agent · cluster 130064 · hermes cli

Data as of

4 open items. Fix attempted, not merged.

The short answer

1open issue
3open PRs
4items grouped
Known?
Yes. 4 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 3 PRs.

A Windows Server 2016 compatibility issue where ffmpeg crashes due to a missing API entry point, plus related fixes to make ffmpeg probe failures non-blocking and improve error code decoding for diagnostics.

Open issues1

  • Issue#130064Windows Server 2016: ffmpeg (BtbN win32-x64 9.0.1) crashes with "Entry Point Not Found: SetThreadDescription", blocking update completion and causing automatic rollback

Open PRs3

  • PR#130068fix(pm): make ffmpeg failures non-blocking
  • PR#130073fix(pm): decode known NTSTATUS exit codes in --version probe failures
  • PR#142838fix(pm): treat ffmpeg as a host gap on Windows Server 2016 (#130064)
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.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
hermes cli
Closed issues
0
Attempts
0 PRs closed without merging

For your agent

The same facts, typed.