OSError: [Errno 107] Transport endpoint is not connected about bittornado

[effigies]

Thanks for all the reports! Three tracebacks will probably take a little time to track down and fix. Started an issue_30 branch I'll work on (no changes yet).

[Yuuki2012]

Sure thing ^^ at least this is not a dead project, I'm glad I can be of some help! :)

[Yuuki2012]

I figured that when this error occurs, peers are unable to connect, pretty much the same as the tracker being offline -- I can't scrape either.

[effigies]

Okay. So it looks like this is probably related to #23, which may be a failure to register clients. So removing a client will fail because it's not there.

Either way, there are also some bugs here that aren't that. Updated issue_30 to take care of these tracebacks. Will start a PR.

But yeah, need to dig in and figure out what's happening here.

[effigies]

Can you check issue_30, now? I pushed a fix to a bug I accidentally introduced in #28, which caused NAT'd peers that are crypto-enabled to push the tracker into an infinite loop.

[Yuuki2012]

Okay, let's see ^^

[effigies]

Any luck?

[Yuuki2012]

I haven't ran into the problem for now, guess you can close it. ^^ it's been running fine ever since.