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
I've seen this issue randomly a few times now, on multiple machines both locally and in CI
Error: async force execution for +vendor: unlazy force execution: failed to compute cache key: failed to get state for index 0 on <omitted>
I assume that it is referring to a corrupt cache layer or something to that effect. I notice that if I just modify the syntax of the affected layer, since that is enough to change the cache key, that usually gets it unstuck. I've also had success with earthly prune.
What should have happened?
I mean, ideally, layers or whatever is causing corruption here just wouldn't happen. Of course, we live in an imperfect world, but in this case it seems there could be a simple solution. If the layer is truly corrupt and no longer verifiable against the cache key, simply nuke the layer and continue instead of crashing? Maybe I'm misunderstanding the problem but it might work, not sure.
What earthly version?
v0.8.9
Buildkit Logs
No response
Other Helpful Information
As mentioned I've seen this more than once on more than one machine, and for multiple different build steps, so it doesn't seem to be related to any specific logic or syntax, just a general heisenbug it seems (best I can tell).
The text was updated successfully, but these errors were encountered:
What went wrong?
I've seen this issue randomly a few times now, on multiple machines both locally and in CI
Error: async force execution for +vendor: unlazy force execution: failed to compute cache key: failed to get state for index 0 on <omitted>
I assume that it is referring to a corrupt cache layer or something to that effect. I notice that if I just modify the syntax of the affected layer, since that is enough to change the cache key, that usually gets it unstuck. I've also had success with
earthly prune
.What should have happened?
I mean, ideally, layers or whatever is causing corruption here just wouldn't happen. Of course, we live in an imperfect world, but in this case it seems there could be a simple solution. If the layer is truly corrupt and no longer verifiable against the cache key, simply nuke the layer and continue instead of crashing? Maybe I'm misunderstanding the problem but it might work, not sure.
What earthly version?
v0.8.9
Buildkit Logs
No response
Other Helpful Information
As mentioned I've seen this more than once on more than one machine, and for multiple different build steps, so it doesn't seem to be related to any specific logic or syntax, just a general heisenbug it seems (best I can tell).
The text was updated successfully, but these errors were encountered: