Don't require zarr 3 Bytes Codec configuration key

[frcroth]

URL of deployed dev instance (used for testing):

• https://___.webknossos.xyz

Steps to test:

• Read a zarr dataset where bytes codec does not have a configuration key

Note that other implemented codecs don't only include optional fields, thus the configuration key is neccessary.

Issues:

• fixes Header of zarr3 array with bytes codec without configuration cannot be parsed  #8233

---

(Please delete unneeded items, merge only when none are left open)

• Updated changelog
• Needs datastore update after deployment

[coderabbitai]

📝 Walkthrough

📝 Walkthrough

Walkthrough

The changes in the Zarr3ArrayHeader.scala file focus on improving the parsing and handling of Zarr3 array headers, particularly for codecs without explicit configurations. The modifications enhance the robustness of codec reading by introducing more flexible configuration extraction, especially for bytes codecs. The updates ensure that missing or minimal configurations can be processed without causing parsing errors, addressing challenges with different Zarr3 metadata formats.

Changes

File	Change Summary
webknossos-datastore/app/com/scalableminds/webknossos/datastore/datareaders/zarr3/Zarr3ArrayHeader.scala	- Updated readCodecs method to handle codec configurations more flexibly - Modified assertValid method to improve data type and codec configuration validation - Enhanced outerChunkShape method to handle chunk grid configurations more explicitly
CHANGELOG.unreleased.md	- Updated to reflect changes in dataset tooltip, terminology, layer name handling, dataset renaming, and various bug fixes related to dataset management and codec handling

Assessment against linked issues

Objective	Addressed	Explanation
Parse Zarr3 array header with bytes codec without configuration [#8233]	✅
Handle optional codec configuration [#8233]	✅
Support minimal codec metadata [#8233]	✅

Possibly related PRs

• Zarr streaming e2e test #8137: This PR implements end-to-end tests for the Zarr streaming feature, which is directly related to the changes made in the Zarr3ArrayHeader.scala file regarding codec reading logic and handling of Zarr data formats.
• Fix: Use forwardRef for scrollable virtualized tree #8186: This PR addresses the implementation of a scrollable virtualized tree component, which may relate to the overall handling of data structures in the application, including those affected by changes in the Zarr3ArrayHeader.scala.
• Relax bounding box requirements for model training #8222: This PR relaxes bounding box requirements for model training, which may indirectly relate to the handling of data types and configurations in the Zarr3ArrayHeader.scala changes.
• Only show locked banner if current user is in organization of the annotation #8273: This PR modifies the display logic of the locked banner based on user organization, which may relate to the overall user interface and data access management in the application, indirectly connecting to the changes in Zarr3ArrayHeader.scala.

Suggested labels

bug, documentation

Suggested reviewers

• daniel-wer

Poem

🐰 In the realm of Zarr, where data flows free,
A rabbit hops through codec complexity
With Option and tryo, we parse with grace
No configuration left without a trace
Bytes dance smoothly, headers now clear! 🧩

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between ec0cbf0 and 71139f0.

📒 Files selected for processing (2)

• CHANGELOG.unreleased.md (1 hunks)
• webknossos-datastore/app/com/scalableminds/webknossos/datastore/datareaders/zarr3/Zarr3ArrayHeader.scala (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (2)

• CHANGELOG.unreleased.md
• webknossos-datastore/app/com/scalableminds/webknossos/datastore/datareaders/zarr3/Zarr3ArrayHeader.scala

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

CHANGELOG.unreleased.md (1)

31-31: Add a comma for better readability.

The sentence would be clearer with a comma before "making".

- Fixed a bug where in the add remote dataset view the dataset name setting was not in sync with the datasource setting of the advanced tab making the form not submittable.
+ Fixed a bug where in the add remote dataset view the dataset name setting was not in sync with the datasource setting of the advanced tab, making the form not submittable.

🧰 Tools

🪛 LanguageTool

[uncategorized] ~31-~31: A comma might be missing here.
Context: ... the datasource setting of the advanced tab making the form not submittable. [#8245...

(AI_EN_LECTOR_MISSING_PUNCTUATION_COMMA)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b0a981e and ec0cbf0.

📒 Files selected for processing (1)

• CHANGELOG.unreleased.md (1 hunks)

🧰 Additional context used

🪛 LanguageTool

CHANGELOG.unreleased.md

[uncategorized] ~31-~31: A comma might be missing here.
Context: ... the datasource setting of the advanced tab making the form not submittable. [#8245...

(AI_EN_LECTOR_MISSING_PUNCTUATION_COMMA)

🔇 Additional comments (1)

CHANGELOG.unreleased.md (1)

36-36: LGTM! Clear and well-referenced changelog entry.

The entry accurately describes the fix implemented in PR #8282 and follows the changelog format.

[fm3]

LGTM, thanks!