Arvados

This seems to be a simple case of turning off resource type prefixing on the process type filter so that the container request api doesn't complain

--- a/services/workbench2/src/store/all-processes-panel/all-processes-panel-middleware-service.ts
+++ b/services/workbench2/src/store/all-processes-panel/all-processes-panel-middleware-service.ts
@@ -27,7 +27,8 @@ export class AllProcessesPanelMiddlewareService extends ProcessesMiddlewareServi
         if (sup === null) { return null; }
         const columns = dataExplorer.columns as DataColumns<string, ContainerRequestResource>;

-        const typeFilters = serializeOnlyProcessTypeFilters(true)(getDataExplorerColumnFilters(columns, AllProcessesPanelColumnNames.TYPE));
+        const typeFilters = serializeOnlyProcessTypeFilters(false)(getDataExplorerColumnFilters(columns, AllProcessesPanelColumnNames.TYPE));
         return joinFilters(sup, typeFilters);
     }
 }

Stephen Smith wrote in #note-2:

This seems to be a simple case of turning off resource type prefixing on the process type filter so that the container request api doesn't complain

[...]

It should be using the group contents API, though?

Stephen says the query is using group contents but the "count" is using container requests. It should use group contents for both.

22130-all-processes-paging @ c449e16ae6754c444ece098220b87322b86b4a60

• Use group contents instead of container_request endpoint so that the filters are the same
• Also fixed loadProject to bail out when called with an invalid uuid (this is because it was making an API call with owner_uuid=all_processes which would never work).
• Also discovered that navigating to the process page would cause loadProcess to be called twice, resulting in a bunch of redundant API calls. Eliminated the unnecessary loadProcess call.

developer-run-tests: #4516

This lgtm!