Skip to content

potential fix to the bug im having #20237

potential fix to the bug im having

potential fix to the bug im having #20237

Re-run triggered February 1, 2025 00:14
Status Failure
Total duration 11m 53s
Artifacts

other_ci.yml

on: pull_request
prevent-gpl-licenses
7s
prevent-gpl-licenses
code-formatting
1m 7s
code-formatting
performance-regressions
4m 15s
performance-regressions
misc-tooling
2m 40s
misc-tooling
parser-silent
7m 52s
parser-silent
Fit to window
Zoom out
Zoom in

Annotations

11 errors
code-formatting
Process completed with exit code 1.
misc-tooling: vlib/net/http/response.v#L45
cannot assign to `status_code`: expected `string`, not `int`
misc-tooling: vlib/net/http/response.v#L49
cannot assign to `status_code`: expected `string`, not `int`
misc-tooling: vlib/net/http/response.v#L62
cannot assign to field `status_code`: expected `int`, not `string`
misc-tooling: vlib/net/http/response.v#L45
cannot assign to `status_code`: expected `string`, not `int`
misc-tooling: vlib/net/http/response.v#L49
cannot assign to `status_code`: expected `string`, not `int`
misc-tooling: vlib/net/http/response.v#L62
cannot assign to field `status_code`: expected `int`, not `string`
misc-tooling: vlib/net/http/response.v#L45
cannot assign to `status_code`: expected `string`, not `int`
misc-tooling: vlib/net/http/response.v#L49
cannot assign to `status_code`: expected `string`, not `int`
misc-tooling: vlib/net/http/response.v#L62
cannot assign to field `status_code`: expected `int`, not `string`
misc-tooling: vlib/net/http/response.v#L45
cannot assign to `status_code`: expected `string`, not `int`