bug: Handle range request with incomplete response
- Dominant language
- Rust
- Stars
- 5.4k
- Forks
- 825
- Avg merge
- 1d 14m
- Merged PRs (30d)
- 127
Description
### Describe the bug
Per: https://issues.chromium.org/issues/390229583 returning 206 with incomplete content is expected. OpenDAL may need to handle this corner case.
Or please also respond to the chromium issue to provide more context.
### Steps to Reproduce
Related: https://github.com/XiangpengHao/parquet-viewer/issues/7
### Expected Behavior
OpenDAL should not crash when receiving 206 with an incomplete response.
### Additional Context
Currently, OpenDAL fails at this line.
https://github.com/apache/opendal/blob/0c44e07c49f65a10cc4f6d56c377e851abb34876/core/src/raw/http_util/body.rs#L89
### Are you willing to submit a PR to fix this bug?
- [ ] Yes, I would like to submit a PR.
Contributor guide
Research direction
Start in core/src/raw/http_util/body.rs around line 89 and inspect how a 206 response with incomplete content is handled. Read the Chromium issue and the related parquet-viewer issue for context on the expected corner case. Done means OpenDAL no longer crashes when receiving that response.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100