fix(ui): Handle incorrect duration format

[yhwang]

Description

Treat the incorrect duration data as 0 and avoid parsing errors. Meanwhile, also generate an error log in the console to show the wrong value.

Motivation and Context

fixed: #26588

Impact

An incorrect format, like a negative number, is treated as 0.

Test Plan

Verify the UI with negative numbers in the JSON payload

Contributor checklist

• Please make sure your submission complies with our contributing guide, in particular code style and commit standards.
• PR description addresses the issue accurately and concisely. If the change is non-trivial, a GitHub Issue is referenced.
• Documented new properties (with its default value), SQL syntax, functions, or other functionality.
• If release notes are required, they follow the release notes guidelines.
• Adequate tests were added if applicable.
• CI passed.
• If adding new dependencies, verified they have an OpenSSF Scorecard score of 5.0 or higher (or obtained explicit TSC approval for lower scores).

Release Notes

Please follow release notes guidelines and fill in the release notes below.

== NO RELEASE NOTE ==

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

The PR updates parseDuration in utils.ts to treat incorrect or unsupported duration formats as 0 with console error logging and adjusts its return signature to always return a number.

Class diagram for updated parseDuration function

classDiagram
    class utils {
        +parseDuration(value: string): number
    }

Loading

Flow diagram for parseDuration error handling

flowchart TD
    A["Input duration string"] --> B["Match with DURATION_PATTERN"]
    B -- "No match" --> C["Log error: Invalid duration format"]
    C --> D["Return 0"]
    B -- "Match" --> E["Parse number and unit"]
    E -- "Supported unit" --> F["Calculate duration in ms"]
    F --> G["Return calculated value"]
    E -- "Unsupported unit" --> H["Log error: Failed to convert to float"]
    H --> D

Loading

File-Level Changes

Change	Details	Files
Enhanced parseDuration to default invalid inputs to zero with error logging	Changed return type from nullable to always number On regex mismatch, log an error and return 0 instead of null On unsupported unit fallback, log an error and return 0 instead of null	presto-ui/src/utils.ts

Assessment against linked issues

Issue	Objective	Addressed	Explanation
#26588	Fix the UI bug where Query Details page shows blank due to a TypeError when parsing duration values.	✅
#26588	Handle incorrect or malformed duration formats in the UI code to prevent runtime errors.	✅
#26588	Log errors to the console when an incorrect duration format is encountered for easier debugging.	✅

Possibly linked issues

• Presto UI shows blank for Query Details #26588: The PR fixes the UI blank screen by ensuring parseDuration returns 0 for invalid formats, preventing 'toFixed' errors.

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey there - I've reviewed your changes and they look great!

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[yhwang]

Attached the manual verification:

Before the change, if the JSON payload contained invalid durations: negative values, the page would hit the error mentioned in #26588

After the change, the incorrect duration values are treated as 0 now. The page can properly show the statistics.

and error messages show up in the console:

[yhwang]

Minor fix and no functionality change. Thanks to @tdcmeehan 's approval. Let me merge the change.