Git repo gets corrupted when using Crostini |
||
Issue descriptionChrome Version: 71.0.3578.21 OS: Chrome What steps will reproduce the problem? (1) Use crostini to develop something, using VS Code and terminal (2) After a while notice the git repo has been corrupted I've seen this a few times now. I think a file in the .git folder is being truncated. It might be because I've been leaving VS Code running while putting my laptop to sleep. It could also be a bug in VS Code. I can provide the git repo privately if desired.
,
Nov 29
<triage>Assigning to Daniel</triage>
,
Nov 29
Could you expand a little on how to reproduce this? I am guessing step 1 involves making commits or doing other git operations. Do you use the VS Code git integration or the command-line git tool? Also, what behavior are you observing once the git repo is corrupted? (error messages from git, etc.)
,
Nov 29
I wish I had repo steps. I use the command line git tool, not VS code git, but VS code git still does stuff (e.g. it shows the status of files etc.). The behavior is stuff like this: ➜ jeloopdead git:(non-polymer) git status fatal: unable to read dcf9f7158ec16b3e0dab5e6fbfed9868062f08e1 At which point I can't commit or upload or anything. I have also got other errors (I think once one of the files in .git somewhere had been truncated to zero length).
,
Nov 29
BTW I know this makes it really hard to fix, but I wanted to log it in case anyone else had seen it or had ideas or suspicions. |
||
►
Sign in to add a comment |
||
Comment 1 by vapier@chromium.org
, Nov 19