Skip to content

add tele-operation service level #53

add tele-operation service level

add tele-operation service level #53

Triggered via pull request September 29, 2026 08:10
@vlasatnovlasatno
synchronize #52
vlasatno:main
Status Failure
Total duration 45s
Artifacts 1

camara-validation.yml

on: pull_request
validation  /  Validate
41s
validation / Validate
Fit to window
Zoom out
Zoom in

Annotations

12 errors, 3 warnings, and 1 notice
validation / Validate
Process completed with exit code 1.
validation / Validate
Validation failed — see summary and annotations above
syntax error: mapping values are not allowed here: code/API_definitions/predictive-connectivity-data.yaml#L498
[syntax] syntax error: mapping values are not allowed here
$ref target does not exist: code/API_definitions/predictive-connectivity-data.yaml#L359
[S-229] '#/components/schemas/NetworkType' does not exist | Suggestion: The $ref points to a JSON pointer that does not exist in the target file. Check the pointer name against the target's components section — a schema renamed or removed in a newer Commonalities release is the usual cause. Fix the reference in this API definition; do not edit code/common/.
$ref target does not exist: code/API_definitions/predictive-connectivity-data.yaml#L312
[S-229] '#/components/schemas/ConnectivityDataAsyncResponse' does not exist | Suggestion: The $ref points to a JSON pointer that does not exist in the target file. Check the pointer name against the target's components section — a schema renamed or removed in a newer Commonalities release is the usual cause. Fix the reference in this API definition; do not edit code/common/.
$ref target does not exist: code/API_definitions/predictive-connectivity-data.yaml#L286
[S-229] '#/components/schemas/AcceptedAsyncResponse' does not exist | Suggestion: The $ref points to a JSON pointer that does not exist in the target file. Check the pointer name against the target's components section — a schema renamed or removed in a newer Commonalities release is the usual cause. Fix the reference in this API definition; do not edit code/common/.
$ref target does not exist: code/API_definitions/predictive-connectivity-data.yaml#L266
[S-229] '#/components/schemas/ConnectivityDataResponse' does not exist | Suggestion: The $ref points to a JSON pointer that does not exist in the target file. Check the pointer name against the target's components section — a schema renamed or removed in a newer Commonalities release is the usual cause. Fix the reference in this API definition; do not edit code/common/.
validation / Validate
Bundling failed for predictive-connectivity-data.yaml: - bad indentation of a mapping entry in "/home/runner/work/PredictiveConnectivityData/PredictiveConnectivityData/code/API_definitions/predictive-connectivity-data.yaml" (498:11)
OpenAPI YAML fails parser conformance: code/API_definitions/predictive-connectivity-data.yaml#L498
[P-037] OpenAPI YAML fails parser conformance: bad indentation of a mapping entry | Suggestion: Prefer block-style YAML for examples. Rewrite invalid JSON-like flow-style YAML mappings or sequences so the file parses with YAML 1.2-conformant parsers.
Schema must declare a type or combiner: code/API_definitions/predictive-connectivity-data.yaml#L463
[S-016] Missing 'type' at components.schemas.RetrieveConnectivityRequest.properties.serviceLevel
validation / Validate
"The ubuntu-latest label will migrate to Ubuntu 26 beginning October 19, 2026. For more information, see https://github.com/actions/runner-images/issues/14748"

Artifacts

Produced during runtime
Name Size Digest
validation-diagnostics
3.33 KB
sha256:0d9fd24966e62aec6c2cbe7d13e6741ccfcdfda774a6b6b42c66339fdee5da15