Skip to content

In case of misconfiguration of dataset.encoding unlimited_dims warn instead of raise #10648

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

Merged
merged 4 commits into from
Aug 18, 2025

Conversation

kmuehlbauer
Copy link
Contributor

@kmuehlbauer kmuehlbauer commented Aug 16, 2025

ping @xylar

Copy link

@xylar xylar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@kmuehlbauer, yes this solves the issue reported in #10647. Thanks very much!

When I run my reproducer from that issue, I now see:

$ ./reproducer.py 
/home/xylar/Desktop/reproducer/tmp/./reproducer.py:25: UserWarning: Unlimited dimension(s) {'time'} declared in 'dataset.encoding', but not part of current dataset dimensions. Consider removing {'time'} from 'dataset.encoding'.
  ds0.to_netcdf('dataset_time0.nc')

@kmuehlbauer
Copy link
Contributor Author

Thanks @xylar, for confirming, much appreciated. Trying to finish this up later today.

@kmuehlbauer kmuehlbauer enabled auto-merge (squash) August 18, 2025 05:55
@kmuehlbauer kmuehlbauer merged commit e3359bc into pydata:main Aug 18, 2025
35 of 36 checks passed
@kmuehlbauer kmuehlbauer deleted the fix-unlimited_dims branch August 18, 2025 06:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

ds.encoding['unlimited_dims'] not getting updated properly
3 participants