-
Notifications
You must be signed in to change notification settings - Fork 59
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
--useCquery probably incorrectly handles SOURCE_FILE's #218
Comments
Maybe due to
|
@tinder-maxwellelliott I think this might be indeed an issue. Not only source files, but also generated files are filter out because of empty |
I think we might just convert |
@honnix Id be open to a PR for this to see what the impact is |
I put up something quickly in #251 |
Hi!
I noticed a difference in behavior between the cquery and query implementations - on the same repository (bazel-diff-sample.zip), we get different results.
The example is quite simple: target B depends on the source file A.cc through the sample_repo local repository and target A.
Query returns significantly more targets than cquery (with the
--fineGrainedHashExternalRepos=sample_repo
flag specified in both cases), when A.cc is modified.cquery:
query:
It is possible that the tool with the --useCquery flag is not working correctly. My suspicion falls on these two (1, 2) code fragments, where almost all sources are implicitly filtered out from the target list because SOURCE_FILE has empty
rule.name
. Which leads to warnings like:And there is no similar filtration performed when the tool is run in query mode. Sorry in advance if I somehow misunderstood this code or idea behind it, but results seem a little bit strange.
The text was updated successfully, but these errors were encountered: