-
Notifications
You must be signed in to change notification settings - Fork 30.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Build task not detected sometimes #173184
Comments
Pls comment if you find a way to repro this |
@meganrogge I really don't. Ran into this twice in last two weeks, is there any log to check if I run into this again? |
Oh nice, same here! I think this happens when I manage to rerun build tasks (the default build task of vscode) right after window reload, very early while the workbench is loading up. |
Yeah it takes some time to resolve workspace tasks, so if you run it too early, it makes sense that you'd see this happen. We don't want to prevent the workbench from starting up, so not sure what could be done here |
I should also mention that when this happens, it does not "just work" when I wait longer. So at that point, I see the picker appearing even later. Not sure if that is explainable. |
@meganrogge for me it still doesn't work after waiting for 10 seconds or so. I would expect the workbench to finish and we have parsed the |
Looked at your gif again @rebornix and I noticed that you only have What that means looking at the code is that vscode/src/vs/workbench/contrib/tasks/browser/abstractTaskService.ts Lines 2618 to 2633 in beea143
|
So I think what's happening is the tasks.json file has been parsed but the task hasn't been fully resolved yet |
@meganrogge this happened again today, and VS Code has been already running for half a day. Here are the trace logs related to Tasks but they don't seem to be helpful.
|
this is probably the root cause #173384 |
Thank you for your patience - I will try to work on this in April |
/duplicate #173384 |
Issue marked as unreleased but unable to locate closing commit in issue timeline. You can manually reference a commit by commenting |
/duplicate #173384 |
Type: Bug
I sometimes ran into this issue where cmd+shift+b stops runnings build task for me for VS Code repo automatically.
Screen.Recording.2023-02-02.at.10.53.13.AM.mov
VS Code version: Code - Insiders 1.75.0-insider (Universal) (e2816fe, 2023-02-01T15:16:42.458Z)
OS version: Darwin x64 22.3.0
Modes:
Sandboxed: Yes
System Info
canvas_oop_rasterization: disabled_off
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
metal: disabled_off
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_renderer: enabled_on
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: disabled_off
Extensions (95)
(7 theme extensions excluded)
A/B Experiments
The text was updated successfully, but these errors were encountered: