Skip to content

tree: fix panic when encoding tuple#95009

Merged
craig[bot] merged 1 commit intocockroachdb:masterfrom
rafiss:fix-tuple-panic
Jan 17, 2023
Merged

tree: fix panic when encoding tuple#95009
craig[bot] merged 1 commit intocockroachdb:masterfrom
rafiss:fix-tuple-panic

Conversation

@rafiss
Copy link
Copy Markdown
Collaborator

@rafiss rafiss commented Jan 10, 2023

fixes #95008

This adds a bounds check to avoid a panic.

Release note (bug fix): Fixed a crash that could happen when formatting a tuple with an unknown type.

This adds a bounds check to avoid a panic.

Release note (bug fix): Fixed a crash that could happen when formatting
a tuple with an unknown type.
@rafiss rafiss requested review from a team and ZhouXing19 January 10, 2023 18:12
@cockroach-teamcity
Copy link
Copy Markdown
Member

This change is Reviewable

@rafiss
Copy link
Copy Markdown
Collaborator Author

rafiss commented Jan 17, 2023

@ZhouXing19 could you give this small fix a review when you have time?

@rafiss
Copy link
Copy Markdown
Collaborator Author

rafiss commented Jan 17, 2023

tftr!

bors r+

@craig
Copy link
Copy Markdown
Contributor

craig bot commented Jan 17, 2023

Build succeeded:

@craig craig bot merged commit 6fd5b04 into cockroachdb:master Jan 17, 2023
@blathers-crl
Copy link
Copy Markdown

blathers-crl bot commented Jan 17, 2023

Encountered an error creating backports. Some common things that can go wrong:

  1. The backport branch might have already existed.
  2. There was a merge conflict.
  3. The backport branch contained merge commits.

You might need to create your backport manually using the backport tool.


error creating merge commit from 3dd00e8 to blathers/backport-release-22.1-95009: POST https://api.github.com/repos/cockroachdb/cockroach/merges: 409 Merge conflict []

you may need to manually resolve merge conflicts with the backport tool.

Backport to branch 22.1.x failed. See errors above.


🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is otan.

@rafiss rafiss deleted the fix-tuple-panic branch January 18, 2023 08:27
mgartner added a commit to mgartner/cockroach that referenced this pull request Mar 15, 2023
This commit fixes a performance regression in pgwire encoding of tuples
introduced in cockroachdb#95009.

Informs cockroachdb#98306

Epic: None

Release note: None
craig bot pushed a commit that referenced this pull request Mar 16, 2023
98682: roachprod: provide workaround for long-running AWS clusters r=srosenberg a=renatolabs

In #98076, we started validating hostnames before running any commands to avoid situations where a stale cache could lead to unintended interference with other clusters due to public IP reuse. The check relies on the VM's `hostname` matching the expected cluster name in the cache. GCP and Azure clusters set the hostname to the instance name by default, but that is not the case for AWS; the aforementioned PR explicitly sets the hostname when the instance is created.

However, in the case of long running AWS clusters (created before host validation was introduced) or clusters that are created with an outdated version of `roachprod`, the hostname will still be the default AWS hostname, and any interaction with that cluster will fail if using a recent `roachprod` version. To remedy this situation, this commit includes:

* better error reporting. When we attempt to run a command on an AWS cluster and host validation fails, we display a message to the user explaining that their hostnames may need fixing.

* if the user confirms that the cluster still exists (by running `roachprod list`), they are able to automatically fix the hostnames to the expected value by running a new `fix-long-running-aws-hostnames` command. This is a temporary workaround that should be removed once we no longer have clusters that would be affected by this issue.

This commit will be reverted once we no longer have clusters created with the default hostnames; this will be easier to achieve once we have an easy way for everyone to upgrade their `roachprod` (see #97311).

Epic: none

Release note: None

98717: tree: fix tuple encoding performance regression r=mgartner a=mgartner

This commit fixes a performance regression in pgwire encoding of tuples
introduced in #95009.

Informs #98306

Epic: None

Release note: None

Co-authored-by: Renato Costa <renato@cockroachlabs.com>
Co-authored-by: Marcus Gartner <marcus@cockroachlabs.com>
blathers-crl bot pushed a commit that referenced this pull request Mar 16, 2023
This commit fixes a performance regression in pgwire encoding of tuples
introduced in #95009.

Informs #98306

Epic: None

Release note: None
blathers-crl bot pushed a commit that referenced this pull request Mar 16, 2023
This commit fixes a performance regression in pgwire encoding of tuples
introduced in #95009.

Informs #98306

Epic: None

Release note: None
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

3 participants