-
Notifications
You must be signed in to change notification settings - Fork 451
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 shared array access on init #2697
Conversation
Codecov Report
@@ Coverage Diff @@
## main #2697 +/- ##
==========================================
- Coverage 93.82% 93.78% -0.04%
==========================================
Files 75 76 +1
Lines 16148 16208 +60
==========================================
+ Hits 15151 15201 +50
- Misses 997 1007 +10 |
* Support no copy with StructuredGrid * Support no copy with RectilinearGrid * Improve convert_array to handle lists * raise on duplication * refactor * add check_duplicates option Co-authored-by: Alex Kaszynski <akascap@gmail.com>
I'm working to wrap up https://github.com/pyvista/pyvista-xarray and need this to merge and patch release as soon as we can |
Per our agreement in our release discussion, we should give everyone 24 hours to review. However, I'm good to merge this sooner if critical. |
My docstring changes seem to break docstring testing, but the failure seems to be in jupyter places(?) and I can't reproduce it locally. Actually, things are falling apart everywhere in CI. What did I break?! 😄 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@akaszynski we're almost done here:
- One discussion about copy=False change, seems resolved to me.
- One discussion about fixing up StucturedGrid's
__init__()
and docs, for which I've opened Clean up StructuredGrid documentation and __init__() #2733 - Fix shared array access on init #2697 (comment) which needs input.
Approving anyway because 3. is still correct as is.
Co-authored-by: Andras Deak <adeak@users.noreply.github.com>
I think this is resolved as-is given @MatthewFlamm's comment:
Furthermore, I'm only seeing one "filter" using this
That indeed needs to be cleaned up, but outside this PR.
Resolved in e552144. Thanks for pointing this out! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Still LGTM.
Resolve #2696, depends on #2698, and generally improves how meshes are created without copying source data when possible
@MatthewFlamm, please review as this is a follow up to your #2070
I'd like to add some more/better tests for this scenario
Memory usage comparison