NousResearch/hermes-agent

Large integer ID corruption in config JSON boundary

Cluster 123439 · dashboard. Data as of

2 open items. Fix attempted, not merged.

The short answer

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

These issues and PRs concern 19-digit platform IDs (snowflakes) being silently corrupted when crossing the web config API JSON boundary, where large integers exceed JavaScript's safe integer range. Proposed fixes involve preserving such IDs as strings rather than bare numeric values.

Open issues1

  • Issue#123439[Bug]: Config UI round-trip silently corrupts 19-digit platform ids (bare ints on the /api/config JSON boundary)

Open PRs1

  • PR#123466fix(web): preserve platform ids and prevent 19-digit snowflake corruption on config JSON boundary

2 PRs closed without merging

From the close comments: done elsewhere 1 · other 1

  • #123488 fix(config): round-trip big platform ids through the web config intact (fixes #123439) · done elsewhere
  • #123497 fix(config): keep >2^53 ids as strings across the web config boundary (fixes #123439) · other → #123439, #1
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
dashboard
Closed issues
0
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.