Incorrect conversion of RangeTo in BytesContentRange conversion

[sameer]

Hello,

First off just wanted to say thanks for this project, makes integrating with cloud storage providers a lot easier.

Just wanted to report some unexpected behavior with range reads. Specifically, when passing a RangeTo like ..END, it gets interpreted as object.len()-END..object.len() instead. I thought this test line should be equal to H not ! based on the equivalent Rust Playground example, but the meaning is different for Range according to MDN.

In range conversion, maybe an unbounded start needs to be turned into Some(0)? https://docs.rs/opendal/0.45.1/src/opendal/raw/http_util/bytes_range.rs.html#218

[sameer]

I guess I missed the doc line that indicates this behavior, but it's really unexpected for Rust:

..1024 means read bytes in range (n - 1024, n) of file

[Xuanwo]

I guess I missed the doc line that indicates this behavior, but it's really unexpected for Rust:

I'm working on changing this.

[Xuanwo]

This shoud already been fixed.

[sameer]

This shoud already been fixed.

Hey Xuanwo, that's good to hear. What commit/PR was that done in?

[Xuanwo]

Hey Xuanwo, that's good to hear. What commit/PR was that done in?

Fixed during a refactor: #4381

[sameer]

Hey Xuanwo, that's good to hear. What commit/PR was that done in?

Fixed during a refactor: #4381

Sounds good, thanks!