Repository navigation
chore(devcontainer): remove the container task limit - #29
Merged
Merged
Conversation
The container allows 1024 tasks, and the limit counts threads. Editor tooling uses about 400 tasks on a 32-core host, so release verification reaches the limit. Builds fail, and the editor cannot start processes. The container sets no memory or CPU limit, so the task limit alone does not contain a runaway workload and is effectively performative anyway. Remove the container task limit. devcontainer: - Use the Docker default task limit for the container.
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.
The container allows 1024 tasks, and the limit counts threads. Editor tooling uses about 400 tasks on a 32-core host, so release verification reaches the limit. Builds fail, and the editor cannot start processes. The container sets no memory or CPU limit, so the task limit alone does not contain a runaway workload and is effectively performative anyway.
Remove the container task limit.
devcontainer: