colexecerror: some runtime panics are no longer recovered from #133617
Labels
branch-master
Failures and bugs on the master branch.
branch-release-23.1
Used to mark GA and release blockers, technical advisories, and bugs for 23.1
branch-release-23.2
Used to mark GA and release blockers, technical advisories, and bugs for 23.2
branch-release-24.1
Used to mark GA and release blockers, technical advisories, and bugs for 24.1
branch-release-24.2
Used to mark GA and release blockers, technical advisories, and bugs for 24.2
branch-release-24.3
Used to mark GA and release blockers, technical advisories, and bugs for 24.3
C-bug
Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.
T-sql-queries
SQL Queries Team
It appears that as of a recent improvement to the stack examination when recovering from panics in #123277 we no longer convert some runtime panics into internal errors (e.g. the reproduction from #130402 (comment) crashes the server). This is because we see
runtime.panicdottypeE
as the "panic emitted from" line, and my guess is thatdebug.Stack()
- that we used before the patch - omits all runtime related lines from the stack.Jira issue: CRDB-43709
The text was updated successfully, but these errors were encountered: