Open eetupulkkinen opened 1 month ago
vs-code-engineering[bot]
commented
1 month ago Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.93.1. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!
unional
commented
1 month ago Notice the same issue. Need to manually click on the source control refresh button.
xy-23
commented
1 month ago same issue
Version: 1.94.0
Commit: d78a74bcdfad14d5d3b1b782f87255d802b57511
Date: 2024-10-02T13:08:12.626Z
Electron: 30.5.1
ElectronBuildId: 10262041
Chromium: 124.0.6367.243
Node.js: 20.16.0
V8: 12.4.254.20-electron.0
OS: Darwin arm64 23.6.0
lszomoru
commented
1 month ago Please use the steps documented on the wiki to collect file watcher logs.
unional
commented
1 month ago I followed the steps and there are no "File Watcher" trace log.
Here are some of the logs without the filter:
TRACE MainThreadFileSystemEventService#$watch(): request to start watching uncorrelated (extension: vscode.git, path: file:///Users/hwong/pan/panwds/.git/refs/remotes/origin/r18, recursive: false, session: 0.26773984001931006, excludes: [], includes: ["**/.git/objects/**/**","**/.git/subtree-cache/**/**","**/.hg/store/**/**","**/.ammonite/**","**/.bloop/**","**/.metals/**"])
...
TRACE MainThreadFileSystemEventService#$unwatch(): request to stop watching (session: 0.26773984001931006)
TRACE MainThreadFileSystemEventService#$watch(): request to start watching uncorrelated (extension: vscode.git, path: file:///Users/hwong/pan/panwds/.git/refs/remotes/origin/r18, recursive: false, session: 0.37957066930119954, excludes: [], includes: ["**/.git/objects/**/**","**/.git/subtree-cache/**/**","**/.hg/store/**/**","**/.ammonite/**","**/.bloop/**","**/.metals/**"])
...
TRACE MainThreadFileSystemEventService#$unwatch(): request to stop watching (session: 0.37957066930119954)
TRACE MainThreadFileSystemEventService#$watch(): request to start watching uncorrelated (extension: vscode.git, path: file:///Users/hwong/pan/panwds/.git/refs/remotes/origin/r18, recursive: false, session: 0.8190720025735565, excludes: [], includes: ["**/.git/objects/**/**","**/.git/subtree-cache/**/**","**/.hg/store/**/**","**/.ammonite/**","**/.bloop/**","**/.metals/**"])I'm following the local steps. Running on MacOS, not on Docker or remote.
viktorrenkema
commented
1 month ago I had this too, and found out that it was caused by the same issue described here: https://github.com/microsoft/vscode/issues/201099#issuecomment-1909545629.
tldr, branch name is too long. try these settings or better, rename the branch:
"scm.showIncomingChanges": false
"scm.showOutgoingChange": false,
unional
commented
1 month ago Um...for me, it is not related to branch name. I work on main.
eetupulkkinen
commented
1 month ago Please use the steps documented on the wiki to collect file watcher logs.
I've been trying to cause the bug so I could get you some trace logs, but this bug hasn't occured to me in a week, which is weird. I'll get back to this issue as soon as the bug occurs again. But 'nice' to see that I am not the only one with this bug.
Thanks for the replies.
I had this too, and found out that it was caused by the same issue described here: #201099 (comment).
tldr, branch name is too long. try these settings or better, rename the branch:
"scm.showIncomingChanges": false"scm.showOutgoingChange": false,
My branch names are not too long either, since it's something like xxx-yyyy.
eetupulkkinen
commented
1 month ago Now I got this bug to occur.
As mentioned before by @unional , no logs showing with 'File Watcher' filter on. Removed the filter. I tried saving a file that wouldn't turn yellow, and got bunch of logs, but this is the most interesting one
TRACE [text file model] handleSaveSuccess(102) - setting dirty to false because versionId did not change
I also have one bugged file that shows yellow (as changed) but it doesnt add my new changes to vscode version control. Tried saving the file and it said the exactly same log.
TRACE [text file model] handleSaveSuccess(646) - setting dirty to false because versionId did not change
thernstig
commented
4 weeks ago I am having this issue as well, but I can see the file changed in the Explorer view. It is yellow and shows the number of changes in the file.
The problem is that it does not immediately show up in the Source Control view. It does show up if I click refresh.
I am using WSL, so I wonder if it has something to do with that?
@lszomoru please note that the file watching issues wiki seems to contain a bug, so it is hard to know which output channel to view. See https://github.com/microsoft/vscode/issues/232715.
edit: I just rebooted my WSL machine, and it reinstalled a new version of VS Code server. I also restarted my computer. After that, everything worked. Unfortunately I did not get a chance to get trace logs before this. So if this was an intermittent issue that can occur, I have no way to prove it now.
thernstig
commented
3 weeks ago There is a definitely a bug here. I am using Windows 11 with WSL2 enabled. After my computer comes back from hibernation, any changes made does not automatically show up in the Source Control view. I have to press the refresh icon in that view for changes to show up. The logs however seem to show that it sees the change, as seen at the bottom of the logs below. It just does not show up in the Source Control view.
Note that there is a ton of issue reported on this: https://github.com/microsoft/vscode/issues?q=is%3Aissue%20state%3Aopen%20source%20control%20refresh. In addition, git status clearly shows the files changed.
There is no problem visible in the Server output channel after having enabled trace logs.
2024-11-04 13:12:44.779 [trace] Log level changed to trace
2024-11-04 13:12:44.784 [trace]
[File Watcher] request stats:
[Summary]
- Recursive Requests: total: 1, suspended: 0, polling: 0, failed: 0
- Non-Recursive Requests: total: 0, suspended: 0, polling: 0
- Recursive Watchers: total: 1, active: 1, failed: 0, stopped: 0
- Non-Recursive Watchers: total: 0, active: 0, failed: 0, reusing: 0
- I/O Handles Impact: total: 1
[Recursive Requests (1, suspended: 0, polling: 0)]:
/home/tobias/code/c-test (excludes: **/.git/objects/**,**/.git/subtree-cache/**,**/.hg/store/**,/home/tobias/.vscode-server/extensions/**, includes: <all>, filter: <none>, correlationId: <none>)
[Recursive Watchers (1, active: 1, failed: 0, stopped: 0)]:
/home/tobias/code/c-test (excludes: **/.git/objects/**,**/.git/subtree-cache/**,**/.hg/store/**,/home/tobias/.vscode-server/extensions/**, includes: <all>, filter: <none>, correlationId: <none>)
[Non-Recursive Requests (0, suspended: 0, polling: 0)]:
[Non-Recursive Watchers (0, active: 0, failed: 0, reusing: 0)]:
2024-11-04 13:12:58.414 [trace] [File Watcher ('parcel')] [CHANGED] /home/tobias/code/c-test/src/helloworld.c
2024-11-04 13:12:58.465 [trace] [File Watcher ('parcel')] [CHANGED] /home/tobias/code/c-test/src/helloworld.c
2024-11-04 13:12:58.490 [trace] [File Watcher ('parcel')] >> normalized [CHANGED] /home/tobias/code/c-test/src/helloworld.c@lszomoru what else can I do to help here, I am willing to do more extensive troubleshooting. This is detrimental almost to the point of non-workable working with VS Code for WSL remotes when this happens.
Note that I have done an extension bisect. It failed on the first step with all extensions disabled, indicating this is a core VS Code problem.
VS Code version: Code 1.95.0 (912bb683695358a54ae0c670461738984cbb5b95, 2024-10-28T20:16:24.561Z) OS version: Windows_NT x64 10.0.22631 Modes: Remote OS version: Linux x64 5.15.153.1-microsoft-standard-WSL2
thernstig
commented
1 week ago @lszomoru this is quite a severe bug/problem working under WSL, could you please look into this? It makes it impossible to work efficiently.
lszomoru
commented
4 hours ago @thernstig, sorry for not getting back to you on this until now. Reading through the comments and the logs it seems to me that right now you have a consistent way to reproduce this issue. Could you please confirm that you are able to repro every time the machine comes out of hibernation? Looking at the logs it seems that when you are reproducing the problem you are storing the workspace file in the WSL file system (ex: /home/tobias...) rather than the Windows file system. Could you please also confirm that. Would you be able to share your power management settings to see if I am able to reproduce this on my windows machine along with the exact WSL distro and version that you are using?
Let's keep the verbose logs on, and also enable verbose logs for the vscode.git extension:
Reproduce the issue and share the file watcher logs and the contents of the git output channel. Thanks!
Type: Bug
I don't know a sure way to reproduce the bug. What happens is that I need to 'reload' my vscode daily, usually multiple times.
Usually it happens after pushing my changes to source control, or changing branches.
What happens is that I make file changes and save the file, the file name doesn't turn yellow and the changed file doesnt pop up in source control. It is fixed by using 'Developer: Reload Window' function in vscode, but it's annoying to do multiple times in a single session.
VS Code version: Code 1.93.0 (4849ca9bdf9666755eb463db297b69e5385090e3, 2024-09-04T13:02:38.431Z) OS version: Darwin arm64 23.6.0 Modes:
System Info
|Item|Value| |---|---| |CPUs|Apple M2 Pro (12 x 2400)| |GPU Status|2d_canvas: enabledcanvas_oop_rasterization: enabled_on
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_graphite: disabled_off
video_decode: enabled
video_encode: enabled
webgl: enabled
webgl2: enabled
webgpu: enabled
webnn: disabled_off| |Load (avg)|1, 2, 2| |Memory (System)|32.00GB (0.08GB free)| |Process Argv|--crash-reporter-id 7addafe9-5ed2-4532-af0c-ae917adae4a6| |Screen Reader|no| |VM|0%|
Extensions (16)
Extension|Author (truncated)|Version ---|---|--- vscode-apollo|apo|2.3.3 atlascode|atl|3.0.10 vscode-tailwindcss|bra|0.12.11 javascript-ejs-support|Dig|1.3.3 xml|Dot|2.5.1 gitlens|eam|15.5.1 prettier-vscode|esb|11.0.0 copilot|Git|1.235.0 copilot-chat|Git|0.20.3 vscode-docker|ms-|1.29.3 playwright|ms-|1.1.7 vscode-thunder-client|ran|2.27.0 vscode-yaml|red|1.15.0 ejs-snippets|Tao|0.1.0 pdf|tom|1.2.2 pretty-ts-errors|Yoa|0.6.0A/B Experiments
``` vsliv368cf:30146710 vspor879:30202332 vspor708:30202333 vspor363:30204092 vscod805cf:30301675 binariesv615:30325510 vsaa593cf:30376535 py29gd2263:31024239 c4g48928:30535728 azure-dev_surveyone:30548225 2i9eh265:30646982 962ge761:30959799 pythongtdpath:30769146 welcomedialog:30910333 pythonnoceb:30805159 asynctok:30898717 pythonmypyd1:30879173 2e7ec940:31000449 pythontbext0:30879054 accentitlementst:30995554 dsvsc016:30899300 dsvsc017:30899301 dsvsc018:30899302 cppperfnew:31000557 dsvsc020:30976470 pythonait:31006305 dsvsc021:30996838 bdiig495:31013172 a69g1124:31058053 dvdeprecation:31068756 dwnewjupyter:31046869 newcmakeconfigv2:31071590 impr_priority:31102340 nativerepl2:31139839 refactort:31108082 pythonrstrctxt:31112756 flighttreat:31134774 wkspc-onlycs-t:31132770 nativeloc2:31134642 wkspc-ranged-t:31125599 cf971741:31144450 defaultse:31146405 notype1:31150297 5fd0e150:31146321 ```