Skip to content

[Kit] Preserve stack traces on unknown CLI errors - #5910

Open
imharjot wants to merge 1 commit into
drizzle-team:betafrom
imharjot:fix/drizzle-kit-preserve-stack
Open

imharjot wants to merge 1 commit into
drizzle-team:betafrom
imharjot:fix/drizzle-kit-preserve-stack

Conversation

@imharjot

@imharjot imharjot commented Jun 18, 2026 •

Copy link
Copy Markdown

Unexpected schema-loading failures currently print only the error message, hiding the file and line needed to debug them. Keep the stack and cause chain in human-readable CLI output, with a cycle guard for malformed causes. Existing typed errors, SQL diagnostics and JSON envelopes retain their current handling.

Rebased onto beta. Added formatter coverage and a regression that runs the real generate CLI against a throwing schema, checking the source location, cause and unchanged JSON response.

Validation: both CLI regression suites passed (63 tests), targeted oxlint reported zero warnings/errors, dprint passed, and the drizzle-kit build completed. The commit is signed and verified by GitHub.

@imharjot
imharjot force-pushed the fix/drizzle-kit-preserve-stack branch from f0ed1f4 to 9213bef Compare October 4, 2026 13:56
@imharjot

imharjot commented Oct 4, 2026 •

Copy link
Copy Markdown
Author

Rebased onto current beta and preserved the newer typed-error and JSON output paths. A real throwing-schema regression now checks that human-readable output includes the schema location and cause, while JSON stays unchanged. All 63 tests in the two CLI suites, targeted lint, formatting and the package build pass locally. The replacement commit is signed and verified.

The refreshed GitHub workflows are marked action_required. Could a maintainer approve or unblock the fork workflows so the remote checks can run?

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