codesandbox / codesandbox/codesandbox-client
Failed to fork repository
Open
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
When creating a fork from above modal, after clicking Fork repository button, an error banner appears at the bottom right of page with this error content:
Failed to fork repository
{"message":"Request failed with status code 502","name":"Error","stack":"@https://codesandbox.io/static/js/vendors~app.f0d671724.chunk.js?_sw-precache=de922f4367705102d5655319d33e93d5:1:410398\n@https://codesandbox.io/static/js/vendors~app.f0d671724.chunk.js?_sw-precache=de922f4367705102d5655319d33e93d5:1:412984\n@https://codesandbox.io/static/js/vendors~app.f0d671724.chunk.js?_sw-precache=de922f4367705102d5655319d33e93d5:1:405347\nr@https://codesandbox.io/static/js/common.ab3c7e841.chunk.js?_sw-precache=8b427389c6cc5351c0a64c0205fd1cf0:1:202007","config":{"url":"/api/beta/fork/github/chromedp/docker-headless-shell","method":"post","data":"{\"name\":\"docker-headless-shell\",\"team_id\":\"cd035ffd-e63d-48fd-b793-9e3e4614abc8\"}","headers":{"Accept":"application/json, text/plain, */*","Content-Type":"application/json;charset=utf-8","x-codesandbox-client":"legacy-web"},"transformRequest":[null],"transformResponse":[null],"timeout":0,"xsrfCookieName":"XSRF-TOKEN","xsrfHeaderName":"X-XSRF-TOKEN","maxContentLength":-1}}
How has this issue affected you? What are you trying to accomplish?
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
Start with the fork flow that calls the POST /api/beta/fork/github/{repository} endpoint from the repository-fork modal. Reproduce the 502 response using the repository and team data shown in the report, then trace whether the failure is in the client request or the fork service. Done means the repository can be forked successfully and the error banner no longer appears.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100