Skip to content

feat(home): inventory drivers and count connections by provider - #595

Merged
huyplb merged 1 commit into
mainfrom
feat/home-drivers-inventory
Nov 6, 2026
Merged

huyplb merged 1 commit into
mainfrom
feat/home-drivers-inventory

Conversation

@huyplb

@huyplb huyplb commented Nov 6, 2026 •

Copy link
Copy Markdown
Contributor

Summary

  • Home → Drivers lists installed dialect packages, checks npm for newer versions, and Install / Update / Remove (queued, admin.drivers) without quoting the install directory in errors or action responses.
  • Connections by provider shows a count per dialect instead of names, hosts, and usernames.
  • Driver load ENOENT / npm path errors keep a package-relative file; a dropped TCP socket (ECONNRESET) is explained as the database closing before login.

Test plan

  • Open Home: Drivers lists packages; Connections by provider shows counts only (no credential details).
  • Install / Update / Remove a driver; overlapping clicks queue; a missing-file error does not include /Users/….
  • Select a saved Redshift credential when Docker is down: schema error mentions ECONNRESET and closing before login, not only read ECONNRESET.

Made with Cursor


Note

Medium Risk
Touches sensitive server-side driver installation/uninstall logic and new system APIs that run npm against production installs, which could break environments if misconfigured even though actions are gated behind admin.drivers.

Reviewed by Cursor Bugbot for commit a8dd395. Bugbot is set up for automated code reviews on this repo. Configure here.

Home can install, update, and remove dialect packages without quoting the
install directory, and the connections strip shows a count per dialect
instead of credential details.

Co-authored-by: Cursor <cursoragent@cursor.com>
@huyplb
huyplb merged commit e500958 into main Nov 6, 2026
9 of 11 checks passed
@huyplb
huyplb deleted the feat/home-drivers-inventory branch November 6, 2026 22:57
@cursor

cursor Bot commented Nov 6, 2026

Copy link
Copy Markdown
Contributor

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: 9ead08c3-84e9-46f3-abfe-4583b667621f)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant