Bug #19362


keep-web notices when collections accessed by uuid have changed

Added by Peter Amstutz 13 days ago. Updated about 16 hours ago.

In Progress
Assigned To:
Target version:
Start date:
Due date:
% Done:


Estimated time:
(Total: 0.00 h)
Story points:


Users reported issues when opening HTML reports via Browser after updating the collection content via S3. Updated HTML pages are not immediately displayed and require a forced reload.

a) if they are uploading via S3, keep-web itself should be able to know that something changed

b) it seems like it would be a good idea to have keep-web either poll for changes or listen to websockets to find out when collections change instead of waiting for the cache to expire

Subtasks 1 (1 open0 closed)

Task #19394: ReviewNewLucas Di Pentima

Actions #2

Updated by Peter Amstutz 13 days ago

  • Description updated (diff)
Actions #3

Updated by Peter Amstutz 10 days ago

  • Target version changed from 2022-08-31 sprint to 2022-08-17 sprint
Actions #4

Updated by Peter Amstutz 10 days ago

  • Assigned To set to Tom Clegg
  • Category set to Keep
Actions #5

Updated by Tom Clegg 7 days ago

  • Status changed from New to In Progress

phase 1: Retire the old per-collection code path in favor of using the per-token session/sitefs for all keep-web requests. That will give better cache behavior, and address the case where a user uploads via S3 and then downloads via web using the same token.

phase 2: Mechanism for sitefs to invalidate cached collections on websocket events. That will also be an important piece of the Go-based fuse mount.

Actions #6

Updated by Peter Amstutz about 16 hours ago

  • Target version changed from 2022-08-17 sprint to 2022-08-31 sprint

Also available in: Atom PDF