Docker submission interface not loading

The page for submitting docker images is not loading correctly at the moment. Tested it with Chromium, Firefox and Safari.

I’m getting quite a lot of vue.js error in the browser console when trying to press the “docker” button.

Summary
Uncaught (in promise) TypeError: this.docker.resources is undefined
    beforeMount docker-submission-panel.vue:479
    callWithErrorHandling runtime-core.esm-bundler.js:155
    callWithAsyncErrorHandling runtime-core.esm-bundler.js:164
    __weh runtime-core.esm-bundler.js:2687
    invokeArrayFns shared.esm-bundler.js:561
    componentUpdateFn runtime-core.esm-bundler.js:5538
    run reactivity.esm-bundler.js:185
    update runtime-core.esm-bundler.js:5694
    setupRenderEffect runtime-core.esm-bundler.js:5708
    mountComponent runtime-core.esm-bundler.js:5490
    processComponent runtime-core.esm-bundler.js:5448
    patch runtime-core.esm-bundler.js:5038
    mountChildren runtime-core.esm-bundler.js:5234
    mountElement runtime-core.esm-bundler.js:5143
    processElement runtime-core.esm-bundler.js:5115
    patch runtime-core.esm-bundler.js:5035
    patchBlockChildren runtime-core.esm-bundler.js:5355
    processFragment runtime-core.esm-bundler.js:5418
    patch runtime-core.esm-bundler.js:5031
    componentUpdateFn runtime-core.esm-bundler.js:5660
    run reactivity.esm-bundler.js:185
    update runtime-core.esm-bundler.js:5694
    callWithErrorHandling runtime-core.esm-bundler.js:155
    flushJobs runtime-core.esm-bundler.js:396
    promise callback*queueFlush runtime-core.esm-bundler.js:285
    queueJob runtime-core.esm-bundler.js:279
    effect runtime-core.esm-bundler.js:5692
    triggerEffect reactivity.esm-bundler.js:394
    triggerEffects reactivity.esm-bundler.js:384
    trigger reactivity.esm-bundler.js:352
    set reactivity.esm-bundler.js:523
    set runtime-core.esm-bundler.js:3158
    onClick user.js line 1001 > eval line 213 > Function:171
    callWithErrorHandling runtime-core.esm-bundler.js:155
    callWithAsyncErrorHandling runtime-core.esm-bundler.js:164
    invoker runtime-dom.esm-bundler.js:369
    addEventListener runtime-dom.esm-bundler.js:319
    patchEvent runtime-dom.esm-bundler.js:337
    patchProp runtime-dom.esm-bundler.js:401
    mountElement runtime-core.esm-bundler.js:5152
    processElement runtime-core.esm-bundler.js:5115
    patch runtime-core.esm-bundler.js:5035
    mountChildren runtime-core.esm-bundler.js:5234
    mountElement runtime-core.esm-bundler.js:5143
    processElement runtime-core.esm-bundler.js:5115
    patch runtime-core.esm-bundler.js:5035
    mountChildren runtime-core.esm-bundler.js:5234
    mountElement runtime-core.esm-bundler.js:5143
    processElement runtime-core.esm-bundler.js:5115
    patch runtime-core.esm-bundler.js:5035
    mountChildren runtime-core.esm-bundler.js:5234
    processFragment runtime-core.esm-bundler.js:5407
    patch runtime-core.esm-bundler.js:5031
    componentUpdateFn runtime-core.esm-bundler.js:5587
    run reactivity.esm-bundler.js:185
    update runtime-core.esm-bundler.js:5694
    setupRenderEffect runtime-core.esm-bundler.js:5708
    mountComponent runtime-core.esm-bundler.js:5490
    processComponent runtime-core.esm-bundler.js:5448
    patch runtime-core.esm-bundler.js:5038
    render runtime-core.esm-bundler.js:6209
    mount runtime-core.esm-bundler.js:4402
    mount runtime-dom.esm-bundler.js:1605
    <anonymous> user.ts:380
    ts user.js:283
    __webpack_require__ user.js:1058
    <anonymous> user.js:1161
    <anonymous> user.js:1163

EDIT: I’m trying to submit a run to the causal retrieval task

1 Like

Dear Lukas,

Thank you for pointing out the problem.
This must be a bug that I introduced in a deployment this morning (I made no changes at this view, and was thinking that I only changed something completely unrelated, so I had not tested this part, sorry for the inconvenience).

I look into this and will report back as soon as it is resolved (it should not take long).

Best regards,

Maik

Dear Lukas,

I now fixed the bug (I shadowed by accident a variable on in the REST response, which is now fixed), and the docker submission is now working again.

Thanks for participating in the task.

Best regards,

Maik