Repository navigation
fix: prevent Gateway stalls caused by container swap - #450
Merged
Merged
Conversation
iililiiilili
marked this pull request as ready for review
November 9, 2026 06:28
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What Problem This Solves
Fixes a deployment issue where the Gateway can become unresponsive while the Node runtime reads heap pages back from swap during garbage collection.
Why This Change Was Made
The deployment bundle sets the Gateway memory and memory-plus-swap limits from one positive value. The 16 GiB default accommodates the existing 8 GiB old-space ceiling, runtime overhead, and reclaimable file cache.
User Impact
Existing deployments pick up the default when Compose recreates the Gateway. Operators can size the limit in
deployment.envand use the deployment runbook to confirm that the container has zero swap.Evidence
docker compose configrendered both limits as 16 GiB when unset or empty and as 20 GiB for a20goverride.memory.swap.max=0with the paired 16 GiB limits.CI Recovery
The required npm lock check exposed a pre-existing ACPX failure. npm resolved the Git-hosted package's Commander range to 15.1.0 because its version-qualified selector did not match the commit reference. The npm lock generator now applies the existing child pins by name when the Git-hosted parent has one locked source. Dependency manifests, locked versions, and CI requirements are unchanged.
The ACPX check, all 95 npm package lock validations, and 74 focused Linux regression tests passed locally. The Gateway and npm-lock commits each passed GPT-6.1 Sol autoreview.