deeplethe/utopia

Snowflake support landed in #239 with wiremock replays of the protocol, but it has never run against a Snowflake account with a programmatic access token or OAuth token. If you have one, please register it under System settings > Data sources as snowflake://:[email protected]/DB/SCHEMA?warehouse=WH then Test, mount it on a base, refresh the schema, and ask Chat a question that needs a query. What we need back: whether Test and the schema sync succeed, what the schema document looks like (table count, comments present or not), and one query_data round trip — the SQL the model wrote and what came back. Anything that fails, paste the error text; the engine surfaces the service's own message. See docs/decisions/0017 for what is deliberately not supported yet (key-pair JWT for Snowflake, Kerberos / OAuth2 for Trino).

Databricks support landed in #239 with wiremock replays of the protocol, but it has never run against a Databricks workspace with a running SQL warehouse. If you have one, please register it under System settings > Data sources as databricks://:TOKEN@host/sql/1.0/warehouses/ID?catalog=main then Test, mount it on a base, refresh the schema, and ask Chat a question that needs a query. What we need back: whether Test and the schema sync succeed, what the schema document looks like (table count, comments present or not), and one query_data round trip — the SQL the model wrote and what came back. Anything that fails, paste the error text; the engine surfaces the service's own message. See docs/decisions/0017 for what is deliberately not supported yet (key-pair JWT for Snowflake, Kerberos / OAuth2 for Trino).

The Notion source ships with parsing tests only. Nobody has pointed it at a real workspace. Unlike the other connectors there is no way to close this locally: Notion is closed-source SaaS with no emulator, and the open-source alternatives (AppFlowy, AFFiNE) do not speak its API. The risk is the same one that bit S3, which passed its construction tests and still broke on every bucket with a folder in it until a live endpoint was tried. What would help: create an internal integration, share one page with it, run the test. # Settings -> My connections -> New internal integration # then share a page with it from the page's ... menu UTOPIA_NOTION_TEST_TOKEN=ntn_xxx cargo test -p utopia-server notion A free workspace with a single page works. The token is read-only over exactly the pages you share with it. The parts most likely to be wrong, none of which construction tests reach: Pagination. Both /v1/search and /v1/blocks/{id}/children page at 100. A workspace with more than that exercises

The GCS source ships with construction tests only. Nobody has pointed it at a real bucket. That gap is not theoretical. S3 passed the same construction tests and still had a bug that broke every bucket anyone had clicked a "new folder" button in: object_store normalises the trailing slash off a directory marker, so the filter never fired, the GET asked for a key that does not exist, and the 404 took the whole sync down. Only a live endpoint found it. GCS shares that fetch path and adds its own builder configuration on top. fsouza/fake-gcs-server cannot close this. It implements the JSON API (/storage/v1/b/...) while object_store lists over the XML API (/bucket?list-type=2), and returns 404 there. The usual emulator does not exercise the path we use. What would help: run the existing test against a real bucket and report what happens. UTOPIA_GCS_TEST_ENDPOINT=https://storage.googleapis.com \ UTOPIA_GCS_TEST_BUCKET=your-bucket \ UTOPIA_GCS_TEST_KEY="$(cat service-account.json)" \ c