codesandbox / codesandbox/codesandbox-client
Executable bit is lost when forking
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
Description of the problem
Executable bit is lost after forking a sandbox.
How has this issue affected you? What are you trying to accomplish?
I forked a sandbox with production shell scripts triggered by a Dockerfile built container. To my surprise, the executeable bit was lost, which can be quite difficult to track down as the errors from k8s deployments, past the CI stage, are sometimes hard to reach.
To Reproduce
- Run
touch start.sh && chmod a+x start.sh - Fork the sandbox
Example sandbox with deploy.sh marked executeable https://codesandbox.io/s/mask-bug-25v8ms?file=/broken_file-cant_save.sh
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 reproduction steps and the linked example sandbox, then trace the sandbox forking flow to find where file permissions are copied. Done means an executable file such as start.sh or deploy.sh retains its executable bit after a fork, including in the Dockerfile-based workflow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, javascript, shell
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100