Benjamin Egelund-Müller

Also bumped into this. Running > (new BN(null)).imuln(0).toString(10) Crashes Node with # # Fatal error in , line 0 # API fatal error handler returned after process out of memory...

Hello all! I see it's been a while since this issue was created, so I wanted to ask if this has been solved or has a known workaround? Our use...

@ziyilin Thank you for sharing this, it certainly seems like a promising workaround for our use case! Do you have a sense of whether this would also work on Mac/Windows?...

Just to keep things organised, can we close either the original PR (https://github.com/rilldata/rill-developer/pull/896) or this one? If you don't have permission to push to existing PRs, ping Himadri and ask...

Aditya's right that we'll need to be able to handle dynamic runtime URLs. Unfortunately the runtime won't always be at a predictable URL – for example, we may need to...

Let's make this issue the canonical reference for the runtime integration. @AdityaHegde, can you update/comment with notes on the bugs you're still encountering?

Did some more debugging – it appears that it’s a DuckDB bug where queries with deeply nested nodes (UNIONs are represented with nested ASTs, not as lists) fail when not...

Filed a bug report in DuckDB: https://github.com/duckdb/duckdb/issues/4802

The bug report above identifies a stack overflow bug that might be what we're seeing in Go, but doesn't manage to reproduce the hanging problem observed in Go. One hypothesis...

Hey, took a look, and looks like it still needs: - Test cases showing the `CREATE SOURCE` syntax in action - Protobuf AST that lets us access `CREATE SOURCE` from...