-
Notifications
You must be signed in to change notification settings - Fork 172
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
TProtocolexception: Invalid Data after chrome update #1693
Comments
There's a good chance upgrading to |
A few people in slack have mentioned this and it appears to be related to the browser cache in some way. If you clear your cache and refresh the page it should work - or open it in an incognito/private browser |
It seems the upgrade to 29.0.2 helped for me! |
I am still running into the issue when using version 30.0.1 for @evidence-dev/evidence, for chrome I am using version 123.0.6312.86 |
@ksstolwijk have you tried clearing the cache in your browser? |
@mcrascal we indeed tried to clear the cache, which initially seemed to help. However, the error appeared again after a while. It might also be noteworthy to say that some of my colleagues who are working on linux machine are not experiencing this issue so far. Whereas I and most of my other colleagues work on Windows machines. |
Have seen this issue pop up a few times in user projects in the last week |
Still getting this with v33.0.1. FYI, I have 3 dropdrown boxes in the report. |
aah so its not only me. I have the same issue! and @hughess is right if you clear cache it resolves. still not good UX though... |
This seems to be only on windows, or at least haven’t been able to reproduce on Mac |
I've been running into the same issue here and have been in contact with @hughess regarding the issue. I can concur with the observations of others that it seems to be Windows-specific and that when the cache is disabled (either through dev tools or through Incognito/InPrivate mode) the application functions as expected. It makes me think that either the backend cached parquet files are corrupting or that there is a path issue (i.e. backslashes / forwardslashes) that affects Windows but doesn't affect Unix/Linux-based systems. I've ran a quick debug on my affected instance and the error is raised in the After the page has errored out, when reload is attempted I get a
With the cache off, the page that errored out will load correctly (no TProtocolException raised), but there is another exception that is raised during the debug:
|
This may be related to this: duckdb/duckdb-wasm#1658 As per the issue above, results in a TProtocolException when calling a Parquet file by URL, and is Windows specific, only affecting Chrome and Edge (Firefox is unaffected). |
Early days, but in initial testing no exceptions are raised with the cache enabled and the page now loads correctly in Edge and Chrome. |
Oh wow nice investigation thx! Will do this override as well let's see if it fixes it for me as well
…-------- Original Message --------
On 6 May 2024, 06:50, Tim Howard wrote:
The issue seems to be fixed with the latest development version of DuckDB. I've placed the following override into the package.json file:
"overrides": {
***@***.***/duckdb-wasm": "1.28.1-dev190.0"
}
Early days, but in initial testing no exceptions are raised with the cache enabled and the page now loads correctly in Edge and Chrome.
—
Reply to this email directly, [view it on GitHub](#1693 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/ABEC63TP7MDLKBMSMRKE3RTZA4DYJAVCNFSM6AAAAABEJCBO62VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJVGE4TGNJXGM).
You are receiving this because you commented.Message ID: ***@***.***>
|
After some further testing, the issue has unfortunately reappeared. Does seem to be an ongoing issue with @duckdb/duckdb-wasm. |
I had a working version of Evidence aside from the one affected, that had an override for
@hughess What settings does Evidence use to save it's Parquet files in Edit: Turning off certain compression schemes in the dev tools, now confronted with this error |
Hi all, I've found a mitigation to stop this from occurring until @duckdb/duckdb-wasm fix the issue. If you turn caching off for certain file types (parquet, arrow, js, json), you won't get the TProtocolException in Chrome/Edge. It will be a little slower as there will be more requests made to the server for the data files, but it will stop the error being raised. Here's a configuration for IIS, which can be adapted to other web servers:
I strongly assume the issue is associated with this: duckdb/duckdb-wasm#1658 |
Thanks for sharing - we're looking into ways to mitigate this issue in advance of the next release of duckdb-wasm (which we hope will contain a fix). Here are the notes we recently shared in our slack community: Known Issue for self-hosted Windows usersSituation:
Cause:
Workarounds:
Upcoming:
|
Steps To Reproduce
After a recent update to chrome we get the following error on a page with dropdown filters. The same page worked in chrome before the update and it works in Firefox still. Seems to be something with duckdb?
Steps we can take to reproduce the issue you're seeing. Sample data is helpful.
Environment
Expected Behavior
Able to select different options in our dropdowns and get updated data views.
Actual Behaviour
On first page load, an error message is shown in console. When selecting options in our dropdowns our graphs and tables get blank values.
Workarounds
Use an older browser version or another browser.
The text was updated successfully, but these errors were encountered: