-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
sql: panic when interacting with BIT array #95543
Labels
C-bug
Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.
O-community
Originated from the community
T-sql-queries
SQL Queries Team
Comments
SteveLeungYL
added
the
C-bug
Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.
label
Jan 19, 2023
Hello, I am Blathers. I am here to help you get the issue triaged. Hoot - a bug! Though bugs are the bane of my existence, rest assured the wretched thing will get the best of care here. I was unable to automatically find someone to ping. If we have not gotten back to your issue within a few business days, you can try the following:
🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is dev-inf. |
blathers-crl
bot
added
O-community
Originated from the community
X-blathers-untriaged
blathers was unable to find an owner
labels
Jan 19, 2023
This was referenced Jan 20, 2023
craig bot
pushed a commit
that referenced
this issue
Jan 27, 2023
95153: sql/schemachanger: Drop function in declarative schema changer r=chengxiong-ruan a=chengxiong-ruan This pr contains 3 commits: 1. add function descriptor elements definition 2. a simple rename of RemoveViewBackReferencesInRelation to RemoveBackReferencesInRelation 3. drop function logics Part of: https://cockroachlabs.atlassian.net/browse/CRDB-19495 95524: kvserver: fix race on Replica.tenantLimiter r=tbg a=pavelkalinnikov When Replica is being destroyed, it can set tenantLimiter to nil. However, all accessors assume synchronization through IsInitialized atomic check and that this field can't be modified after the replica is initialized. There is no particular need in nullifying this limiter, the replica is going away soon, so this commit removes this line in order to fix the data race. Fixes #95345 Epic: none Release note: none 96002: eval: fix internal error casting bytes to bit r=msirek a=msirek Fixes #95543 Release note (bug fix): This patch fixes an internal error which may occur in the SHOW RANGE FROM TABLE statement when the FOR ROW clause specifies a BYTE literal and the corresponding column data type is BIT. 96030: docgen: remove redundant SQL diagrams r=nickvigilante a=taroface Diagrams updated in #95591 were not generating HTML files as intended because of some redundant lines in the code. This removes the redundancies per `@nickvigilante.` Epic: none Release note: none Release justification: non-production code change 96048: optbuilder: fix internal error in LATERAL queries with redundant function calls r=DrewKimball,mgartner a=msirek Fixes #95615 Function `optbuilder.Builder.buildZip` may try to build 2 identical function calls into 2 zip expressions, each one adding one or more columns to the output. However, if buildZip's called to `buildScalar` recognizes a scalar expression has already been built, it skips adding a new output columns and returns the previously-built output column. This mismatch in the number of output columns actually built, and the number of columns communicated to the parent expression via `outScope` confuses the execution engine, and in this case we error out because the expected data type of one column doesn't match the actual data type. The fix is to skip building zip expressions with redundant expressions which already exist in `outScope`. Release note (bug fix): This patch fixes rare internal errors in LATERAL queries with redundant function calls. 96099: upgrades: share a column family for the new tenant columns r=ajwerner a=knz Fixes #96093. The previous change in that area was causing the new columns to be (implicitly) added into separate column families. However, we're expecting (from the bootstrap schema) to use a single column family for them. This patch fixes that. Release note: None Co-authored-by: Chengxiong Ruan <[email protected]> Co-authored-by: Pavel Kalinnikov <[email protected]> Co-authored-by: Tobias Grieger <[email protected]> Co-authored-by: Mark Sirek <[email protected]> Co-authored-by: Ryan Kuo <[email protected]> Co-authored-by: Raphael 'kena' Poss <[email protected]>
msirek
pushed a commit
to msirek/cockroach
that referenced
this issue
Jan 27, 2023
Fixes cockroachdb#95543 Release note (bug fix): This patch fixes an internal error which may occur in the SHOW RANGE FROM TABLE statement when the FOR ROW clause specifies a BYTE literal and the corresponding column data type is BIT.
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.
O-community
Originated from the community
T-sql-queries
SQL Queries Team
Describe the problem
The latest version of the CockroachDB (9735954) shows
Internal Error
when executing the following query:To Reproduce
Here is the detail steps to reproduce the bug.
make install
in the root repository folder../cockroach demo
, and then paste the PoC query to the cockroach cli environment.Internal Error
and log the stack information.Expected behavior
The select statement should be executed correctly and outputs empty result.
Additional data / screenshots
Here is the outputted stack trace:
Environment:
./cockroach demo
)Additional context
The
Internal Error
can be reproduced byCockroachDB v23.1 Testing Releases
,v22.2.2
andv22.1
. We haven't tested earlier versions.Jira issue: CRDB-23581
The text was updated successfully, but these errors were encountered: