-
-
Notifications
You must be signed in to change notification settings - Fork 80
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 broken #374
Comments
Support for defining tasks in your tasks.json was added only recently and does not work in 0.9, yet. We will need to release a new version for this to work. @cameron-martin do you have any thoughts on when we should cut the next release? I think we have enough new functionality by now such that a new release is worth it. Maybe we should still try to get #372 merged before cutting the release (it's essentially a rather straightforward 10-line change), but that's purely optional. At the same time, I think it would make sense to cut the release before merging #366. #366 bumps the required VSCode version. By cutting a release before doing the version bump, users on older VS Code versions will still be able to profit from all the other improvements |
Ahh you're right. |
Amazing! Thank you 🙂 |
I'm still seeing this issue in 0.10.0 using a Mac as client, editing a Bazel project on a Linux server. Builds via the "Bazel Build Targets" pane work fine, but I cannot turn these into tasks in tasks.json. When I try to re-run a build using "Run Task" I receive the following error:
What debugging info would be helpful for me to provide? |
When running "bazel" tasks the the "run task" menu I get the following error:
Using VSCode 1.88, and Bazel Extension 0.9.0 (latest in extension market place).
The text was updated successfully, but these errors were encountered: