Jack
Jack
i think that would work for your case, my issue is i simply don't use qbit. maybe we could instead use my check as a fallback if qbit url isn't...
I think a non client specific solution/fallback would probably be better we could just chuck it behind a "VERIFY_INTERNET_CONNECTION" flag and default to false?
>a) the queue response from the *arr apps add the torrent client connectivity status (would require a change on *arr side) id assume this too is dependent on client tbh...
if anyone else gets this i can confirm just changing the port fixes the issue, maybe theres a chance of something else stealing the port? Edit: actually this doesn't help,...
thanks @nezihtkadioglu still useful 3 years later
the version of npm is getting a bit out of date, i dont have permission to make releases on npm. i assume thats why. if the owner doesnt get back...
have worked around it by publishing to github instead please use this going forward`npm install -g https://github.com/swapnilsoni1999/spotify-dl`
``` The ability to find a video is dependent on the fact it is hosted on youtube, and even then there is a chance it is still incorrectly matched ```...
You would have to check the output logs to see how its searching, it should say `searching youtube with keywords` Then you can go to youtube and see what it...
can confirm i'm seeing its memory use creep up way too much But i have not a single log posted by autokuma during the increase. i assume its a lack...