Possibly remove InvalidRangeRequest handling
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1k
- Forks
- 305
- Avg merge
- 22h 37m
- Merged PRs (30d)
- 4
Description
See https://github.com/dask/s3fs/pull/229. After that, the catching of Invalid ranges we do in https://github.com/dask/s3fs/blob/3825b7473312cbb3e7bc9196fbd46eefe3c4556b/s3fs/core.py#L1153-L1157
may be unnecessary.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read PR 229 first, then inspect the InvalidRange handling at s3fs/core.py lines 1153-1157. Confirm whether the changes in that pull request make the catch unnecessary and check for relevant tests or callers. Done means the obsolete handling is removed only if the resulting behavior remains covered and correct.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cloud
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100