Skip to content

Conversation

JelteF
Copy link
Contributor

@JelteF JelteF commented Jun 30, 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.

@JelteF
Copy link
Contributor Author

JelteF commented Jun 30, 2025

I'd like this change to be backported to the 1.3 branch (since the stack trace addition is there too). Should I create the PR against that branch, or against main?

@carlopi
Copy link
Contributor

carlopi commented Jun 30, 2025

I'd like this change to be backported to the 1.3 branch (since the stack trace addition is there too). Should I create the PR against that branch, or against main?

1.3.2 will be build from the branch v1.3-ossivalis, so idea is sending a PR vs that branch (require usually cherry-pick + force-push + changing PR target, or just close + reopen on a different branch).

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 JelteF force-pushed the add-stack-trace-marker branch from 50ebc67 to cbcfa3a Compare June 30, 2025 09:00
@JelteF JelteF changed the base branch from main to v1.3-ossivalis June 30, 2025 09:00
@duckdb-draftbot duckdb-draftbot marked this pull request as draft June 30, 2025 09:01
@JelteF
Copy link
Contributor Author

JelteF commented Jun 30, 2025

require usually cherry-pick + force-push + changing PR target

Done

@JelteF JelteF marked this pull request as ready for review June 30, 2025 09:02
@Mytherin Mytherin merged commit 39c99b2 into duckdb:v1.3-ossivalis Jul 1, 2025
51 checks passed
@Mytherin
Copy link
Collaborator

Mytherin commented Jul 1, 2025

Thanks!

github-actions bot pushed a commit to duckdb/duckdb-r that referenced this pull request Jul 1, 2025
krlmlr added a commit to krlmlr/duckdb-r that referenced this pull request Jul 9, 2025
krlmlr added a commit to krlmlr/duckdb-r that referenced this pull request Jul 9, 2025
github-actions bot pushed a commit to krlmlr/duckdb-r that referenced this pull request Jul 9, 2025
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.

3 participants