Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

<reported error>: error.go:77: func1: unexpected error from the vectorized runtime: %+v #42871

Closed
sentry-io bot opened this issue Nov 30, 2019 · 2 comments · Fixed by #42968
Closed

<reported error>: error.go:77: func1: unexpected error from the vectorized runtime: %+v #42871

sentry-io bot opened this issue Nov 30, 2019 · 2 comments · Fixed by #42968
Assignees
Labels
C-bug Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.

Comments

@sentry-io
Copy link

sentry-io bot commented Nov 30, 2019

Sentry Issue: COCKROACHDB-16Z

<reported error>: error.go:77: func1: unexpected error from the vectorized runtime: %+v
  File "/go/src/github.com/cockroachdb/cockroach/pkg/sql/colexec/execerror/error.go", line 77, in func1
  File "/usr/local/go/src/runtime/panic.go", line 522, in gopanic
  File "/go/src/github.com/cockroachdb/cockroach/pkg/col/coldata/vec.go", line 160, in NewMemColumn
  File "/go/src/github.com/cockroachdb/cockroach/pkg/col/coldata/batch.go", line 142, in AppendCol
  File "/go/src/github.com/cockroachdb/cockroach/pkg/sql/colexec/builtin_funcs.go", line 49, in Next
...
(22 additional frame(s) were not displayed)

*errors.errorString
*safedetails.withSafeDetails: unexpected error from the vectorized runtime: %+v (1)
error.go:77: *withstack.withStack (2)
*assert.withAssertionFailure
(check the extra data payloads)
@itsbilal
Copy link
Member

Seeing a bit of a spike of these events recently, though they're all on one cluster running 19.2.1, so it might not be a legitimate bug and doesn't seem urgent. @yuzefovich or someone from SQL exec, mind taking a quick look when you can?

@jordanlewis jordanlewis added the C-bug Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior. label Dec 2, 2019
@yuzefovich
Copy link
Member

I think I found the root cause. PR incoming.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-bug Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants