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
Tasks (and TaskExecutions) are not === in the onDid(Start|End)Task callbacks. #96643
Comments
I also checked Insiders for 1.45 and it also fails to compare the Task and TaskExecution objects in onDid(Start|End)TaskProcess callbacks. |
Related bug for TaskExecutions being comparable #47465 |
This bug actually completely broke our extension. Is the milestone to fix this still May 2020? This is very blocking, especially since otherwise there is no way to wait for a task to be done and then do something with the result of that task. |
@ashgti and @ThadHouse I have pushed a fix that solves the task executions not being equal. If you can, please install the insiders build tomorrow and verify that the issue you were seeing is resolved. If you still see a problem with the next insiders build, please let me know as soon as possible so I can have time to fix it before the next release. |
Works for me! Thanks! |
Added an API test. |
After moving some code around in my extension, i'm seeing the race condition again. I've added some details to #98080 (comment) |
Steps to Reproduce:
yo code
.If you break inside the onDidStartTaskProcess and onDidEndTaskProcess that comparison fail, which means its difficult to determine when the task starts or ends.
It's worth noting that in VSCode 1.43 the above comparisons both work, but in 1.44 this is not working.
Does this issue occur when all extensions are disabled?: Yes
The text was updated successfully, but these errors were encountered: