-
Notifications
You must be signed in to change notification settings - Fork 121
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
ibazel ought to use CQuery instead of regular query #594
Comments
I believe ac2ce9f might have broken something with ibazel. I'm seeing this error when running ibazel:
I believe this means that ibazel will not reload if there are changes to BUILD / bzl files that affect the watched target. I believe the issue is that The fix is to have this query still use query, rather than cquery: bazel-watcher/internal/ibazel/ibazel.go Line 309 in 8af081f
|
same here! |
Same error here. Any chance we could rollback the change @achew22 ? |
Yeah, let's roll it back |
Looks like there may be more complexity here than initially thought. Rolling back to restore functionality. Thanks for the reporting everyone! |
This issue should be reopened. The cache invalidation issue still exists |
Stale issue message |
This takes antoher stub at bazelbuild#594 by introducing cquery back in. In difference to the previous attempt this splits up the resolving of buildfiles. CQuery does not support buildfiles but without cquery bazel-watcher could watch files which are not reflected in the build for e.g. dependencies behind a select statement. In order to avoid depending on such cases first a cquery is issued which resolves dependencies of selected targets. These dependencies are then injected into the buildfiles query in order to get dependent build files. Signed-off-by: Tobias Kohlbau <tobias@kohlbau.de>
This takes antoher stub at bazelbuild#594 by introducing cquery back in. In difference to the previous attempt this splits up the resolving of buildfiles. CQuery does not support buildfiles but without cquery bazel-watcher could watch files which are not reflected in the build for e.g. dependencies behind a select statement. In order to avoid depending on such cases first a cquery is issued which resolves dependencies of selected targets. These dependencies are then injected into the buildfiles query in order to get dependent build files. Signed-off-by: Tobias Kohlbau <tobias@kohlbau.de>
This takes antoher stub at bazelbuild#594 by introducing cquery back in. In difference to the previous attempt this splits up the resolving of buildfiles. CQuery does not support buildfiles but without cquery bazel-watcher could watch files which are not reflected in the build for e.g. dependencies behind a select statement. In order to avoid depending on such cases first a cquery is issued which resolves dependencies of selected targets. These dependencies are then injected into the buildfiles query in order to get dependent build files. Signed-off-by: Tobias Kohlbau <tobias@kohlbau.de>
This takes antoher stub at bazelbuild#594 by introducing cquery back in. In difference to the previous attempt this splits up the resolving of buildfiles. CQuery does not support buildfiles but without cquery bazel-watcher could watch files which are not reflected in the build for e.g. dependencies behind a select statement. In order to avoid depending on such cases first a cquery is issued which resolves dependencies of selected targets. These dependencies are then injected into the buildfiles query in order to get dependent build files. Signed-off-by: Tobias Kohlbau <tobias@kohlbau.de>
This takes antoher stub at bazelbuild#594 by introducing cquery back in. In difference to the previous attempt this splits up the resolving of buildfiles. CQuery does not support buildfiles but without cquery bazel-watcher could watch files which are not reflected in the build for e.g. dependencies behind a select statement. In order to avoid depending on such cases first a cquery is issued which resolves dependencies of selected targets. These dependencies are then injected into the buildfiles query in order to get dependent build files. Signed-off-by: Tobias Kohlbau <tobias@kohlbau.de>
This takes antoher stub at bazelbuild#594 by introducing cquery back in. In difference to the previous attempt this splits up the resolving of buildfiles. CQuery does not support buildfiles but without cquery bazel-watcher could watch files which are not reflected in the build for e.g. dependencies behind a select statement. In order to avoid depending on such cases first a cquery is issued which resolves dependencies of selected targets. These dependencies are then injected into the buildfiles query in order to get dependent build files. Signed-off-by: Tobias Kohlbau <tobias@kohlbau.de>
Describe the bug
Running
bazel build <target>
thenbazel query <target>
invalidates the cache sometimes becausebazel query
doesn't consider select statements.Reproduction instructions
Any repo with a target with select statements. Run the above commands and see the cache is invalidated.
Expected behavior
The cache should not be invalidated. This leads to really long boot up times.
Version (please complete the following information):
MacOS 13.3
v0.16.2
6.1.0
The text was updated successfully, but these errors were encountered: