aws-amplify / aws-amplify/amplify-cli
improve error messaging for "Your socket connection to the server... will be closed"
- Dominant language
- TypeScript
- Stars
- 2.9k
- Forks
- 825
- Avg merge
- 11d 23h
- Merged PRs (30d)
- 2
Description
### How did you install the Amplify CLI?
npm
### If applicable, what version of Node.js are you using?
v19.0.1
### Amplify CLI Version
10.6.2
### What operating system are you using?
Ubuntu
### Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
There is an existing override.ts but is the original from functional deployments.
### Describe the bug
Initializing an existing project under my own account.
Removed the amplify team-provider-info.json file.
Getting error on amplify push:
**
:~/Documents/DeckAnalyzer$ amplify push
✖ There was an error pulling the backend environment devtwo.
🛑 Packaging overrides failed.
Command failed with exit code 1: yarn install
Resolution: There may be errors in your overrides file. If so, fix the errors and try again.
Learn more at: https://docs.amplify.aws/cli/project/troubleshooting/
Session Identifier: 23f96950-8041-44f9-8a30-2a76743c0494
**
### Expected behavior
Expected project to initialize and deploy.
### Reproduction steps
amplify init
delete team-provider-info.json
amplify push
### Project Identifier
Project Identifier: caa1b95f02a190bcb0b4ee7bcb9e7b6f
### Log output
```
# Put your logs below this line
```
### Additional information
_No response_
### Before submitting, please confirm:
- [X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
- [X] I have removed any sensitive information from my code snippets and submission.
Contributor guide
Research direction
Start by reproducing the reported sequence with `amplify init`, deleting `team-provider-info.json`, and running `amplify push` on Ubuntu with the stated CLI and Node versions. Inspect the existing `override.ts` and the packaging step that reports `yarn install` failure; done means the project initializes and deploys without the misleading socket-connection error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, node.js, typescript
- Domain
- backend, cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100