Fantix King
Fantix King
`async_task` is actually in use at line 383?
Thanks for the PR! However, I think we should try to connect to all resolved addresses and use the first one that succeeded, in the same way as asyncio does....
Private functions also return `i32`, but it's less of an issue because they are not publicly visible on WASM level.
> The issue with the start function is that we can't use any FFI that relies on the current module. That's the same reason why WASI preview 1 defined another...
Which version of server are you running on? Will you be able to set some environment variables to get more details in server log: ``` EDGEDB_DEBUG_SERVER_PROTO=1 EDGEDB_DEBUG_PGSERVER=1 ```
In that case, could you pls get the `stage_no` in `select sys::get_version();`?
No worries! Theoretically (by reviewing the code) this may be caused by a certain type of weird network error that only closes half of the client connection during a slow...
I think I eventually reproduced this issue - it involves a few steps happening in a very subtle order. Let me push a fix with an explanation of the issue.
Another reference for the time API: https://docs.edgedb.com/database/stdlib/datetime
> we would like to have this package landed, could it be submitted as a standalone PR independently Sure, tho I'm outta town for 2 weeks, I can only reply...