fix: use --build_event_binary_file for lint command #251
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jbedard
force-pushed
the
869-proxy-via-socket
branch
from
cfaf2fe to
0e37520
Compare
thesayyn
reviewed
Oct 10, 2025
jbedard
force-pushed
the
869-proxy-via-socket
branch
from
0e37520 to
db4a7e7
Compare
thesayyn
approved these changes
Oct 10, 2025
jbedard
force-pushed
the
869-proxy-via-socket
branch
from
db4a7e7 to
f8ff0f8
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Switch the
lintcommand to use a new--build_event_binary_file-based source of BES info to avoid all the--bes_backendproxying complications and bugs.We may want to replace all
--bes_backendusage, for now we'll only dolint.Fix #5
Changes are visible to end-users: no
Test plan