Repository navigation
fix(features): remaining raw exception messages say what went wrong in plain words and are logged (#1761, part 4) - #1799
Merged
Conversation
github-actions
Bot
added
enhancement
This was referenced Oct 25, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #1761 (with #1794, #1795, #1798).
The rest of the raw
'...: $e'user-visible messages inlib/featuresgo throughfailureMessage: table views (SQLite, PostgreSQL, extension), the connection forms' Test result (theerror: ...format thatconnectionTestMessageparses is kept), extension install and driver restart, the MCP start error and the SQL workspace (cancel, open and save file). Driver errors getDatabaseDriver.*; the failed driver restart is logged once and the same text goes to the session error and the toast.Left as they are on purpose: the start-up recovery screen and the update dialogs (their text is the point), parse errors of the user's own JSON, the ERD export messages and the file-open message that names the file.
No test depended on the changed texts. Not run locally, CI will.