-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Add support for --keep_going
to bazel mod
#23828
Conversation
@bazel-io fork 8.0.0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks a lot!!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the change overall LGTM. I'm just wondering if we need to check for --keep_going
at all. While digging through the code, I found that SkyframeExecutor.prepareAndGet
which is used by ModCommand
actually always sets "keep going" to true. This makes me wonder if there's ever a case where we don't want to "keep going". WDYT?
8d7417e
to
4cbbc54
Compare
b82387e
to
4cbbc54
Compare
4cbbc54
to
a2e0597
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks, this looks great! just one last question.
@@ -194,6 +193,7 @@ private BlazeCommandResult execInternal(CommandEnvironment env, OptionsParsingRe | |||
EvaluationContext.newBuilder() | |||
.setParallelism(threadsOption.threads) | |||
.setEventHandler(env.getReporter()) | |||
.setKeepGoing(options.getOptions(KeepGoingOption.class).keepGoing) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder if we should just set this to true unconditionally. After all, it's been the case so far, and IMO for an informational subcommand like bazel mod
, most people would want to set --keep_going
as a default.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
While it's technically been enabled so far, I don't think that it had any effect in practice since the relevant SkyFunction
s are not catching errors. But I still agree that bazel mod
commands should probably keep going by default. I've also implemented this for bazel mod tidy
.
fb6b76c
to
4a69c89
Compare
RELNOTES: `bazel mod` now tries to evaluate all module extensions, even when some have failed to evaluate. Closes bazelbuild#23828. PiperOrigin-RevId: 694448503 Change-Id: I1e4f7a36384c7dfdc16d13cdfcd0b4b3aeb41834
RELNOTES: `bazel mod` now tries to evaluate all module extensions, even when some have failed to evaluate. Closes bazelbuild#23828. PiperOrigin-RevId: 694448503 Change-Id: I1e4f7a36384c7dfdc16d13cdfcd0b4b3aeb41834
RELNOTES:
bazel mod
now skips over extensions that failed to evaluate when used with--keep_going
.