Skip to content

Use exceptions instead of HTML responses with error statuses #11592

Use exceptions instead of HTML responses with error statuses

Use exceptions instead of HTML responses with error statuses #11592

Re-run triggered October 1, 2024 16:01
Status Failure
Total duration 19m 38s
Artifacts 9

comment.yml

on: issue_comment
verify_author
5s
verify_author
run-full  /  ...  /  search_cache
4s
run-full / search_cache / search_cache
Matrix: run-full / e2e_testing
send_status
4s
send_status
Fit to window
Zoom out
Zoom in

Annotations

1 error and 3 warnings
run-full / e2e_testing (actions_tasks3)
Process completed with exit code 1.
Variables should be defined before their use: Dockerfile#L96
UndefinedVar: Usage of undefined variable '$no_proxy' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/
Legacy key/value format with whitespace separator should not be used: Dockerfile#L147
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Sensitive data should not be used in the ARG or ENV commands: Dockerfile.ui#L7
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ARG "SOURCE_MAPS_TOKEN") More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/

Artifacts

Produced during runtime
Name Size
cypress_screenshots_actions_tasks3
171 KB
e2e_container_logs_actions_tasks3
29.2 KB