codesandbox / codesandbox/codesandbox-client
Unable to start the microVM
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 13.6k
- Forks
- 2.4k
- Avg merge
- 6d 19h
- Merged PRs (30d)
- 2
Description
🐛 bug report
Preflight Checklist
- I have read the Contributing Guidelines for this project.
- I agree to follow the Code of Conduct that this project
adheres to. - I have searched the issue tracker for an issue that matches the one I want
to file, without success.
Description of the problem
There is a Timed out error while trying to import a new project to codesandbox, I have tried doing it from the codesandbox dashboard by importing the repository I want and also have tried with githubox and all threw the same error Unable to start the microVM. Below is the detailed error message from Codesandbox
Error: Error: Timed out after 5000ms
Version: 0c12b80
Environment: production
Event: Initial connect to Pitcher
State: ERROR
Branch: ksxmst
I also have the screenshot here👇
How has this issue affected you? What are you trying to accomplish?
There is a similar issue here https://github.com/codesandbox/codesandbox-client/issues/7663 but the error messages differs
To Reproduce
Link to sandbox: link (optional)
Your Environment
| Software | Name/Version |
|---|---|
| Сodesandbox | |
| Browser | |
| Operating System |
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue does not identify a repository file, test, or entry point to inspect. Start by reproducing the production import failure and reviewing the reported “Initial connect to Pitcher” timeout; done means identifying and resolving the cause of the microVM startup timeout with a regression check.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100