unboundsoftware/schemas
6
0
Fork 0
Code Issues 1 Pull Requests 1 Actions Packages Projects Releases 32 Activity

fix: cap Node.js heap to prevent OOM during wgc composition #788

Merged
argoyle merged 1 commits from fix-wgc-oom into main 2026-03-29 09:31:55 +00:00
Conversation 0 Commits 1 Files Changed 1
+3
argoyle commented 2026-03-29 08:01:31 +00:00
Owner
Copy Link
Copy Source

Summary

  • Sets NODE_OPTIONS=--max-old-space-size=64 in Dockerfile to cap Node.js heap when running wgc router compose
  • Prevents container OOMKills in memory-constrained environments (e.g. acctest with 128Mi limit)
  • The wgc Node.js process was using unbounded heap, which combined with the Go service easily exceeded container memory limits during rapid schema publishing

🤖 Generated with Claude Code

## Summary - Sets `NODE_OPTIONS=--max-old-space-size=64` in Dockerfile to cap Node.js heap when running `wgc router compose` - Prevents container OOMKills in memory-constrained environments (e.g. acctest with 128Mi limit) - The wgc Node.js process was using unbounded heap, which combined with the Go service easily exceeded container memory limits during rapid schema publishing 🤖 Generated with [Claude Code](https://claude.com/claude-code)
argoyle scheduled this pull request to auto merge when all checks succeed 2026-03-29 08:01:45 +00:00
argoyle added 1 commit 2026-03-29 09:22:22 +00:00
fix: cap Node.js heap to prevent OOM during wgc composition
schemas / vulnerabilities (pull_request) Successful in 1m58s
Details
schemas / check (pull_request) Successful in 2m36s
Details
schemas / check-release (pull_request) Successful in 2m46s
Details
schemas / build (pull_request) Successful in 5m54s
Details
pre-commit / pre-commit (pull_request) Successful in 6m40s
Details
schemas / deploy-prod (pull_request) Has been skipped
Details
5208af2010 
Set NODE_OPTIONS=--max-old-space-size=64 after wgc installation
to limit Node.js heap for runtime wgc invocations, preventing
container OOMKills in memory-constrained environments.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
argoyle force-pushed fix-wgc-oom from af967fdb2a to 5208af2010 2026-03-29 09:22:22 +00:00 Compare
argoyle merged commit 9a32cdb1b3 into main 2026-03-29 09:31:55 +00:00
argoyle deleted branch fix-wgc-oom 2026-03-29 09:31:56 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
dependencies
Pull requests that update a dependency file
 docker
go
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
acctest (Shiny Acctest) argoyle (Joakim Olsson) buildtools (Buildtools) kubernetes (Kubernetes) releaser (Unbound Releaser) renovate (Renovate Bot)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: unboundsoftware/schemas#788
Delete Branch "fix-wgc-oom"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?