Skip to content

feat (telemetry) Handling synchronization when registering prometheus metrics #445

feat (telemetry) Handling synchronization when registering prometheus metrics

feat (telemetry) Handling synchronization when registering prometheus metrics #445

Triggered via pull request July 15, 2024 18:40
Status Failure
Total duration 1m 56s
Artifacts

pipeline.yml

on: pull_request
Matrix: ci
Fit to window
Zoom out
Zoom in

Annotations

5 errors and 3 warnings
ci (lint, ubuntu-latest, 1.21.0): telemetry/prometheus/metrics.go#L170
Error return value is not checked (errcheck)
ci (lint, ubuntu-latest, 1.21.0): telemetry/prometheus/metrics.go#L241
Error return value is not checked (errcheck)
ci (lint, ubuntu-latest, 1.21.0): telemetry/prometheus/metrics.go#L169
type assertion on error will fail on wrapped errors. Use errors.As to check for specific errors (errorlint)
ci (lint, ubuntu-latest, 1.21.0): telemetry/prometheus/metrics.go#L240
type assertion on error will fail on wrapped errors. Use errors.As to check for specific errors (errorlint)
ci (lint, ubuntu-latest, 1.21.0)
Process completed with exit code 2.
ci (test, ubuntu-latest, 1.21.0)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3, actions/setup-go@v3, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
ci (build, ubuntu-latest, 1.21.0)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3, actions/setup-go@v3, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
ci (lint, ubuntu-latest, 1.21.0)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3, actions/setup-go@v3, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/