Skip to content
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

fix(Context.Run): Don't panic on unselected root node #484

Merged
merged 1 commit into from
Jan 4, 2025

Conversation

abhinav
Copy link
Contributor

@abhinav abhinav commented Jan 3, 2025

Fixes bug introduced in 2544d3f.

That commit refactored control flow slightly and missed a case
where the selected node is an application node but it does not
have a Run method.

The fix was straightforward:
Treat the "if application node" code path as a possible way to fill
node, and check it again afterwards.

Resolves #483

Fixes regression introduced in 2544d3f.

That commit refactored control flow slightly and missed a case
where the selected node is an application node but it does not
have a Run method.

The fix was straightforward:
Treat the "if application node" code path as a possible way to fill
`node`, and check it again afterwards.

Resolves alecthomas#483
@abhinav abhinav force-pushed the panic-on-empty-run branch from 16403e3 to 4e96b85 Compare January 3, 2025 21:48
@alecthomas alecthomas merged commit 7ca8467 into alecthomas:master Jan 4, 2025
5 checks passed
@alecthomas
Copy link
Owner

Thanks!

@abhinav
Copy link
Contributor Author

abhinav commented Jan 6, 2025

Thanks for merging, @alecthomas!
Would you be willing to tag a release with this soon-ish?

@alecthomas
Copy link
Owner

Done!

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 Run with no selected nodes
2 participants