Workaround for broken version restore view for large update action log

[philippotto]

URL of deployed dev instance (used for testing):

• https://___.webknossos.xyz

Steps to test:

• no need to test in my opinion

Issues:

• see https://scm.slack.com/archives/C5AKLAV0B/p1745829684656839

---

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

• Updated changelog
• Updated migration guide if applicable
• Updated documentation if applicable
• Adapted wk-libs python client if relevant API parts change
• Removed dev-only changes like prints and application.conf edits
• Considered common edge cases
• Needs datastore update after deployment

[coderabbitai]

Caution

Review failed

The pull request is closed.

📝 Walkthrough

Walkthrough

A fix was implemented to address an issue where the Version Restore sidebar would hang indefinitely when handling very large volume annotations. The solution involved reducing the ENTRIES_PER_PAGE constant in the frontend code from 5000 to 2500, thereby decreasing the size of JSON payloads and preventing them from exceeding the Node.js engine's maximum string length limit. No changes were made to the declarations of exported or public entities.

Changes

Files	Change Summary
frontend/javascripts/oxalis/view/version_list.tsx	Reduced ENTRIES_PER_PAGE from 5000 to 2500 to prevent oversized JSON payloads during sidebar version restore.
CHANGELOG.unreleased.md	Documented the fix for the Version Restore sidebar hanging on large volume annotations.

Possibly related PRs

• Workaround for broken version restore view for large update action log #8574: Also modifies ENTRIES_PER_PAGE in version_list.tsx to address the sidebar loading hang with large update action logs.

Suggested labels

bug, frontend

Poem

A sidebar once stuck in a loop,
With large annotations, it just couldn't cope.
Now with a tweak to entries per page,
The restore flows smooth—no more rage!
🐇✨ A hop, a fix, and all is right,
Restoring versions, day or night!

---

📜 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 d170d36 and 082d02c.

📒 Files selected for processing (1)

• CHANGELOG.unreleased.md (1 hunks)

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @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.

[MichaelBuessemeyer]

Did not test but sounds reasonable and shouldn't need testing imo. Thanks for patching this 🙏