Skip to content

Error delete _state: [403] Resource not accessible by integration #1133

Open

Description

@autoantwort

Description:
If a job has multiple actions/stale steps the creation of the cache fails.

Action version:
9

Platform:

  • Ubuntu
  • macOS
  • Windows

Runner type:

  • Hosted
  • Self-hosted

Repro steps:
https://github.com/microsoft/vcpkg/blob/master/.github/workflows/stale.yml

Expected behavior:
No errors.

Actual behavior:
Errors. See https://github.com/microsoft/vcpkg/actions/runs/7750221792

Activity

  1. v-HarithaVattikuti commented on Feb 3, 2024

    @v-HarithaVattikuti
    Contributor

    Hello @autoantwort
    Thank you for creating this issue. We will investigate it and get back to you as soon as we have some feedback.

  2. ericLemanissier commented on Feb 7, 2024

    @ericLemanissier
  3. added a commit that references this issue on Feb 22, 2024
  4. Pil0tXia commented on Apr 14, 2024

    @Pil0tXia

    Hi everyone, I'm encountering the same issue at https://github.com/apache/eventmesh/actions/runs/8675497930/job/23788986036 and I hope this log would be helpful to you.

    Maybe I would revert back to v8 and see if this problem still exists.

  5. shmishra99 commented on Apr 26, 2024

    @shmishra99

    Granting actions:write to the stale workflow will allow it to manage issues cache as intended.

  6. jeremystretch commented on May 14, 2024

    @jeremystretch

    This appears to be the same issue described in #1131.

  7. autoantwort commented on May 23, 2024

    @autoantwort
    Author

    Adding actions: write also fixes parts of the problem. The same cache entry is then still used across different cache steps

  8. 12 remaining items

  9. added a commit that references this issue on Feb 4, 2025
  10. ericLemanissier commented on Apr 10, 2025

    @ericLemanissier

    @autoantwort you probably want to try my proposition from #1237.
    For this, you can replace uses: actions/stale@...with uses: actions/stale@4c023f01d613e60293d8004f251a18bfb9bbd71d and remove actions: write from https://github.com/microsoft/vcpkg/blob/master/.github/workflows/stale.yml

  11. autoantwort commented on Apr 10, 2025

    @autoantwort
    Author

    Microsoft don't want that: microsoft/vcpkg#41403 (comment)

  12. added a commit that references this issue on Apr 21, 2025
  13. suyashgaonkar commented on May 16, 2025

    @suyashgaonkar
    Contributor

    Hi @autoantwort ,To maintain state, this action uses GitHub Actions Cache, via the API. One of the operations it needs to perform in the event of a cache conflict is to delete the existing cache. We have updated the README in the PR #1248 which is now successfully merged. You can now try the workflow by adding recommended permissions and let us know.

  14. suyashgaonkar commented on May 22, 2025

    @suyashgaonkar
    Contributor

    Hi @autoantwort , We are awaiting for your response on the following ticket please let us know if you have any queries on the same.

  15. autoantwort commented on May 22, 2025

    @autoantwort
    Author

    Hi @suyashgaonkar! With the permission you don't get an error anymore, but the stale action is still doing the wrong stuff. If you have multiple stale actions in a repo they will all share the same cache, which means if the first action moves the offset by 30 issues, the next action will not check the first 30 issues again (with different conditions). For such an example see here: https://github.com/microsoft/vcpkg/blob/master/.github/workflows/stale.yml
    There are two PRs which are fixing this bug: #1169 or #1134 which both create a unique key for each used cached action in a repo so that they don't interfere which each other.

  16. suyashgaonkar commented on Jun 10, 2025

    @suyashgaonkar
    Contributor

    Hi @autoantwort , Generating unique for each cached action could resolve the conflicts, but it is something that cannot be taken lightly. We can consider a major change like this in the future updates, for now we are marking this a feature request.

  17. added
    feature requestNew feature or request to improve the current logic
    and removed
    bugSomething isn't working
    on Jun 10, 2025
  18. removed their assignment
    on Jun 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    feature requestNew feature or request to improve the current logic

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions