Skip to content

fix(relay): increase OREF curl maxBuffer to prevent ENOBUFS#609

Merged
koala73 merged 2 commits intomainfrom
fix/oref-enobufs
Feb 28, 2026
Merged

fix(relay): increase OREF curl maxBuffer to prevent ENOBUFS#609
koala73 merged 2 commits intomainfrom
fix/oref-enobufs

Conversation

@koala73
Copy link
Owner

@koala73 koala73 commented Feb 28, 2026

Summary

  • OREF history bootstrap fails with spawnSync curl ENOBUFS on Railway
  • AlertsHistory.json exceeds execFileSync default 1MB maxBuffer
  • Increased to 10MB — affects only the orefCurlFetch helper

Test plan

  • Deploy to Railway → no more ENOBUFS error in logs
  • [Relay] OREF history bootstrap: N records should appear instead

AlertsHistory.json response exceeds execFileSync default 1MB buffer,
causing spawnSync ENOBUFS on Railway container at startup.
@vercel
Copy link

vercel bot commented Feb 28, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

4 Skipped Deployments
Project Deployment Actions Updated (UTC)
worldmonitor Ignored Ignored Preview Feb 28, 2026 11:01pm
worldmonitor-finance Ignored Ignored Preview Feb 28, 2026 11:01pm
worldmonitor-happy Ignored Ignored Preview Feb 28, 2026 11:01pm
worldmonitor-startup Ignored Ignored Preview Feb 28, 2026 11:01pm

Request Review

@chatgpt-codex-connector
Copy link

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

…ffer

Large AlertsHistory.json overflows execFileSync stdout buffer (ENOBUFS).
Now writes to temp file via curl -o, reads with fs.readFileSync, cleans up.
Live alerts (tiny payload) still use stdout path.
@koala73 koala73 merged commit 1d7547f into main Feb 28, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant