Print internal exception stack traces on failed transaction rollback #18023
Conversation
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
|
Thanks! |
github-actions bot
pushed a commit
to duckdb/duckdb-r
that referenced
this pull request
Jun 27, 2025
Print internal exception stack traces on failed transaction rollback (duckdb/duckdb#18023) Make test more lenient (duckdb/duckdb#18022)
github-actions bot
added a commit
to duckdb/duckdb-r
that referenced
this pull request
Jun 27, 2025
Print internal exception stack traces on failed transaction rollback (duckdb/duckdb#18023) Make test more lenient (duckdb/duckdb#18022) Co-authored-by: krlmlr <krlmlr@users.noreply.github.com>
JelteF
added a commit
to JelteF/duckdb
that referenced
this pull request
Jun 30, 2025
Since duckdb#18023 stack traces are now being added in ConstructFinalMessage. However they were not using the "Stack trace:" prefix that is used for all other stack traces. This makes it hard extract/remove these specific stack traces from the resulting error message. This adds that same prefix.
JelteF
added a commit
to JelteF/duckdb
that referenced
this pull request
Jun 30, 2025
Since duckdb#18023 stack traces are now being added in ConstructFinalMessage. However they were not using the "Stack trace:" prefix that is used for all other stack traces. This makes it hard extract/remove these specific stack traces from the resulting error message. This adds that same prefix.
Mytherin
added a commit
that referenced
this pull request
Jul 1, 2025
Since #18023 stack traces are now being added in ConstructFinalMessage. However they were not using the "Stack trace:" prefix that is used for all other stack traces. This makes it hard extract/remove these specific stack traces from the resulting error message. This adds that same prefix.
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.
Also ensures that
ErrorData::ConstructFinalMessage()always appends the stack trace.Close https://github.com/duckdblabs/duckdb-internal/issues/5166.