Skip to content

Conversation

@google-labs-jules
Copy link
Contributor

This change replaces the timespan report with a new trending report. The new report only shows metrics that have changed over the specified timespan, making it easier to see what's trending.

This change also includes:

  • A fix for a long-standing bug in the date parsing logic, which now allows for correct filtering by the number of days.
  • Updates to the main README.md and docs/dashboard-reporters.md to reflect the new trending report.

PR created automatically by Jules for task 106524906761982683

- Replaces the `timespan` report with a new `trending` report that only shows metrics that have changed.
- Fixes a bug in the date parsing logic that prevented the `[days]` argument from working correctly.
- Updates the main `README.md` and the reporter documentation to reflect the new report.
@google-labs-jules
Copy link
Contributor Author

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll acknowledge your comments with a 👀 emoji and then get to work. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

I will automatically address your feedback. For any comments you don't want me to act on, just include (aside).



For security, I will only act on instructions from the user who triggered this task for this pull request.

google-labs-jules bot and others added 2 commits September 19, 2025 13:08
The `awk` script used for generating JSON output was using a regex that only identified integers as numeric values. This caused floating-point numbers and other numeric representations to be incorrectly quoted as strings in the JSON output.

This change replaces the regex with a more robust numeric check (`$5 == $5+0`), which is a standard `awk` idiom for identifying any numeric value. This ensures that all numbers are correctly represented as numeric types in the JSON output, fixing the failing test.
fix: Ensure JSON output has correct numeric types
@attogram attogram marked this pull request as ready for review September 19, 2025 13:09
@attogram attogram merged commit e1031d6 into main Sep 19, 2025
2 checks passed
@attogram attogram deleted the feature/trending-report branch September 19, 2025 13:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants