Fix CPU metric spike on first observation #1706

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft

scottopell wants to merge 1 commit into dd/extract-lading-observer-crate-clean from sopell/observer-bugfixes

+41 −28

Draft

Fix CPU metric spike on first observation #1706

Fix CPU metric spike on first observation

Annotations

3 warnings

Build and push to GHCR: Dockerfile#L16

SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ARG "AWS_SESSION_TOKEN") More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/

Build and push to GHCR: Dockerfile#L15

SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ARG "AWS_SECRET_ACCESS_KEY") More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/

Build and push to GHCR: Dockerfile#L14

SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ARG "AWS_ACCESS_KEY_ID") More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Fix CPU metric spike on first observation #1706

Uh oh!

Fix CPU metric spike on first observation #1706

Uh oh!

Annotations

Re-running jobs...

Fix CPU metric spike on first observation #1706

Are you sure you want to change the base?