Skip to content

Ensure all nan-slice warnings are caught#1941

Merged
psavery merged 1 commit intomasterfrom
catch-nan-slice-warnings
Feb 25, 2026
Merged

Ensure all nan-slice warnings are caught#1941
psavery merged 1 commit intomasterfrom
catch-nan-slice-warnings

Conversation

@psavery
Copy link
Collaborator

@psavery psavery commented Dec 5, 2025

They were not always being caught with the previous setup, but this catches them all.

@psavery psavery requested a review from saransh13 December 5, 2025 22:00
@saransh13
Copy link
Member

saransh13 commented Dec 6, 2025

issue still persists on Mac. However, the issue goes away when the solid angle intensity corrections are turned off. Must have something to do with that part of the code.

@psavery
Copy link
Collaborator Author

psavery commented Dec 15, 2025

Please let me know if this issue is now gone after all of the latest updates. You can try both with this branch and without this branch. If it still persists... I'll look into it more.

@saransh13
Copy link
Member

Still persisting, unfortunately.

@saransh13 saransh13 force-pushed the catch-nan-slice-warnings branch from 0336f0f to 774e574 Compare December 15, 2025 23:44
Signed-off-by: Patrick Avery <patrick.avery@kitware.com>
@psavery psavery force-pushed the catch-nan-slice-warnings branch from 774e574 to 43c16a8 Compare February 25, 2026 04:30
@psavery
Copy link
Collaborator Author

psavery commented Feb 25, 2026

I'm hopeful this fix should work. Let me know if it doesn't.

Copy link
Member

@saransh13 saransh13 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

most recent change fixed the issue. LGTM

@psavery psavery merged commit ff27fdd into master Feb 25, 2026
10 checks passed
@psavery psavery deleted the catch-nan-slice-warnings branch February 25, 2026 21:02
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.

2 participants