alefminus
alefminus
I created a relevant issue: #228
I will be happy to give it a go. Is anyone already working on this?
Well, I managed to reproduce your "Cannot start a runtime from within a runtime. This happens because a function..." error, so I guess this refers to the async runtime, which...
It is the postgres connection. ``` at 23:38:06 ❯ cargo +nightly run --features database --bin columnq -- sql -t ***@***.***/alon' 'select version()' Compiling columnq v0.5.0 (/home/alon/src/roapi/columnq) Compiling columnq-cli v0.3.0 (/home/alon/src/roapi/columnq-cli)...
Thanks. I verified it is still present in 0.7.1-717-gdd8134b6 (git describe --tags), stack trace unchanged. Any pointers to trying to fix it? (on the low probability I manage to find...
That should work fine. The second part, reloading the client (i.e. client notices websocket died, goes into reconnection loop, then connection works, reinits) is the part I'm less inclined to...
cool! thanks a lot, I'll check it soon. With tests and everything too :)
I've opened #773 after testing, otherwise works great, thanks!
When trying to submit this bug I managed to reproduce the second problem, namely staleness: 1. case one, above: cell 4 fails to complete running, interrupting shows above stack trace....
Note 3: joblib's Parallel/delayed seems to work fine