fix infinite loop due to panic from bare .unwrap
of a Result
in create_digests
intrinsic
#21746
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.
While investigating #21709, the investigation was obscured by the fact that the issue manifested as a panic in the
create_digests
intrinsic. The error was in theErr
variant of aResult
which thecreate_digests
blindly called.unwrap()
on, which of course panics by design.This panic resulted in the engine retrying the build graph node at issue and hitting the panic again ... and again ... and again ...
The engine should really stop if it encounters a panic from a node computation, but in the meantime, the
create_digests
should just return errors inResult
instances instead of panicking.