Work around xarray StringDType serialization error#1086
Merged
Conversation
Arcomano1234
approved these changes
Apr 24, 2026
Contributor
Arcomano1234
left a comment
There was a problem hiding this comment.
LGTM, thanks for quickly spotting this.
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
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.
The evaluator integration test on beaker failed with the following error:
Details
This should be fixed in the next release of xarray (pydata/xarray#11218), but for the time being we can work around it with the code in this PR.
Changes:
Modifies the way we assign
"source"coordinate values to the dataset constructed inPairedSphericalPowerSpectrumAggregator.get_datasetsuch that they are of a unicode dtype rather than a string dtype.Tests added