Skip to content

S3 backend configuration does not react the same way whether endpoint or endpoints.s3 is specified #19486

S3 backend configuration does not react the same way whether endpoint or endpoints.s3 is specified

S3 backend configuration does not react the same way whether endpoint or endpoints.s3 is specified #19486

Triggered via issue November 21, 2024 15:08
Status Success
Total duration 18s
Artifacts

issue-comment-created.yml

on: issue_comment
issue_comment_triage
7s
issue_comment_triage
Fit to window
Zoom out
Zoom in

Annotations

1 error and 4 warnings
issue_comment_triage
Error: failed to remove labels: stale,waiting-reply
issue_comment_triage
The following actions uses node12 which is deprecated and will be forced to run on node16: actions-ecosystem/action-remove-labels@2ce5d41b4b6aa8503e285553f75ed56e0a40bae0. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
issue_comment_triage
The following actions use a deprecated Node.js version and will be forced to run on node20: actions-ecosystem/action-remove-labels@2ce5d41b4b6aa8503e285553f75ed56e0a40bae0. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
issue_comment_triage
failed to remove label: stale: HttpError: Label does not exist
issue_comment_triage
failed to remove label: waiting-reply: HttpError: Label does not exist