Skip to content
Move labeled issues on project board

Exception: Connection failed. (docker instance v2023.3) #183

Sign in to view logs

Exception: Connection failed. (docker instance v2023.3)

Exception: Connection failed. (docker instance v2023.3) #183

Triggered via issue November 6, 2023 18:01
@fabiovincifabiovinci
labeled #1003 c105766
Status Success
Total duration 15s
Artifacts –

labeled_issue.yml

on: issues
Move "under development" issues
4s
Move "under development" issues
Move "ready for testings" issues
5s
Move "ready for testings" issues
Move "solved" issues
4s
Move "solved" issues
Move "deployed in reference validator" issues
3s
Move "deployed in reference validator" issues
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
Move "under development" issues
The following actions uses node12 which is deprecated and will be forced to run on node16: konradpabjan/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Move "solved" issues
The following actions uses node12 which is deprecated and will be forced to run on node16: konradpabjan/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Move "deployed in reference validator" issues
The following actions uses node12 which is deprecated and will be forced to run on node16: konradpabjan/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Move "ready for testings" issues
The following actions uses node12 which is deprecated and will be forced to run on node16: konradpabjan/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/