-
Notifications
You must be signed in to change notification settings - Fork 24
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
Bionic reports some IO problems as cache integrity issues #79
Labels
bug
Something isn't working
Comments
Just noting that we've also seen a |
Recreated this error by dropping internet connection while gcs cache was being updated. Here is the stack trace
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In general, almost any exception while reading a cached file will currently be reported as an
InvalidCacheStateError
, which means the user will be told the cache is corrupted and needs to be cleared. However, this includes things like like GCS timing out while copying a local cached file into a bucket (like here), which are not cache corruption problems at all. We may need to be more picky about which exceptions we report this way.The text was updated successfully, but these errors were encountered: