Description
schema_index does not work in altimate-code0.5.2 with a BigQuery connection because the released CLI appears to run on a Bun-based binary, while the schema cache depends on better-sqlite3, which Bun does not support.
In my case:
warehouse_test succeeds for the configured BigQuery connectionschema_index fails even after installing the dependencies suggested by the CLI- this makes schema-cache-based features unusable (
schema_index, schema_cache_status, likely schema_search and sql_autocomplete too)
This looks like a runtime incompatibility in the released CLI, not a warehouse connectivity problem.
Steps to Reproduce
- Install
altimate-code0.5.2 on macOS arm64 - Configure a BigQuery warehouse connection
- Run
warehouse_test for the connection and confirm it succeeds - Run
schema_index for that warehouse - If the CLI asks for missing dependencies, install them:
npm install @google-cloud/bigquerynpm install better-sqlite3
- Run
schema_index again - See the error:
Failed to index warehouse schema: 'better-sqlite3' is not yet supported in Bun.
Expected Behavior
After installing the required warehouse and cache dependencies, schema_index should complete successfully.
At minimum, the CLI should either:
- use a Bun-compatible SQLite backend for schema cache
- avoid suggesting
better-sqlite3 in a Bun runtime where it cannot work - or provide a supported fallback/runtime path for schema indexing
Actual Behavior
warehouse_test succeeds, so the BigQuery connection is valid, but schema_index still fails due to the local schema cache implementation.
Observed errors during setup:
- first:
BigQuery driver not installed. Run: npm install @google-cloud/bigquery - after installing BigQuery driver and
better-sqlite3:
Failed to index warehouse schema: 'better-sqlite3' is not yet supported in Bun.
As a result, schema indexing cannot be completed in the released CLI build.
Environment
- OS: macOS
26.3 (arm64) - CLI version:
0.5.2 - Python version:
3.12.11 - Node version:
v25.6.0
Description
schema_indexdoes not work inaltimate-code0.5.2with a BigQuery connection because the released CLI appears to run on a Bun-based binary, while the schema cache depends onbetter-sqlite3, which Bun does not support.In my case:
warehouse_testsucceeds for the configured BigQuery connectionschema_indexfails even after installing the dependencies suggested by the CLIschema_index,schema_cache_status, likelyschema_searchandsql_autocompletetoo)This looks like a runtime incompatibility in the released CLI, not a warehouse connectivity problem.
Steps to Reproduce
altimate-code0.5.2on macOS arm64warehouse_testfor the connection and confirm it succeedsschema_indexfor that warehousenpm install @google-cloud/bigquerynpm install better-sqlite3schema_indexagainFailed to index warehouse schema: 'better-sqlite3' is not yet supported in Bun.Expected Behavior
After installing the required warehouse and cache dependencies,
schema_indexshould complete successfully.At minimum, the CLI should either:
better-sqlite3in a Bun runtime where it cannot workActual Behavior
warehouse_testsucceeds, so the BigQuery connection is valid, butschema_indexstill fails due to the local schema cache implementation.Observed errors during setup:
BigQuery driver not installed. Run: npm install @google-cloud/bigquerybetter-sqlite3:Failed to index warehouse schema: 'better-sqlite3' is not yet supported in Bun.As a result, schema indexing cannot be completed in the released CLI build.
Environment
26.3(arm64)0.5.23.12.11v25.6.0