Telegram service: use slog, improve error handling #13

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

Merged

weoses merged 1 commit into master from improve-logging-v1

Mar 30, 2025

Merged

Telegram service: use slog, improve error handling #13

Telegram service: use slog, improve error handling

Annotations

6 warnings

Dockerfile-telegram-service#L30

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/

Dockerfile-telegram-service#L1

FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/

Dockerfile-storage-service#L30

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/

Dockerfile-storage-service#L1

FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/

Dockerfile-ocr-service#L31

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/

Dockerfile-ocr-service#L1

FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Telegram service: use slog, improve error handling #13

Uh oh!

Uh oh!

Telegram service: use slog, improve error handling #13

Uh oh!

Annotations

The logs for this run have expired and are no longer available.

Re-running jobs...