Get the latest tech news
Chrome Returns 206 when the Server Returns 403
Sorry for the clickbait, but it is true. I was helping my partner debug an interesting bug in his fancy parquet viewer. The website crashes when a user tries to access S3. So the symptom is that OpenDAL (one of the parquet viewer’s dependencies) crashes because it did not receive enough data from S3 storage. My Initial Attempt Initially, I thought this was a bug inside OpenDAL, so I tried compiling everything on my native machine, but the bug disappeared. This allowed me to narrow the bugs to all WASM-related components. |Ao Li
So the symptom is that OpenDAL(one of the parquet viewer’s dependencies) crashes because it did not receive enough data from S3 storage. As a reflection, the main issue of my debugging process is that I set the wrong trust boundary at the very beginning. I was assuming Chrome was functioning correctly and jumped into the rabbit hole of debugging application code.
Or read this on Hacker News