Fix FutureWarning when merging xarrays #507
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
There was a problem hiding this comment.
Pull request overview
This PR addresses a FutureWarning in xarray by explicitly specifying the compat parameter when merging datasets. The xarray library is changing its default merge behavior (ref: pydata/xarray PR 10062), and this fix prevents warnings by making the compatibility mode explicit.
Changes:
- Added explicit
compat="no_conflicts"parameter toxr.merge()call
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
yumouwei
approved these changes
Jan 21, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
default behavior of
xr.mergewill change (ref: pydata/xarray PR 10062), so let's silence the warning with an explicitcompatassignment.