You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Error delete _state: [403] Resource not accessible by integration #1133
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.
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.
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.
Activity
v-HarithaVattikuti commentedon Feb 3, 2024
Hello @autoantwort
Thank you for creating this issue. We will investigate it and get back to you as soon as we have some feedback.
ericLemanissier commentedon Feb 7, 2024
Hello, the same error happens in here : https://github.com/conan-io/conan-center-index/actions/runs/7810903828/job/21305055330#step:2:1032
Update stale.yml to use old version as a bug fix
sophies927 commentedon Feb 15, 2024
Hello, I am encountering the same error here: https://github.com/microsoft/onnxruntime/actions/runs/7917906948/job/21615103971#step:2:3615.
Update stale.yml to use old version as a bug fix (#19532)
Reverted back to version 8 of stale workflow due to a bug in their ca…
Squashed commit of the following:
Pil0tXia commentedon Apr 14, 2024
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.
shmishra99 commentedon Apr 26, 2024
Granting
actions:writeto the stale workflow will allow it to manage issues cache as intended.Reduce drequency of GitHub stale action, and add action write permiss…
jeremystretch commentedon May 14, 2024
This appears to be the same issue described in #1131.
autoantwort commentedon May 23, 2024
Adding
actions: writealso fixes parts of the problem. The same cache entry is then still used across different cache steps12 remaining items
Update auto-close.yml
Add actionw write permission to stale CI
ericLemanissier commentedon Apr 10, 2025
@autoantwort you probably want to try my proposition from #1237.
For this, you can replace
uses: actions/stale@...withuses: actions/stale@4c023f01d613e60293d8004f251a18bfb9bbd71dand removeactions: writefrom https://github.com/microsoft/vcpkg/blob/master/.github/workflows/stale.ymlautoantwort commentedon Apr 10, 2025
Microsoft don't want that: microsoft/vcpkg#41403 (comment)
Update dormant.yml
suyashgaonkar commentedon May 16, 2025
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.
suyashgaonkar commentedon May 22, 2025
Hi @autoantwort , We are awaiting for your response on the following ticket please let us know if you have any queries on the same.
autoantwort commentedon May 22, 2025
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.
suyashgaonkar commentedon Jun 10, 2025
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.
Update stale.yml to use old version as a bug fix (#19532)
Update stale.yml to use old version as a bug fix (#19532)
[GitHub Actions] Updated workflows with newer revisions