- 
                Notifications
    You must be signed in to change notification settings 
- Fork 64
fix findmin/findmax #93
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
Conversation
| Codecov Report
 @@           Coverage Diff           @@
##             main      #93   +/-   ##
=======================================
  Coverage   89.18%   89.18%           
=======================================
  Files           7        7           
  Lines        5677     5679    +2     
=======================================
+ Hits         5063     5065    +2     
  Misses        614      614           
 📣 Codecov can now indicate which changes are the most critical in Pull Requests. Learn more | 
| Error seems unrelated | 
| 404 error is unrelated | 
| looks like that logic is flawed | 
cf062ab    to
    9cf449e      
    Compare
  
    Co-authored-by: Steven G. Johnson <[email protected]>
| @dkarrasch, I didn't realize you did not have merge access here. I think you should have gotten an invite now. | 
| @KristofferC I think I already had merge access, I was just a bit hesitant to push the button. Tests pass, which is good, but I haven't completely understood the originally missing case here. | 
| 
 Your approve symbol was gray which I thought typically means that the person reviewing does not have merge rights. It is green now, however. | 
| The missing case is when the sparse vector is filled with value from the beginning but not all the way to the end. The original "find first non-stored zero" rely on there existing a gap in the stored values | 
| Thanks for the fix! Now, how do we make sure this enters julia v1.8? | 
| something like this: | 
| Alright, so the bot will jump in at some point. | 
| idk if the backport to 1.8 will have to be manual though @DilumAluthge | 
| did we ever back port this? | 
| The backport to  To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-1.8 1.8
# Navigate to the new working tree
cd .worktrees/backport-1.8
# Create a new branch
git switch --create backport-93-to-1.8
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick --mainline 1 352dfafd4a31782c316c6aac69806336b979922c
# Push it to GitHub
git push --set-upstream origin backport-93-to-1.8
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-1.8Then, create a pull request where the  | 
Co-authored-by: Steven G. Johnson <[email protected]>
Co-authored-by: Steven G. Johnson <[email protected]>
Co-authored-by: Steven G. Johnson <[email protected]>
fixes JuliaLang/julia#44978