Good point. To those unaware, the time.After is equivalent to time.NewTimer(d).C, but "the underlying Timer is not recovered by the garbage collector until the timer fires" (quote from the doc). That slowAPICall…
There's an ugly bug in http.TimeoutHandler though - it obscures stack traces so that it's impossible to use them to locate panic in decorated handler: https://github.com/golang/go/issues/27375
> The latter two positions say "San Francisco", but we have a growing engineering office in Berlin with people working on the live video CDN and fraud detection. These positions can be filled in Berlin and we'd be very…
Yes, there is. https://github.com/KeepSafe/aiohttp It's hard to write an asynchronous ORM though. Your options are either to use some existing synchronous ORM (like SQLAlchemy) in a thread pool (`loop.run_in_executor`)…
Good point. To those unaware, the time.After is equivalent to time.NewTimer(d).C, but "the underlying Timer is not recovered by the garbage collector until the timer fires" (quote from the doc). That slowAPICall…
There's an ugly bug in http.TimeoutHandler though - it obscures stack traces so that it's impossible to use them to locate panic in decorated handler: https://github.com/golang/go/issues/27375
> The latter two positions say "San Francisco", but we have a growing engineering office in Berlin with people working on the live video CDN and fraud detection. These positions can be filled in Berlin and we'd be very…
Yes, there is. https://github.com/KeepSafe/aiohttp It's hard to write an asynchronous ORM though. Your options are either to use some existing synchronous ORM (like SQLAlchemy) in a thread pool (`loop.run_in_executor`)…