Skip to content

Fix: propagate NaN when dealing with cummax and curmin - #4047

Open
JasonHonKL wants to merge 7 commits into
ml-explore:mainfrom
JasonHonKL:issue-4044
Open

Fix: propagate NaN when dealing with cummax and curmin#4047
JasonHonKL wants to merge 7 commits into
ml-explore:mainfrom
JasonHonKL:issue-4044

Conversation

@JasonHonKL

Copy link
Copy Markdown
Contributor

Proposed changes

Fix #4044

Checklist

Put an x in the boxes that apply.

  • I have read the CONTRIBUTING document
  • I have run pre-commit run --all-files to format my code / installed pre-commit prior to committing changes
  • I have added tests that prove my fix is effective or that my feature works
  • I have updated the necessary documentation (if needed)

@JasonHonKL
JasonHonKL marked this pull request as draft August 7, 2026 05:18
@JasonHonKL
JasonHonKL marked this pull request as ready for review August 7, 2026 05:25
@JasonHonKL

Copy link
Copy Markdown
Contributor Author

This PR is a bit large due to the test. The core change is around 30 to 40 Loc

@zcbenz zcbenz added the await verification This pull request is non-trivial and requires a human expert to verify its correctness. label Aug 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

await verification This pull request is non-trivial and requires a human expert to verify its correctness.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[BUG] mx.cummax / mx.cummin mishandle NaN: device-dependent (CPU ≠ GPU), leak ±∞, and disagree with NumPy

2 participants