Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Missing-driver error says "Searched 0 locations:" and names nowhere on a first run

Open Beginner friendly
#1,191 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
1-3 hours
Newbie friendliness
91/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
typescript
Domain
cli

Research direction

Open packages/drivers/src/resolve.ts and inspect the DriverNotInstalledError branch used when driverSearchRoots() returns no directories. Reproduce with ALTIMATE_DRIVER_DIR=/tmp/does-not-exist and any DuckDB operation. Done means the error clearly says there was nothing to search and names the directory created by the install command, without changing resolution behavior.

Written by the indexing model from the issue text.

Description

Drivers are deliberately not shipped with the binary, so "driver not installed" is a normal, expected state that users hit by design. That makes the message a primary UX surface — and in the first-run case it currently names nowhere to look.

driverSearchRoots() only returns directories that already exist. On a machine that has never installed a driver, every candidate root is absent, so it returns an empty array and DriverNotInstalledError renders:

DuckDB driver not installed.
Install it with the warehouse_install_driver tool, or run:
  npm install --prefix /home/user/.local/share/altimate-code/drivers duckdb
Searched 0 locations:

The last line ends in a colon with nothing after it. It reads like a truncated message or a bug in the CLI rather than the ordinary "you have not installed this yet" state, and it names no location at all.

Expected: the message should say plainly that there was nothing to search, and name the directory the install command creates, so the two failure modes stay distinguishable:

  • not installed anywhere (this case)
  • found on disk but failed to load (already handled separately, and already clear)

Reproduce with a compiled binary and a driver directory that does not exist:

ALTIMATE_DRIVER_DIR=/tmp/does-not-exist altimate ...  # any DuckDB operation

Scope: text and one branch in DriverNotInstalledError in packages/drivers/src/resolve.ts. No change to resolution behaviour.

Dominant language
TypeScript
Stars
813
Forks
134
Avg merge
2d 5h
Merged PRs (30d)
63

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from AltimateAI/altimate-code

All issues in AltimateAI/altimate-code

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.