Remove cache of beacon data files - #2959
Merged
Merged
Conversation
naddison36
requested review from
clement-ux,
shahthepro and
sparrowDom
as code owners
August 4, 2026 12:15
sparrowDom
approved these changes
Aug 4, 2026
sparrowDom
left a comment
Member
There was a problem hiding this comment.
thanks looks more resiliant
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
verifyBalancesandverifyDepositscomplete.finallyblock so files are removed even when verification fails.Background
Talos containers no longer create
/app/cacheduring their build. Beacon verification actions consequently failed withENOENTwhen attempting to write./cache/state_<slot>.ssz.Beacon state files are large and only needed while an action is running, so they do not need to persist between actions or container deployments.
Testing
utils/beacon.jsloads successfully.git diff --check.