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

release-23.2: cluster-ui: fix insights page crash #120210

Merged
merged 2 commits into from
Mar 12, 2024

Conversation

blathers-crl[bot]
Copy link

@blathers-crl blathers-crl bot commented Mar 11, 2024

Backport 1/1 commits from #120137 on behalf of @laurenbarker.

/cc @cockroachdb/release


When the Schema Insights Type is uninitialized, the Schema Insights tab would crash because a string method was being called on undefined. The types are all correct, but because strict mode isn't enabled, it's not considered a type error.

Now the string method is only called if the Schema Insights Type is defined.

Fixes: https://cockroachlabs.atlassian.net/browse/CC-27391

Release note (bug fix): Fixes intermittent page crash on the Schema Insights view.


Release justification: Without this fix, the Schema Insights page occasionally crashes and customers are unable to see any schema insights. Backporting also keeps DB Console and CC Console in sync.

When the Schema Insights Type is unitialized, the Schema Insights tab
would crash because a string method was being called on `undefined`. The
types are all correct, but because strict mode isn't enabled, it's not
considered a type error.

Now the string method is only called if the Schema Insights Type is
defined.

The same type issue that was fixed for `filters.schemaInsightType` was
fixed for all other filters in the same file as well.

Fixes: https://cockroachlabs.atlassian.net/browse/CC-27391

Release note (bug fix): Fixes intermittent page crash on the Schema
Insights view.
@blathers-crl blathers-crl bot requested a review from a team March 11, 2024 15:08
@blathers-crl blathers-crl bot force-pushed the blathers/backport-release-23.2-120137 branch from 7398253 to 1f3d096 Compare March 11, 2024 15:08
@blathers-crl blathers-crl bot added blathers-backport This is a backport that Blathers created automatically. O-robot Originated from a bot. labels Mar 11, 2024
Copy link
Author

blathers-crl bot commented Mar 11, 2024

Thanks for opening a backport.

Please check the backport criteria before merging:

  • Backports should only be created for serious
    issues
    or test-only changes.
  • Backports should not break backwards-compatibility.
  • Backports should change as little code as possible.
  • Backports should not change on-disk formats or node communication protocols.
  • Backports should not add new functionality (except as defined
    here).
  • Backports must not add, edit, or otherwise modify cluster versions; or add version gates.
  • All backports must be reviewed by the owning areas TL and one additional
    TL. For more information as to how that review should be conducted, please consult the backport
    policy
    .
If your backport adds new functionality, please ensure that the following additional criteria are satisfied:
  • There is a high priority need for the functionality that cannot wait until the next release and is difficult to address in another way.
  • The new functionality is additive-only and only runs for clusters which have specifically “opted in” to it (e.g. by a cluster setting).
  • New code is protected by a conditional check that is trivial to verify and ensures that it only runs for opt-in clusters. State changes must be further protected such that nodes running old binaries will not be negatively impacted by the new state (with a mixed version test added).
  • The PM and TL on the team that owns the changed code have signed off that the change obeys the above rules.
  • Your backport must be accompanied by a post to the appropriate Slack
    channel (#db-backports-point-releases or #db-backports-XX-X-release) for awareness and discussion.

Also, please add a brief release justification to the body of your PR to justify this
backport.

@blathers-crl blathers-crl bot added the backport Label PR's that are backports to older release branches label Mar 11, 2024
@cockroach-teamcity
Copy link
Member

This change is Reviewable

This bug fix needs to be pulled into CC Console, so publishing is
required.

Epic: none

Release note: None
@laurenbarker laurenbarker requested a review from rgcase March 11, 2024 21:45
Copy link
Collaborator

@rgcase rgcase left a comment

Choose a reason for hiding this comment

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

LGTM seems very low risk.

Reviewable status: :shipit: complete! 0 of 0 LGTMs obtained (waiting on @dhartunian, @laurenbarker, and @xinhaoz)

Copy link
Collaborator

@dhartunian dhartunian left a comment

Choose a reason for hiding this comment

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

:lgtm:

Reviewable status: :shipit: complete! 1 of 0 LGTMs obtained (waiting on @laurenbarker and @xinhaoz)

@laurenbarker
Copy link
Contributor

TFTRs!

@laurenbarker laurenbarker merged commit aaffaed into release-23.2 Mar 12, 2024
5 of 6 checks passed
@laurenbarker laurenbarker deleted the blathers/backport-release-23.2-120137 branch March 12, 2024 17:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport Label PR's that are backports to older release branches blathers-backport This is a backport that Blathers created automatically. O-robot Originated from a bot.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants