-
Notifications
You must be signed in to change notification settings - Fork 27
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
Bug 1694770 - Implement the timespan metric type #253
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good overall, there's a few nits and a CHANGELOG entry should be added as well. Does the glean_parser already produce valid code to use this?
Yes, we were only missing labeled. Unless we introduce a metric type that the Glean SDK does not also support, we are good. |
b689d9e
to
4dbef01
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
r+
* No error is recorded if no `start()` was called. | ||
*/ | ||
cancel(): void { | ||
Context.dispatcher.launch(() => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why wasn't this failing our tests? did you end up finding out?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Dispatched or not, start and cancel when called in sequence seem to run one after the other. Probably because neither have any actual await
inside. I tried to make the tests fail, but they never did.
Only when I launch some setTimeout's in between calling them do they fail, but I did not commit such a test because I thought it would be confusing.
No description provided.