Bug #18966
closed
Requesting a non-visible collection UUID shows a blank page
Added by Lucas Di Pentima almost 3 years ago.
Updated almost 3 years ago.
Estimated time:
(Total: 0.00 h)
Release relationship:
Auto
Description
When a user attempts to view an existing collection that they don't have read access to, or a non-existing collection (but valid) UUID, the resulting UI is a blank page. (see attached screenshot)
From reading the browser's devtools networkl screen, it seems that collection is being request via a LIST call with all it's past versions, so a 404 response isn't available when the UUID cannot be accessed or doesn't exist.
Files
- Status changed from New to In Progress
- Assigned To set to Lucas Di Pentima
- Related to Bug #18484: Direct links to Collections are retrieving the full manifest_text for no reason added
Updates at arvados-workbench2|c1c27e7f - branch 18966-collection-not-found-ui
- developer-tests-workbench2: #640 
- Changes the
collectionService.get()
func to use a GET request instead of LIST. To avoid getting the manifest_text
field, it passes a hardcoded list of default fields that excludes it.
- Improves Cypress test related to the "not found" dialog, adding more cases, including collections.
- Updates
collectionService.get()
unit tests to reflect the current behavior.
Only one minor thing - it looks like an it.only() snuck in from the main branch in the search spec L85, but otherwise everything passes and it LGTM!
- Status changed from In Progress to Resolved
Also available in: Atom
PDF