Skip to content

fix: ZstdCodec with sharding#56

Merged
brokkoli71 merged 1 commit into
zarr-developers:mainfrom
LDeakin:fix/zstd_w_sharding
Feb 9, 2026
Merged

fix: ZstdCodec with sharding#56
brokkoli71 merged 1 commit into
zarr-developers:mainfrom
LDeakin:fix/zstd_w_sharding

Conversation

@LDeakin

@LDeakin LDeakin commented Feb 7, 2026

Copy link
Copy Markdown
Member

zstd would try end decode the entire shard instead of a subchunk. The added test fails without the patch with: ZarrV3Test.testShardingWithZstdCodecReadWrite:225 » Zstd Destination buffer is too small

`zstd` would try end decode the entire shard instead of a subchunk. The added test fails without the patch with:
`ZarrV3Test.testShardingWithZstdCodecReadWrite:225 » Zstd Destination buffer is too small`
@normanrz
normanrz requested a review from brokkoli71 February 9, 2026 07:40

@brokkoli71 brokkoli71 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Good catch! I think the problem is, that the underlying array that is returned with .array() contains the whole shard, right? I think it makes sense to check for other ByteBuffer.array() calls that could raise a similar problem. I can do that in a separate PR.

@brokkoli71
brokkoli71 merged commit 3984a9e into zarr-developers:main Feb 9, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants