It does not, in fact it the error recurred a few more times in the terminal. On the notebook end, it somewhat works where it successfully runs like the first time, and then becomes unresponsive.
The same error? duckdb 1.0 should have a function called extract_statements. That’s perplexing. You’re sure the correct Python environment is activated?
If you have an example that you could share that I can try to reproduce, that would help. I know we have a bug in which we enable SQL cells even if the duckdb version is incompatible with marimo. I am pushing up a fix for that.
So far I'm not having any troubles, and have run the cells multiple times, but can share the next time I experience it. Thanks! I do think it may have the duckdb version. FWIW I have Anaconda as the python environment (at least I think that's what you mean by python environment)
