internal/cmd/cue-ast-print: fix panic when printing the ast tree #2771
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.
Panic was observed when running cue-ast-print 2567.slice.1.cue or similar cue samples.
This commit fixes the problem by moving the test
if !v.IsValid(){...}
a few lines up, to prevent referencing a nil pointer.The script issue-panic.txtar verifies that cue-ast-print works after this fix.
Running the script with a build of cue-ast-print before the fix demonstrates the panic about half-way into the printing.