Zettat123 8ae48ae033 fix: keep the shared action cache as extracted, re-fetch damaged trees (#1352) ...

The toolkit patch rewrote bundles in place in the shared action cache. Since https://gitea.com/gitea/runner/pulls/1316 trees are never refreshed, so a bundle left truncated failed every later job using it.

Patched bundles now only overwrite the job container's copy, so the runner no longer writes to an extracted tree.

Extraction records each file's size beside the tree, and a tree that no longer matches is fetched again, offline mode included, as a missing one always was. This also catches damage from outside the runner, such as storage losing a write, for a stat per file, a fraction of the copy each stage already makes. Trees from older runners have no record and download once more, except in offline mode, which keeps using them as before.

Generated with Claude Code.

Reviewed-on: https://gitea.com/gitea/runner/pulls/1352
Reviewed-by: Lunny Xiao <xiaolunwen@gmail.com>
Reviewed-by: bircni <bircni@icloud.com>
Co-authored-by: Zettat123 <zettat123@gmail.com>

2026-10-26 17:20:53 +00:00

..

config_test.go

…

config.example.yaml

fix: keep the shared action cache as extracted, re-fetch damaged trees (#1352)

2026-10-26 17:20:53 +00:00

config.go

…

edit_other.go

…

edit_test.go

…

edit_unix.go

…

edit.go

…

embed.go

…

registration_test.go

…

registration.go

…