Updating notebooks using Git pull changes owner to root
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- docker, git, shell
- Domain
- devops, infrastructure
Research direction
Start by inspecting the repository's Dockerfiles and the notebook update workflow, then reproduce a git pull inside the Docker environment. Trace why updated files become owned by root:root and determine the expected ownership that allows notebooks to be saved. Done means updates retain writable ownership for the notebook user.
Written by the indexing model from the issue text.
Description
If you use git pull to update the notebooks the changed files get the owner and group root:root. This makes the notebook unable to be saved. I tried correcting this locally(docker) by using the $chown --preserve[=ATTR_LIST] but that did not seem to work for some reason.
- Dominant language
- Shell
- Stars
- 28
- Forks
- 10
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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.
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
astral-sh/python-build-standalone#1293 ·
-
package-update
Difficulty 1/5 Under an hour Newbie friendliness 90/100
oSoWoSo/vOid_Community_repOsitory#185 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
carbon-language/carbon-lang#7821 ·