Open anomiex opened 6 months ago
Hello @anomiex Thank you for creating this issue. We will investigate it and get back to you as soon as we have some feedback.
I notice there is a linked pr https://github.com/actions/stale/pull/1152 is there any possibility this might move forward?
We're seeing this, too. A fix would be highly appreciated. Handler might end up in
Warning: If you think that not enough issues were processed you could try to increase the quantity related to the operations-per-run (https://github.com/actions/stale#operations-per-run)) option which is currently set to 30
otherwise.
Description: If a repository has many caches being used between runs of
actions/stale
, such that the "_state" cache entry is not on the first page of results returned from the list caches API,actions/stale
will fail to restore its state and then will fail to update the state.Action version: 9.0.0
Platform:
Runner type:
Repro steps:
actions/stale
with a lowoperations-per-run
and enough issues that a single run cannot process them all.actions/stale
run, which should create the "_state" cache entry.https://api.github.com/repos/{owner}/{repo}/actions/caches
no longer includes "_state" as it has been pushed to the second page of results.actions/stale
run again.My test repo for this issue is at https://github.com/anomiex/test-stale.
Expected behavior: For step 4, the state is restored correctly and processing continues from where the previous run left off.
Actual behavior: In step 4, near the start, it reports
Processing begins from the first issue. Then at the end it reports
Analysis: The
checkIfCacheExists
function only checks the first page of results, using the default value of 30 entries per page. https://github.com/actions/stale/blob/3f3b0175e8c66fb49b9a6d5a0cd1f8436d4c3ab6/src/classes/state/state-cache-storage.ts#L33-L46 While you could fix the bug by adding pagination so the relevant cache entry is found even if it's not on the first page, a more performant fix would be to make use of thekey
andref
parameters to the list caches API to specify the branch and key that we actually care about.I suppose doing both would be an even better idea, just in case some repo is creating a lot of other cache entries with the "_state" prefix.