Snowflake needs someone with a real cluster to run its test
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- Half a day
- Newbie friendliness
- 30/100
Research direction
Prerequisite is a real Snowflake account with a programmatic access token or OAuth token — without one this issue cannot be started. Register the source under System settings > Data sources with the connection string snowflake://:[email protected]/DB/SCHEMA?warehouse=WH, then run Test, mount it on a base, refresh the schema, and ask Chat a question that triggers a query. Report back: Test/schema-sync result, schema document shape (table count, comments), one query_data round trip (model-written SQL and response), and verbatim error text for anything that fails. Read docs/decisions/0017 first for what is deliberately unsupported; the wiremock replay tests from PR #239 are the existing coverage being validated.
Written by the indexing model from the issue text.
Description
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).
- Dominant language
- Rust
- Stars
- 8.1k
- Forks
- 1.1k
- Avg merge
- 21h 2m
- Merged PRs (30d)
- 263
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from deeplethe/utopia
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 56/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
deeplethe/utopia#1341 · 1 comment ·
Maintainers usually reply within 1 day
-
bug
Difficulty 5/5 Over a week Newbie friendliness 48/100
deeplethe/utopia#1338 · 2 comments ·
Maintainers usually reply within 1 day
All issues in deeplethe/utopia
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Maintainers usually reply within 1 day
-
o8 next debug build aborts on Glass to Dark appearance switch (nil identifier messaged before check)Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
hurttlocker/o8#5112 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
Maintainers usually reply within 1 day
-
memory_patch_page drops the `#` of headings like `## Notes on C#`Possibly taken @viniciusdsandrade claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
akitaonrails/ai-memory#1859 ·
Maintainers usually reply within 1 day
-
bug prio:p3 triaged ux
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day