Cairn

Redact secrets from cron error persistence

NousResearch/hermes-agent · cluster 102700 · cron

Data as of

3 open items. Fix attempted, not merged.

The short answer

1open issue
2open PRs
4items grouped
Known?
Yes. 4 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 1 PR 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 2 PRs.

These issues and PRs concern API keys and tokens appearing in raw error strings that get written to jobs.json and executions.db. The work involves sanitizing or redacting sensitive values before they are persisted.

Open issues1

  • Issue#102700cron: jobs.json stores raw error strings that can leak API key identifiers

Open PRs2

  • PR#102722fix(cron): redact secrets before persisting errors to jobs.json/executions.db
  • PR#102814fix(cron): sanitize API keys/tokens in error messages before persisting to jobs.json

1 PR closed without merging

From the close comments: other 1

  • #102732 fix(cron): sanitize last_error before writing jobs.json · other → #102722
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
1 PR closed without merging

For your agent

The same facts, typed.

cluster/102700.json
cluster/102700.md