Issue with SIGSEGV on v0.3.7 as included by prologue with nim 2.0.0

[ahungry]

I'm getting a similar problem to the OP here: planety/prologue#227 - it only happens when using httpx as the prologue back end (asynchttpserver is fine via prologue's -d:usestd flag).

I noticed some commentary about httpbeast and nim 2.0 here:

nim-lang/Nim#21422

Where I see a common name on both areas (@ringabout ) - so I am guessing this is known and maybe being worked on?

TIA!

[ahungry]

I think this is the resolution on httpbeast, but only in HEAD as of this writing:

dom96/httpbeast#89

[ringabout]

I don't think it's the cause. Besides, httpx supports startup events preceding httpbeast.

[ringabout]

Whether nim-lang/Nim#21422 is fixed is not clear to me.