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-25.1: ui: fix statement diag reports when min exec latency is null #139587

Merged
merged 1 commit into from
Jan 23, 2025

Conversation

blathers-crl[bot]
Copy link

@blathers-crl blathers-crl bot commented Jan 22, 2025

Backport 1/1 commits from #139342 on behalf of @kyle-a-wong.

/cc @cockroachdb/release


A bug in db console was resulting in statement diagnostics reports to not work as intended. As a result, activating diagnostics didn't result in the intended state change which showed a user that a diagnostics report is running or downloadble.

This was happening in edge cases where reports "minExecutionLatency" response field was null, but the db console expected it to be populated. Now, db console should handle this edge case.

Fixes: #139340
Epic: none
Release note (bug fix): Fixes a bug where sometimes activating diagnostics for sql activity appears unresponsive, with no state or status update upon activating. Now, the status should always reflect that diagnosticsa are active or that a statement bundle is downloadable.


Release justification:

A bug in db console was resulting in statement diagnostics
reports to not work as intended. As a result, activating
diagnostics didn't result in the intended state change which
showed a user that a diagnostics report is running or downloadble.

This was happening in edge cases where reports "minExecutionLatency"
response field was null, but the db console expected it to be populated.
Now, db console should handle this edge case.

This commit also adds nanosecond granularity to the returned
StatementDiagnosticsResponse.min_execution_latency field. Previously only
the seconds portion of the statement's min_execution_latency was
converted into the returned objects duration, but often times this
latency will be sub 1 second, resulting in "O" to be returned.

Fixes: #139340
Epic: none
Release note (bug fix): Fixes a bug where sometimes activating
diagnostics for sql activity appears unresponsive, with no
state or status update upon activating. Now, the status should
always reflect that diagnosticsa are active or that a statement
bundle is downloadable.
@blathers-crl blathers-crl bot requested a review from a team as a code owner January 22, 2025 19:16
@blathers-crl blathers-crl bot force-pushed the blathers/backport-release-25.1-139342 branch from 60417cf to bfb75cc Compare January 22, 2025 19:16
@blathers-crl blathers-crl bot requested review from xinhaoz and removed request for a team January 22, 2025 19:16
@blathers-crl blathers-crl bot added blathers-backport This is a backport that Blathers created automatically. O-robot Originated from a bot. labels Jan 22, 2025
Copy link
Author

blathers-crl bot commented Jan 22, 2025

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. 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 Jan 22, 2025
@cockroach-teamcity
Copy link
Member

This change is Reviewable

@kyle-a-wong kyle-a-wong merged commit ad44f93 into release-25.1 Jan 23, 2025
18 of 20 checks passed
@kyle-a-wong kyle-a-wong deleted the blathers/backport-release-25.1-139342 branch January 23, 2025 14:41
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.

3 participants