mirror of
https://github.com/nektos/act.git
synced 2026-04-26 01:15:51 +03:00
[GH-ISSUE #2021] Artefact cache returns 400 for reserving already-reserved key, github returns 409 #970
Labels
No labels
area/action
area/cli
area/docs
area/image
area/runner
area/workflow
backlog
confirmed/not-planned
kind/bug
kind/discussion
kind/external
kind/feature-request
kind/question
meta/duplicate
meta/invalid
meta/need-more-info
meta/resolved
meta/wontfix
meta/workaround
needs-work
pull-request
review/not-planned
size/M
size/XL
size/XXL
stale
stale-exempt
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/act#970
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @huonw on GitHub (Sep 23, 2023).
Original GitHub issue: https://github.com/nektos/act/issues/2021
Bug report info
Command used with act
Describe issue
When reserving a cache item that already exists, GitHub returns status 409 Conflict, but act returns 400 Bad Request. This means that users of the cache cannot easily distinguish an attempted overwrite (which is okay in some applications) vs. other error conditions.
The corresponding output from GitHub, has
attempt-recreateincludeHTTP/2 409instead ofHTTP/1.1 400for act.Link to GitHub repository
No response
Workflow content
Relevant log output
Additional information
Thanks for act!
@github-actions[bot] commented on GitHub (Mar 22, 2024):
Issue is stale and will be closed in 14 days unless there is new activity