Igor Katson

Also please don't change stderr to stdout for logs. If you really need it for some reason, make it a parameter, but keep the current behavior.

Never heard of the *arr apps before, but overall don't mind adding features to make rqbit work with them. The new stats/all API proposed is ok at a high level....

wow, 567 MB/s?! what's the download / upload speed when this happens? As you can see CPU and memory are very low.

I don't know how to profile on Windows, but would be cool to know what is it doing. It's not obvious to me why it would use so much disk...

Is it consistent? Is it always proportional to the down/up speed? I'm developing on osx, never noticed anything unusual there. But if it's a windows only thing should be possible...

What this might be related to on Windows is it wasn't creating sparse files before, it was fixed here https://github.com/ikatson/rqbit/pull/390 I'll close the issue as stale, feel free to reopen

Thanks @mpmc for kind words! I don't see any downsides in doing the first 2 (baseURI), proxying rqbit's API sounds reasonable. We may keep the issue around just for these,...

Is the intention for Web / desktop UI or CLI too?

It is possible it's rqbit. Your usage sounds fine, I'll take a look

Hmm, I think doing it in the backend is the only correct way. The backend has a "timeout" query parameter that you can pass, and then you don't need to...