VSCode Version:
Version: 1.29.0 (user setup)
Commit: 5f24c93878bd4bc645a4a17c620e2487b11005f9
Date: 2018-11-12T07:47:15.448Z
Electron: 2.0.12
Chrome: 61.0.3163.100
Node.js: 8.9.3
V8: 6.1.534.41
Architecture: x64
OS Version: Windows 10 Professional 1809 (Build 17763.55)
Steps to Reproduce:
It's interesting that the "ASE" does not react when do the commit/update by using TortoiseSVN client or by typing commands in the terminal.
This problem is since the 1.29.0 update.
Does this issue occur when all extensions are disabled?: Yes.
Update:
So it seems nothing to do with shortcut keys 馃憞
(Experimental duplicate detection)
Thanks for submitting this issue. Please also check if it is already covered by an existing one, like:
@Monkey-D-Pixel is this happening every time. We see something comparable with gulp but only when starting the task the first time.
@Monkey-D-Pixel is this happening every time. We see something comparable with gulp but only when starting the task the first time.
yes, every time
might be a specific case of #63055, not just svn tasks
Adding @alexr00 since she is on #63055. How does the SVN task look like? Can you provide use with a GitHub repository we can clone that demos this?
One try. If you add the following settings
"npm.autoDetect": "off",
"gulp.autoDetect": "off",
"grunt.autoDetect": "off",
"jake.autoDetect": "off"
to the workspace settings does it still reproduce ?
@dbaeumer just user defined configurations in task.json, like this:
{
"taskName": "svn update",
"type": "shell",
"command": "svn update ${fileDirname} ",
"group": {
"kind": "svn",
"isDefault": true
}
}
It's still reproducing after adding those settings.
And just found more about this:
If I ctrl+p, select "Run task" in the command palette, MOSTLY "ASE" will also spike, while there is a loading indicator at the bottom of the palette until the tasks are loaded. Then I choose one, the task is invoked immediately. SOMETIMES, normally after several times of trying the same steps, the tasks are loaded very quickly, with "ASE" not spiking.
So I think there is something wrong during loading tasks.
I can repro. It does look as though something is very slow during loading tasks.
edit: Actually, I can only repro a slow down during the first time I load tasks after a window reload. @Monkey-D-Pixel, can you confirm whether you see the slowdown both times when you run the "Run Task" command, wait for it to load, then immediately run the "Run Task" command again?
I think the sequence is: (slow down and DOES NOT work) -> (slow down and work) -> (slow down and DOES NOT work) -> (slow down and work) -> ...
I forgot one task provider. Can you disable that one as well:
"typescript.tsc.autoDetect": "off"
@alexr00 Yes, slows down both times.
@dbaeumer Finally, NO MORE slow down with this line added. But why?
@Monkey-D-Pixel TypeScript provides task to build typescript project automatically and this seems to gotten slower in 1.29.
@mjbvz, any ideas on why the typescript task provider has gotten slower in 1.29?
Does this involve searching? Does it do a findFiles('**/tsconfig.json') or something? I've got #63070 and a couple others.
I forgot one task provider. Can you disable that one as well:
"typescript.tsc.autoDetect": "off"
Thx, it solved my problem #63026
I believe this is the same issue as https://github.com/Microsoft/vscode/issues/63055.
Yes, same root cause as #63070. The tsc task detector searches the workspace for all tsconfig.json files.
@roblourens for FYI.
Let's call this a dupe of #63070.
Most helpful comment
I forgot one task provider. Can you disable that one as well: