Archie Sarre Wood
Archie Sarre Wood
This is because the package was not published after the last update. @ItsMeBrianD is going to add a changeset and republish
In general while the dev server is open. I suspect we arent closing the connection properly after running queries or something like that
Do you suspect this is an issue with the underlying library? or the way we are implementing it? https://github.com/motherduckdb/duckdb-async
I might be wrong, but I think there isn't a close method implemented in duckdb-async?
I am wrong: https://github.com/motherduckdb/duckdb-async/blob/868886e3beac197c97fe30673f894938e806c646/src/duckdb-async.ts#L322
this remains unresolved as yet!
It may be helpful to surface errors from other connectors. I am unsure about this
The suggested approach is to upload a key file, which auto populates this field
Ah yes this looks like a bug As a workaround, you can add the files to your sources directly like: `/sources/big_query/connection.yaml` ```yaml name: big_query type: bigquery options: location: US authenticator:...
> Also, I understand the convenience of the field being auto-populated during certain workflows, but why can't it be configured manually at the same time? for most connectors you can,...