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

amplify push stuck forever before pushing changes, with no errors #12859

Closed
2 tasks done
giorgiocarniel opened this issue Jun 23, 2023 · 3 comments
Closed
2 tasks done
Labels
pending-response Issue is pending response from the issue author pending-triage Issue is pending triage

Comments

@giorgiocarniel
Copy link

How did you install the Amplify CLI?

npm

If applicable, what version of Node.js are you using?

12.18.0

Amplify CLI Version

10.2.3, got same error on 12.1.1 (current @latest)

What operating system are you using?

Windows 10

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

Command amplify push --yes is stuck forever on my local terminal, but somehow works fine on amplify CI/CD triggered by git commit.
There are no errors shown either on the terminal or amplify logs.
Already tried to reinstall both aws cli and amplify cli (and deleting both .aws and .amplify folders) but nothing was solved.
Already tried multiple cli versions (9.10, 10.2.3, 12.1.1), the --force parameter on amplify push, env pull, and env checkout.

The last line of amplify log is always this (amplify-meta.json exists on the deployment s3 bucket):
amplify-provider-awscloudformation.aws-s3.s3.getFile([{"Key":"[***]ify-[***]json","Bucket":"[***]ify-[***]tech-[***]gca-[***]316-[***]ment"}])

image

Terminal shows this forever, with no signs of life:
image

It was working until 2 days ago.
Even if I turn back to a commit from multiple days ago when I'm certain it worked, the result is the same, stuck forever.

Btw I know it may take a while to push changes when there are multiple lambda codes to compile but this is not the case, I kept it running for a full day multiple times, it never complete.

Expected behavior

amplify push should complete, not get stuck

Reproduction steps

Unable to provide reproducible steps

Project Identifier

Project Identifier: 953c1a0842174ddef0ecd07b22dc2f4b

My app id is doi87xs5wbi44 on eu-central-1

Log output

amplify-cli-2023-06-23.log

Additional information

Any workaround is accepted, this problem is heavily impacting our productivity

Before submitting, please confirm:

  • I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
  • I have removed any sensitive information from my code snippets and submission.
@giorgiocarniel giorgiocarniel added the pending-triage Issue is pending triage label Jun 23, 2023
@josefaidt
Copy link
Contributor

Hey @giorgiocarniel 👋 thanks for raising this! Although I'm not seeing any throttling errors in the logs you provided I'm curious whether this hangs only when executing commands locally or whether it also hangs when deploying with Amplify Hosting? How large are the Lambda Functions? And lastly, are you able to run amplify build without issue?

@josefaidt josefaidt added the pending-response Issue is pending response from the issue author label Jun 28, 2023
@josefaidt
Copy link
Contributor

Closing due to inactivity

@josefaidt josefaidt closed this as not planned Won't fix, can't repro, duplicate, stale Aug 14, 2023
@github-actions
Copy link

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pending-response Issue is pending response from the issue author pending-triage Issue is pending triage
Projects
None yet
Development

No branches or pull requests

2 participants