Mert
Mert
As I understand it, the spec as written doesn't seem to have a way for the client to resume an upload if it doesn't know or forgets the URI provided...
That's clever! It's maybe semantically incorrect since it isn't *really* a server error, but it addresses the use-case in question.
*Should* it allow the client to reject a greater offset? Even a streamed input can work with a greater offset.
I can say that as a server implementer, although supporting all RUFH clients is ideal, my priority is targeting URLSession and probably one or two more clients for other platforms....
I suppose that would still be fine as long as the client `DELETE`'s the upload resource if declined. The only issue is if they both can't accept the offset and...
> We haven't implemented upload cancellation in URLSession yet, so yeah it will be stuck Hmm, perhaps it should be an opt-in behavior through a request header to be safe....
> URLSession is not open source unfortunately. Please file feedbacks requesting this and send me the FB number, so it can be prioritized. Thank you for prioritizing this! I made...
The spec could probably use different wording to acknowledge that the server is allowed to send a greater offset and that the client should accept it if it's able. The...
I think OpenVINO likely has a memory leak here, but I haven't seen anything to suggest CPU or CUDA leaks memory. High RAM usage is not the same thing as...
> > High RAM usage is not the same thing as a leak, for reference. > > True, but not reasonable. If a container will naturally spike to 10-16GB memory...