Make version history view paginated

[frcroth]

URL of deployed dev instance (used for testing):

• paginationforupdateactionlog.webknossos.xyz

Steps to test:

• Create some annotations
• Check the update history

Issues:

• fixes Pagination for update action log #5421

---

• Updated (unreleased) changelog
• Ready for review

[fm3]

@philippotto this issue became relevant again recently (a user reported data loss and we could not explore older annotation version as the update action log request did not complete in reasonable time). Do you think you have some capacity to adapt the front-end to use pagination? And if so, do you think the API with newestVersion and oldestVersion makes sense? Or would you prefer to send a limit and page number? The front-end should already know the newest possible version of the tracing, right? and the oldest should always be zero. This is not urgent, but if you have some time, maybe you could have a look :)

[philippotto]

@philippotto this issue became relevant again recently (a user reported data loss and we could not explore older annotation version as the update action log request did not complete in reasonable time). Do you think you have some capacity to adapt the front-end to use pagination? And if so, do you think the API with newestVersion and oldestVersion makes sense? Or would you prefer to send a limit and page number? The front-end should already know the newest possible version of the tracing, right? and the oldest should always be zero. This is not urgent, but if you have some time, maybe you could have a look :)

I'm having a look :)

@frcroth could you do the same for the SkeletonTracingController? I think it makes sense that both version routes use the pagination mechanism.

[philippotto]

The front-end is ready from my side. For easier testing I set the items per page parameter to 5. However, it could probably be something like 500? I also made the groups auto-expand for the testing round, but I'd revert that, too.

The only thing missing is that the back-end also accepts the new parameters for skeleton tracings.

[fm3]

Yes 500 seems reasonable. We can still tweak it again later if we find that with real-world annotations this is still slow

[frcroth]

@philippotto The route for skeleton tracing is implemented

[philippotto]

@philippotto The route for skeleton tracing is implemented

Thanks!

@fm3 Would you like to test this PR? Maybe you could also review the frontend? In that case, I think it would be easiest to have a quick call where I guide you through it :)

[fm3]

Works for me :) Thanks for guiding me through the code in person. Maybe you can investigate why the first two pages are fetched twice each

[philippotto]

Maybe you can investigate why the first two pages are fetched twice each

Found the bug! I had to change a || to &&. Will merge now unless you veto :)