FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

Round fields in TRAP caching telemetry to integers by edoardopirovano · Pull Request #1188 · github/codeql-action · GitHub

Round fields in TRAP caching telemetry to integers - #1188

Merged
edoardopirovano merged 1 commit into
mainfrom
edoardo/round-fields
Aug 17, 2022
Merged

edoardopirovano merged 1 commit into
mainfrom
edoardo/round-fields

Conversation

edoardopirovano commented Aug 17, 2022
edited
Loading

Copy link
Copy Markdown
Contributor

The status reporting API expects these to be integers.

Merge / deployment checklist

  • Confirm this change is backwards compatible with existing workflows.
  • Confirm the readme has been updated if necessary.
  • Confirm the changelog has been updated if necessary.

edoardopirovano requested a review from a team as a code owner August 17, 2022 12:31

henrymercer left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

I think keeping them as ints makes sense since it's consistent with the other duration metrics like analyze_builtin_queries_cpp_duration_ms.

Comment thread src/analyze-action.ts
config.trapCaches,
logger
trap_cache_upload_duration_ms: Math.round(trapCacheUploadTime || 0),
trap_cache_upload_size_bytes: Math.round(

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

You could optionally push the rounding in here, if you'll only need the rounded values.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

Hmm, yes, I considered doing that but decided that rounding at the point where we construct the status report was the safest way to make sure we only send an integer to the API. Let's leave it like this for now to unbreak things, and we can always shuffle this around at some other point.

This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
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.

3 participants


Back | FazBrowse Home | New Git URL