Skip to content

Conversation

dstansby
Copy link
Contributor

This makes sure the chunk shape is the chunk shape, and not the shard shape. I'm not sure why the chunk shape was being set to the shard shape, but I am worried this is going to break things, or at least pulling on this might result in a bit of a mess 😬

This is the root cause of, and fixes #3221

TODO:

  • Add unit tests and/or doctests in docstrings
  • Add docstrings and API docs for any new/modified user-facing classes and functions
  • New/modified features documented in docs/user-guide/*.rst
  • Changes documented as a new file in changes/
  • GitHub Actions have all passed
  • Test coverage is 100% (Codecov passes)

@github-actions github-actions bot added the needs release notes Automatically applied to PRs which haven't added release notes label Jul 15, 2025
@dstansby
Copy link
Contributor Author

Okay, I went further down the rabbit hole and this isn't the correct fix.

@dstansby dstansby closed this Jul 15, 2025
@d-v-b
Copy link
Contributor

d-v-b commented Jul 15, 2025

yes i think the correct fix is to ensure that we iterate over the correct array regions, not changing the chunks / shards declaration

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

needs release notes Automatically applied to PRs which haven't added release notes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Reading sharded array with multiprocessing produces wrong result

2 participants