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
This issue is most easily triggered with a large data set, so I've loaded these 24 files of GitHub data into a pool called github.
Then I click on Query Pool and while the stacked bar chart still shows "Loading..." I issue the following query against that pool:
repo.name=="duckdb/duckdb" type=="PullRequestEvent"
| count() by login:=actor.login
| sort -r count
| head 5
As shown in the attached video, once that query is issued an Unhandled Runtime Error AbortError: BodyStreamBuffer was aborted is surfaced.
Repro.mp4
Via binary search I found that this problem appeared at Zui commit 28f3f50 (associated with #2934). At commit 4399c1a that came right before that, there was still an Uncaught DOMException shown in DevTools, but it did not surface in the app as an error.
As shown in the attached video, now when we repeat the repro steps the query is issued immediately despite the stacked bar chart still showing "Loading..." and errors are not surfaced in the app nor DevTools.
Repro is with Zui commit 28f3f50.
This issue is most easily triggered with a large data set, so I've loaded these 24 files of GitHub data into a pool called
github
.Then I click on Query Pool and while the stacked bar chart still shows "Loading..." I issue the following query against that pool:
As shown in the attached video, once that query is issued an Unhandled Runtime Error
AbortError: BodyStreamBuffer was aborted
is surfaced.Repro.mp4
Via binary search I found that this problem appeared at Zui commit 28f3f50 (associated with #2934). At commit 4399c1a that came right before that, there was still an Uncaught DOMException shown in DevTools, but it did not surface in the app as an error.
But then at commit 28f3f50 it looks like:
As @jameskerr said upon reviewing this evidence:
The text was updated successfully, but these errors were encountered: