If we fail to lock, include the config #463
Merged
+11
−2
Conversation
This file contains 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
imjasonh
approved these changes
Feb 14, 2025
It's nearly impossible to get at the config that failed if we fail to lock (because we won't have a plan to inspect), so we'll include the input config in the diagnostic details to make this at least possible. Signed-off-by: Jon Johnson <[email protected]>
jonjohnsonjr
force-pushed
the
include-config-in-lock-failures
branch
from
5c2b5f3 to
6d53fb8
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
It's nearly impossible to get at the config that failed if we fail to lock (because we won't have a plan to inspect), so we'll include the input config in the diagnostic details to make this at least possible.