[11:43] <ersi> soultcer: oh, oopsy. Yeah.
[11:58] <soultcer> There seems to be some kind of bug that makes the standalone instances freeze
[12:03] <ersi> and mine just froze when you wrote that
[12:04] <ersi> naw, but the requests takes a lot longer
[12:04] <ersi> oh, 'cause of socket error: timed out
[12:05] <soultcer> Mine froze completely, dunno why
[12:06] <ersi> 25od5sk, 25od5t0 etc - are those snipurl?
[12:08] <soultcer> Yeah
[12:08] <ersi> If I poke the failing codes manually, it works just fine. The tinyback instance is having issues though :o
[12:08] <ersi> and my instance seems to only do snipurl
[12:09] <ersi> oh.. I got multiple snipurl jobs running o_o
[12:10] <ersi> no I don't, the pipeline/Web-UI has just fucked up
[12:22] <soultcer> That should fix the snipurl issues
[12:22] <GitHub73> [tinyback] soult pushed 2 new commits to master: https://github.com/soult/tinyback/compare/32de98d881d0...365bb422950f
[12:22] <GitHub73> tinyback/master 365bb42 David Triendl: services.HTTPService: Add http_keepalive property...
[12:22] <GitHub73> tinyback/master 5d5cd18 David Triendl: services.Postly: Treat connection timeout as being blocked
[12:23] <soultcer> The HTT exception always happened after an URL not found page, and in that special case, the HTTP connection was reused by tinyback
[12:30] <ersi> ahh
[12:32] <soultcer> Snipurl pretens it supports http-keep-alive, but it clearly doesn't
[12:32] <soultcer> *pretends
[16:43] <GitHub134> [tinyback] soult pushed 1 new commit to master: https://github.com/soult/tinyback/commit/32e8245f930055fbd672e2ca8658791b2acbbdbd
[16:43] <GitHub134> tinyback/master 32e8245 David Triendl: services.Postly: Send user-agent