Arvados

When Workbench queries the status of a queued container request, if the dispatcher returns no information (e.g., because it's not the cloud dispatcher), Workbench should not try to render anything. As of 3.1.0 it logs the empty message with a timestamp which looks goofy and is unhelpful.

Workbench should not try to predict whether or not the dispatcher will return a status message. Hopefully more dispatchers will do so in the future. Continue querying dispatcher status as we do now. The only change is, if that dispatch message is empty, short circuit rendering it in the log console. Here in source:services/workbench2/store/process-logs-panel/process-logs-panel-actions.ts :

               if (process?.container?.state === ContainerState.QUEUED || process?.container?.state === ContainerState.LOCKED) {
                    const containerStatus: ContainerStatus = await containerRequestService.containerStatus(process?.containerRequest?.uuid, false);
                    logFragments.push({
                        logType: LogEventType.SCHEDULING,
                        contents: [`${new Date().toISOString()} ${containerStatus.schedulingStatus}`],
                    });
                }

We should check that containerStatus.schedulingStatus has a non-whitespace character in it before calling logFragments.push.