-
Notifications
You must be signed in to change notification settings - Fork 366
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stale workflow fails to override cache. #1131
Comments
Hello @mshima |
Looks like issues already processed in previous runs never get closed due to the cache. .github/workflows/stale.yaml: name: 'Close stale issues'
on:
workflow_dispatch:
schedule:
- cron: '30 1 * * *'
permissions:
issues: write
jobs:
stale:
runs-on: ubuntu-latest
steps:
- uses: actions/stale@v9
with:
stale-issue-message: 'This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.'
days-before-stale: 30
days-before-close: 5
|
As workaround:
|
I think the docs are missing that the I saw the "Error delete _state: [403] Resource not accessible by integration" error here in a test repo while trying to reproduce a different issue, and based on the docs for the API used I added that permission and the error went away. |
Hi @mshima , we did investigation with provided information for the issue. Tried to reproduce the issue with actions/stale v8 and v9 both, and everything seems to be working fine on our end. We did not get the mentioned error Warning: Error delete _state: [403] Resource not accessible by integration. |
Hi @mshima , We are awaiting for your response on the issue. Please let us know if we can close this issue if there are no further queries. |
@suyashgaonkar thanks for the response. We've not had more problems since stale only processes at most 1-2 issues per day in our use case. At adoption we had more than 100 stale issues pending. |
@mshima you probably want to try my proposition from #1183. |
Description:
We have a stale workflow: https://github.com/jhipster/generator-jhipster/blob/main/.github/workflows/stale.yml
At first run it successfully generates a cache entry.
After that, the cache is never updated and is reused, so cached entries are never analyzed again.
See builds 599-605 at https://github.com/jhipster/generator-jhipster/actions/workflows/stale.yml
See 2 consecutive days have same cached issue numbers:
https://github.com/jhipster/generator-jhipster/actions/runs/7689412024/job/20951825772
https://github.com/jhipster/generator-jhipster/actions/runs/7682085625/job/20936000418
The error reported is:
Warning: Error delete _state: [403] Resource not accessible by integration
Are we missing a configuration? A permission maybe? There is no info in the docs.
Action version:
v9
Platform:
Runner type:
Repro steps:
Links above.
Expected behavior:
A new cache should be written at every run.
Actual behavior:
New cache are not been overridden
The text was updated successfully, but these errors were encountered: