Use --output=streamed_proto if supported

[fmeum]

This avoids reading a single giant proto message with all configured targets. Instead, Bazel streams out invidual length-delimited configured target protos, which is more memory efficient and also supports result sizes > 2GB.

[fmeum]

@sitaktif Ready for review now, I had to run go mod tidy

[illicitonion]

Thanks!

[honnix]

I tried the HEAD of main branch but got this error failed to unmarshal streamed cquery stdout: proto: cannot parse invalid wire-format data, which seems to be caused by this change. I will see whether I could get more error messages.

[honnix]

I tried the HEAD of main branch but got this error failed to unmarshal streamed cquery stdout: proto: cannot parse invalid wire-format data, which seems to be caused by this change. I will see whether I could get more error messages.

@fmeum Have you got time to take a look at this? Thank you.

[fmeum]

@honnix How are you using target-determinator? Can you reproduce this on a small project?

[honnix]

@honnix How are you using target-determinator? Can you reproduce this on a small project?

Very basic usage of target-determinator. I tested using this command /path/to/target-determinator.darwin.arm64 --enforce-clean=enforce-clean --targets='//...'.

That said we have tons of stuff in .bazelrc. I will try to come up with a repro.

[honnix]

Actually if I try to upgrade bazel used by this repo to 8.4.0, I could already see the same issue.

[fmeum]

Actually if I try to upgrade bazel used by this repo to 8.4.0, I could already see the same issue.

Did this happen when you run the tests? I can't reproduce the issue in that way. I haven't used target-determinator yet, so if you can share the exact command to run on its repo, that would be appreciated. :-)

[honnix]

Sure.

• Upgrade bazel to 8.4.0 (actually any version supporting streamed proto) in .bazelversion, commit the change
• bazel build //target-determinator
• bazel-bin/target-determinator/target-determinator_/target-determinator --enforce-clean=enforce-clean --targets="//target-determinator" HEAD~1

[honnix]

Did this happen when you run the tests?

No it doesn't happen with tests because I think everything is running under Bazel 7.5.0:

target-determinator/.bazelversion

Line 1 in 1e25331

7.5.0

[fmeum]

@honnix Sent #120, could you test it?

[honnix]

@honnix Sent #120, could you test it?

That makes a lot of sense. I will test it asap.

[honnix]

@honnix Sent #120, could you test it?

@fmeum I can confirm this fixes the issue. Thank you for the fix.