Amplify push causes SIGSEGV #12390
Comments
|
hey @curb47, Thank you for reaching out. could you confirm if your function lockfile is up to date? could you try running |
ykethan
added
functions
|
Thanks @ykethan -- I did the steps you suggested but am still getting the same result. I am happy to take this offline if you think this is an issue specific to my install. |
github-actions
bot
removed
the
pending-response
|
hey @curb47, as a quick check, could you try removing the |
|
possibly related to #12402 (comment) |
|
hey @curb47, interesting. are you able to the command |
ykethan
added
the
pending-response
|
Hey @ykethan , I was able to successfully run that command in the No, I am not using any container. I have tried to only use amplify commands to manage this project. |
github-actions
bot
removed
the
pending-response
|
Hey @curb47 after installing dependencies were you able to push successfully? What version of yarn are you using? |
josefaidt
added
the
pending-response
|
Hey @josefaidt , no, I am getting the same failure. I am using the latest version of yarn: 1.22.19. This is the error: |
github-actions
bot
removed
the
pending-response
|
+1 to this. I have the same exact stack trace with no containers. Adding auth and storage works fine, but this occurs when I try to add an api in conjunction with a lambda |
|
Hey @curb47 @brendanwong was Node/npm installed with |
josefaidt
added
the
pending-response
|
Hi @josefaidt, node was not installed with |
github-actions
bot
removed
the
pending-response
|
Hey @curb47 what dependencies do you have listed for this Function? Are you able to build/push other functions in the project? |
josefaidt
added
the
pending-response
|
Hi @josefaidt , these are my dependencies. |
github-actions
bot
removed
the
pending-response
|
Hey @curb47 I am not able to reproduce with the same dependency list. Are you able to push other functions by chance, such as the small "Hello World" template? That should help us narrow down whether this is unique to the affected Function or perhaps yarn |
josefaidt
added
the
pending-response
|
Hey @curb47 are you still experiencing this? |
|
I'm experiencing it still. Same symptoms, same setup, same attempted remediation. |
|
This is not a fix to the problem as described. I solved the issue by switching to NPM for package management. |
|
Hey folks just wanted to follow-up on this one. I have not been able to successfully reproduce this issue, however would like to reference a few feature requests that I think would help us workaround this
Please subscribe or add your thoughts to the feature requests linked above. |
|
|
Any update on this? same problem here for yarn after adding a lambda function to my Amplify project |
|
So I just stopped using yarn. I went back to |
|
All guys with problems, do you use an Apple Silicon? Otherwise you installed yarn with home-brew right? So I use a M1 MacBook Pro. |
|
@biller-aivy On Mac install node using brew it will fix your prb |
|
Re-installed yarn with
|
How did you install the Amplify CLI?
yarn
If applicable, what version of Node.js are you using?
v18.12.1
Amplify CLI Version
v11.0.3
What operating system are you using?
Mac
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
No manual changes made
Describe the bug
The following error occurred when I attempted to push:
amplify pushExpected behavior
amplify pushshould finish successfully.Reproduction steps
amplify pushfrom root directory of project.Project Identifier
Project Identifier: 22ffa3f55ead13e5fd7ee5ef4d3aa320
Log output
Additional information
Here is the stacktrace when running
amplify push --debug:Before submitting, please confirm:
The text was updated successfully, but these errors were encountered: