Replies: 2 comments 6 replies
-
|
Any chance this project is public? I could give it a shot to see
if I get the same issue. Without a reproduction it will be tough
to track down.
Is there anything different about how you open this project
compared to others? For example do you open it directly or is it
part of a workspace, are all the projects on the same machine,
etc.
Otherwise all I can think of is to try disabling extensions,
clearing data (browser and maybe on disk at
~/.local/share/code-server but note removing the latter will
delete extensions as well), cloning the project again, that sort
of thing.
|
Beta Was this translation helpful? Give feedback.
-
Yes :
Nope, it's based on a template that I use often :
Yes.
How could they not ?
The issue occurs on a single project but on all browsers I use
I'd like to avoid that.
Will try. |
Beta Was this translation helpful? Give feedback.
-
Same, and yeah you were right; it did not reproduce for me. 😞 Just to be thorough what I did was:
Some people use different machines or at least different containers per project, with different dependencies and even different operating systems. These differences may be unlikely to cause this issue but I am just trying to narrow down the reproduction.
If you want to try it out just to double-check whether it fixes the issue you can always move the directory to a new location then move it back afterward or point code-server to a temporary directory with something like But I am not sure that will do anything anyway. Whatever git command VS Code uses to get the file is probably failing. If you check the |
Beta Was this translation helpful? Give feedback.
-
I see, well, yes, all my projects are located on the same machine, a dedicated server, on which I use
No new line is added to that log when failing to preview/stage/unstage/undo changes. By the way, I also found another error appearing in DevTools while performing those actions : |
Beta Was this translation helpful? Give feedback.
-
|
So, cloning the project again was inconclusive : the issue persisted the first time, then didn't the next three times. 🤷 |
Beta Was this translation helpful? Give feedback.
-
Huh weird!
Maybe one of the earlier commands it ran to detect the repository failed, as that can cause a This may not be helpful at all but here is what I get on startup: Then once I open a diff: Sorry I am not able to be more helpful, but if you do manage to track down a reproduction I will jump on it. |
Beta Was this translation helpful? Give feedback.
-
I found no error in those logs :
That command works fine.
It looks like I'm never getting to this output though. Would you be interested in a remote control session ? |
Beta Was this translation helpful? Give feedback.
-
|
Right now that would be difficult but maybe in the coming weeks I could do that. If you were able to install local VS Code or use Codespaces and try the same that could help a lot since if it reproduces we could send this upstream and they have a lot more resources at their disposal to help with debugging. |
Beta Was this translation helpful? Give feedback.
-
Hello,
On a specific code-server project (i.e. other projects aren't affected), source control doesn't work anymore at all : I can't commit/push/pull/view changes.
However, those actions still work using the terminal.
The changelist is still displayed, but when clicking on a file :
The editor could not be opened because the file was not found.error is displayed in the UI ;Unable to read file 'git:<path>?{"path":"<path>","ref":"~"}' (Error: Unable to resolve nonexistent file 'git:<path>?{"path":"<path>","ref":"~"}')error is displayed in the console (with any file, despite they all exist).Nothing is printed server-side when performing this action, even in verbose mode.
I would have filed an issue but I can't figure out how to reproduce it and am not a VSCode user so I can't fill those.
Thanks
Beta Was this translation helpful? Give feedback.
All reactions