Shouldn't this be 8192?

Also this means that gitpod no longer works

Shouldn't this be 8192?

Also this means that gitpod no longer works

@hoegertn Do you know how increasing the memory limit "breaks" gitpod? Is there a safe number?

Breaking might not be the "right" word but a default GitPod env has 8GB of RAM (https://www.gitpod.io/docs/configure/workspaces/workspace-classes)

So maxing out on that limit might not be a good idea.

"No longer working was too hard" I remembered lower limits on GitPod, my fault.

Breaking might not be the "right" word but a default GitPod env has 8GB of RAM (https://www.gitpod.io/docs/configure/workspaces/workspace-classes)

So maxing out on that limit might not be a good idea.

"No longer working was too hard" I remembered lower limits on GitPod, my fault.

Thanks for clarification! I meant to look at the gitpod setup this week and will try and see if there's a better value for it.

6GB aka 6144 seems to work as well.

Thanks for the comments @hoegertn and @mrgrain! I've set this to 6144 for buildup and builddown and left the other scripts (that probably wouldn't typically be used in Gitpod).

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

I also just want to provide an FYI in case anyone is unaware and checking out this PR, if you don't need a stateful buildup or builddown, you can use lerna exec --stream --include-dependencies --scope=<package-name> yarn build for buildup or lerna exec --stream --include-dependents --scope=<package-name> yarn build for builddown. It's fast enough on my machine that I don't typically care about the loss of ability to restart the build from the failed package.

AWS CodeBuild CI Report

• CodeBuild project: AutoBuildv2Project1C6BFA3F-wQm2hXv2jqQv
• Commit ID: 6a9c983
• Result: SUCCEEDED
• Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).