fix(weave_query): Handle stale file handle os errors on table load #3401
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.
Description
Fixes the panel crash reported in WB-22355
The panel crash happens due to an unhandled 'stale file handle' error when query engine is executing
file-table.
See screenshot below from this trace.This panel crash happens very rarely as it took almost a week for repro & trace capture. We're unsure to what causes this, but we're handling the error by returning a None value for the file-table op which is consistent with how we handle pulling files from run summary.
Testing
Using the
invoker.ini
dev environment.I simulated a stale file handle error by raising an
OSError
exception witherrno.ESTALE
in the opening of the json table and confirmed that the panel on the frontend no longer crashes.