Yahia M.

Hi Guilherme, thanks for the detailed writeup, and glad you're back up and running. One small thing worth flagging: the UUID in that error was your lakehouse database, which had become the session's default after my_db was dropped. Dropping lakehouse.main then removed the schema that session startup falls back to, which is why DDL failed while fully-qualified SELECTs kept working. Recreating a database with a main schema (as you did) clears it. Let me know if you have any questions!

Can you clarify what you mean here with separate package? Any context on your use case with the CI would help!

Hi, yes! We update this json (docs here) with the latest MotherDuck supported DuckDB version. Currently the latest supported version is 1.5.2 so 1.5.3 (which was just released this week) is not yet compatible! Let me know if you have any questions about this! Happy to help set up version pinning to the latest supported version for your pipelines.

Hi Joe C., thanks again for raising this! The getdot.ai MotherDuck connector has been updated and now works, allowing you to model your data in the app. Let me know if you have any further questions! Note: when setting the connection, it might be best to set the attach mode to single: md:database_name?attach_mode=single&motherduck_token=YOUR_TOKEN_HERE

Hi Joe, thanks for flagging this! I was able to reproduce the same indefinite "initialising" state, so we have a clean repro to work from. We're looking into it and will reach out to the getdot.ai team for more info, and I'll follow up here as soon as we know more. If you happen to see any errors or log output from getdot.ai beyond "initialising", feel free to share, otherwise no action needed on your end for now.

Hi Bill (and Pat), we're investigating this issue! (also responded on the public support channel)

This is a really cool project jwalzer! A few quick thoughts:

Nice work putting this together!

Hi Jonah, just following up here, are you currently unblocked? Let me know if you face any further issues!

I see that the database my_db is missing for this service account. Can you connect using this service account using a read/write token (which will automatically create the database)? This can be done easiest by impersonating the service account in the UI. After connecting using a read/write token, we can check the Dive again and I will monitor things on our side!

Hi Jonah, I'm taking a look!