Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Node v20.12.x causes segmentation fault with npx ampx sandbox and latest version of node due to parcelWatcher #1297

Open
deconduino opened this issue Apr 15, 2024 · 5 comments
Labels
bug Something isn't working dependency Issue related to upstream dependency p2

Comments

@deconduino
Copy link

Environment information

System:
  OS: Linux 5.15 Arch Linux
  CPU: (12) x64 AMD Ryzen 5 3600 6-Core Processor
  Memory: 11.50 GB / 15.59 GB
  Shell: /usr/bin/zsh
Binaries:
  Node: 20.12.2 - ~/.nvm/versions/node/v20.12.2/bin/node
  Yarn: undefined - undefined
  npm: 10.5.2 - ~/.nvm/versions/node/v20.12.2/bin/npm
  pnpm: undefined - undefined
NPM Packages:
  @aws-amplify/backend: 0.13.0-beta.16
  @aws-amplify/backend-cli: 0.12.0-beta.18
  aws-amplify: 6.0.28
  aws-cdk: 2.137.0
  aws-cdk-lib: 2.137.0
  typescript: 5.4.5

Description

Ran into this one today, putting it here in case anyone else hits the same issue. Running npx amplify sandbox will result in a segmentation fault when using node v20.12 if there are any wildcards in the .gitignore file due to an issue with parcelWatcher.

Workaround - rollback to node v20.11 until resolved.

parcel-bundler/watcher#170

@deconduino deconduino added the pending-triage Incoming issues that need categorization label Apr 15, 2024
@JonasGranlund1
Copy link

JonasGranlund1 commented Apr 17, 2024

Thanks! It solved the problem for me.

@jgomezupstart13
Copy link

thank you for this!!! really really thank you, I was going crazy trying to find a way to solve it.

@ykethan ykethan added the dependency Issue related to upstream dependency label Apr 19, 2024
@ykethan
Copy link
Contributor

ykethan commented Apr 19, 2024

@deconduino thank you for reporting this. Marking this as bug to track this.

@ykethan ykethan added bug Something isn't working p2 and removed pending-triage Incoming issues that need categorization labels Apr 19, 2024
@ykethan ykethan changed the title Segmentation fault with npx amplify sandbox and latest version of node due to parcelWatcher Node v220.12 causes segmentation fault with npx amplify sandbox and latest version of node due to parcelWatcher Apr 23, 2024
@ykethan ykethan changed the title Node v220.12 causes segmentation fault with npx amplify sandbox and latest version of node due to parcelWatcher Node v20.12 causes segmentation fault with npx amplify sandbox and latest version of node due to parcelWatcher Apr 23, 2024
@ykethan ykethan changed the title Node v20.12 causes segmentation fault with npx amplify sandbox and latest version of node due to parcelWatcher Node v20.12.x causes segmentation fault with npx amplify sandbox and latest version of node due to parcelWatcher Apr 23, 2024
@ykethan ykethan pinned this issue Apr 23, 2024
@ykethan ykethan changed the title Node v20.12.x causes segmentation fault with npx amplify sandbox and latest version of node due to parcelWatcher Node v20.12.x causes segmentation fault with npx ampx sandbox and latest version of node due to parcelWatcher May 8, 2024
@pchinjr
Copy link

pchinjr commented May 16, 2024

thanks for reporting, I was using Node v.20.2 and found the same error, I rolled Node back to v.20.11.0 and sandbox is working again.

@TheRealBenForce
Copy link

Thank you!

nvm install --lts bringing me to v20.13.1 worked for me

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working dependency Issue related to upstream dependency p2
Projects
None yet
Development

No branches or pull requests

6 participants