Xuanwo
> and just remove support Do you mean we will return an error if users try to `range_read(..xxx)`?
In our current logic, we will never send `..1024` to the underlying services. Because we always need to calculate the correctl offset and size before sending requests. https://github.com/apache/incubator-opendal/blob/7166d873a0a1d3a502f17116777d81271532e1f5/src/layers/complete.rs#L173-L185 I think...
We should treat this feature as a new capability.
> And `pdoc` doesn't pickup docstrings in `.pyi` files with current setup. Related to https://github.com/mitmproxy/pdoc/issues/239?
I am not satisfied with the current state of the Layers API. Therefore, I am fine if we do not document any API related to layers at this time. Maybe...
Hello, @messense. I apologize for the broken CI. It has been fixed now. Kindly update your branch and try again.
Added https://github.com/datafuselabs/opendal/issues/1279
Closing, we are about to start our tracking issues for opendal 2024.
Do we need to build the C-binding before starting on the Java binding?
We don't need to address all possible problems right now. We can document this limitation and fix it in the future.