Skip to content

Conversation

@rudo-thomas
Copy link
Contributor

The bug was that a non-nil error was not returned when the cached Node was returned. Fix: Just cache both.

The other possibility was not to cache when there is an error. But that broke a test in the linter.

Fixes #822

The bug was that a non-nil error was not returned when the cached Node
was returned. Fix: Just cache both.

The other possibility was not to cache when there is an error. But that
broke a test in the linter.

Fixes google#822
@johnbartholomew
Copy link
Collaborator

Thanks for the bug report, and the fix! This looks good, I'll just rebase it.

@johnbartholomew johnbartholomew force-pushed the rudo.thomas/fix-cached-import-syntax-error branch from 939a751 to 3d41737 Compare January 27, 2026 16:37
@coveralls
Copy link

Coverage Status

coverage: 44.168% (+0.06%) from 44.109%
when pulling 3d41737 on rudo-thomas:rudo.thomas/fix-cached-import-syntax-error
into 751aedf on google:master.

@johnbartholomew johnbartholomew merged commit 3d41737 into google:master Jan 27, 2026
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

panic on 0.21.0 when evaluating a file with a syntax error the second time in the same VM

3 participants