aws-amplify / aws-amplify/amplify-cli

All Amplify CLI commands fail with EBUSY error after upgrade

Open
#12,660 7 comments 0 reactions 0 assignees View on GitHub
bug mock p2 storage windows
Dominant language
TypeScript
Stars
2.9k
Forks
825
Avg merge
11d 23h
Merged PRs (30d)
2

Description

### How did you install the Amplify CLI?

_No response_

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

14.15.3

### Amplify CLI Version

12.0.0

### What operating system are you using?

Windows

### Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.

No changes.

### Describe the bug

After running `amplify upgrade` and successfully installing version 12.0.0, all attempts to run any amplify command generate the following error:

🛑 EBUSY: resource busy or locked, rmdir 'C:\Users\9037568\.amplify\lib\amplify-dynamodb-simulator\emulator'

When I tried deleting that folder manually I got an error from the OS saying it was in use by another process, so I suspect the upgrade left something running, but I've been unable to identify what that is.

### Expected behavior

Upgrade should not kill the CLI.

### Reproduction steps

Upgrade.
Run any amplify command.

### Project Identifier

Can't because all amplify commands fail.

### Log output

```
# Put your logs below this line
2023-05-20T14:36:31.552Z|info : amplify upgrade core
2023-05-20T14:36:31.586Z|info : amplify-cli-core.banner-message/index.ts.fetch banner messages from https://aws-amplify.github.io/amplify-cli/banner-message.json({}

```

### 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

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.