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

server,sql: remove usages of prettify on details pages #99450

Merged
merged 1 commit into from
Mar 25, 2023

Conversation

maryliag
Copy link
Contributor

The usage of prettify_statement and Pretty could cause OOM. Those were being used on statemen details and transaction insight details.
This commit removes those usages and add a very basic formatting function that can be used on the SQLBox component.

Part Of #91197

Release note (performance improvement): Removal of prettify usages that could cause OOM on Statement Details and Transaction Details page.

@maryliag maryliag added backport-22.1.x backport-23.1.x Flags PRs that need to be backported to 23.1 labels Mar 24, 2023
@maryliag maryliag requested review from a team March 24, 2023 02:40
@cockroach-teamcity
Copy link
Member

This change is Reviewable

Copy link
Contributor

@j82w j82w left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed 2 of 11 files at r1, all commit messages.
Reviewable status: :shipit: complete! 0 of 0 LGTMs obtained (waiting on @maryliag)


pkg/ui/yarn-vendor line 1 at r1 (raw file):

Subproject commit c0d256e029be53fae2abe2302a0988302a0bb4ec

Is this expected?

The usage of `prettify_statement` and `Pretty` could cause
OOM. Those were being used on statemen details and
transaction insight details.
This commit removes those usages and add a very basic
formatting function that can be used on the SQLBox
component.

Part Of cockroachdb#91197

Release note (performance improvement): Removal of prettify
usages that could cause OOM on Statement Details and
Transaction Details page.
Copy link
Contributor Author

@maryliag maryliag left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewable status: :shipit: complete! 0 of 0 LGTMs obtained (waiting on @j82w)


pkg/ui/yarn-vendor line 1 at r1 (raw file):

Previously, j82w (Jake) wrote…

Is this expected?

Added by mistake. Removed now

@maryliag
Copy link
Contributor Author

bors r+

Copy link
Contributor

@j82w j82w left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:lgtm:

Reviewed 7 of 11 files at r1, 1 of 2 files at r2, all commit messages.
Reviewable status: :shipit: complete! 1 of 0 LGTMs obtained

@craig
Copy link
Contributor

craig bot commented Mar 24, 2023

Build failed (retrying...):

@craig
Copy link
Contributor

craig bot commented Mar 24, 2023

Build failed (retrying...):

@craig
Copy link
Contributor

craig bot commented Mar 24, 2023

Build failed (retrying...):

@craig
Copy link
Contributor

craig bot commented Mar 25, 2023

Build failed (retrying...):

@craig
Copy link
Contributor

craig bot commented Mar 25, 2023

Build succeeded:

@blathers-crl
Copy link

blathers-crl bot commented Mar 25, 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 350f42b to blathers/backport-release-22.1-99450: 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.


error creating merge commit from 350f42b to blathers/backport-release-22.2-99450: 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.2.x failed. See errors above.


🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is dev-inf.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport-23.1.x Flags PRs that need to be backported to 23.1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants