Skip to content
push-image

fix: app and envoy container not shutting down gracefully (#2155) #2666

Sign in to view logs

fix: app and envoy container not shutting down gracefully (#2155)

fix: app and envoy container not shutting down gracefully (#2155) #2666

Triggered via push October 20, 2025 14:22
@cre8ivejpcre8ivejp
pushed c78bb7e
main
Status Success
Total duration 3m 37s
Artifacts –

push-image.yaml

on: push
setup
10s
setup
go
2m 54s
go
dispatch
11s
dispatch
notify-success-to-slack
3s
notify-success-to-slack
notify-failure-to-slack
notify-failure-to-slack
Fit to window
Zoom out
Zoom in

Annotations

2 warnings
notify-success-to-slack
Additionally, the attachment-level `fallback` argument is missing in the request payload for a chat.postMessage call - To avoid this warning, it is recommended to always provide a top-level `text` argument when posting a message. Alternatively, you can provide an attachment-level `fallback` argument, though this is now considered a legacy field (see https://api.slack.com/reference/messaging/attachments#legacy_fields for more details).
notify-success-to-slack
The top-level `text` argument is missing in the request payload for a chat.postMessage call - It's a best practice to always provide a `text` argument when posting a message. The `text` is used in places where the content cannot be rendered such as: system push notifications, assistive technology such as screen readers, etc.