Chronos fire token validated against wrong profile

NousResearch/hermes-agent · cluster 69715 · cron

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 bug where Chronos fire webhook tokens were being validated against the default profile instead of the specific job's profile. Includes the bug report and corresponding fix.

Open issues1

  • Issue#69715[Bug]: Chronos fire webhook validates tokens against the default profile before resolving the job profile

Open PRs3

  • PR#69730fix(cron): verify fire tokens against job profile
  • PR#70624fix: validate Chronos fire token against job's profile, not default (#69715)
  • PR#109582fix(cron): authenticate Chronos callbacks with the job profile
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
cron
Closed issues
0
Attempts
0 PRs closed without merging

For your agent

The same facts, typed.