[BUG] #148 still an issue about docker-deluge HOT 11 CLOSED

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

from docker-deluge.

A human has marked this issue as invalid, this likely happened because the issue template was not used in the creation of the issue.

from docker-deluge.

Nothing more frustrating than trying to help only to be met with silly non-replies, non-communication. Great going!

from docker-deluge.

Your issue was marked as invalid due to not completely the issue template.

from docker-deluge.

A human has marked this issue as invalid, this likely happened because the issue template was not used in the creation of the issue.

What part of the template is missing?

from docker-deluge.

this.

from docker-deluge.

First:
Click the mentioned other bug report - #148, look at the log.

Second:
Vanilla means I didn't change anything in the docker-compose from what you distribute.

from docker-deluge.

Honestly, if you can't be bothered to answer the few questions we ask, we can't be bothered to look into your issue. Thanks for reaching out. Feel free to open a new issue if decide to comply with our requests.

from docker-deluge.

No, I get that 100%. I do issue triage too. I'm just not looking for excuses not to consider reports. If your time is as precious as you'd like me to believe by throwing this hissy fit, you would have made that 1 extra click required to "complete" your view on the issue at hand.

Incredible how poor your attitude is, as a group. 3 people replied, and all 3 in the same vein...

from docker-deluge.

occasionally crash

this is not enough info to troubleshoot or reproduce, hence why more info is requested

from docker-deluge.

Well, I'm sorry, but I have no idea why or what exactly triggers it to crash and the log is as succinct as you saw. The behavior I saw consistently around crashes is when I add multiple things at once (or sequentially) to download. .torrent or magnet - doesn't matter.

I don't know how to get you more info to troubleshoot or reproduce.

In fact, given the logs, I've wondered if it's deluge itself crashing because of a bug, or libtorrent causing it to. I've already filed a bug with deluge a while back but nothing became of it.

So if this isn't enough, I get it, and it's cool. Thanks for looking into it.

from docker-deluge.