

-
Indeed, and this is a limitation of running networking libraries with no specific knowledge of the inner event loop. The article mentions using URI.openor net-http with async for parallel requests, but this only works if the underlying sockets aren't shared across fibers, something that more advanced libraries do for you. This is something I found out while testing httpx inside async , and it's something impossible to do atm without async-specific code (what async-http does), something which will hopefully be addressed. Do you know if polyphony suffers from the same limitation?
-
CodeRabbit
CodeRabbit: AI Code Reviews for Developers. Revolutionize your code reviews with AI. CodeRabbit offers PR summaries, code walkthroughs, 1-click suggestions, and AST-based analysis. Boost productivity and code quality across all major languages with each PR.
-
how is this diff from: https://github.com/digital-fabric/polyphony
-
It seems that Active Record compatibility is being discussed here. It's kind of cool that all it took for Sequel to be async-compatible was to replace Thread.current with Fiber.current.
-
It seems that Active Record compatibility is being discussed here. It's kind of cool that all it took for Sequel to be async-compatible was to replace Thread.current with Fiber.current.
-
there is a PR on puma for this: https://github.com/puma/puma/pull/2601
-