You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We decide to add some conditional checks in report_metrics() to ensure it works as expected when encounting some tricky corner case and enhance its robustness.
Why is this needed?
In the AutoML and Training WG Community Call, @tenzen-y asked what would happen if we pushed the same metrics twice in a single container. However, the current version of the report_metrics() API does not process this corner case.
Thus, we decided to raise an issue discussing the possible corner case that report_metrics() might meet with. Everyone is welcome to put your valuable insights and suggestions here!
Love this feature?
Give it a 👍 We prioritize the features with most 👍
The text was updated successfully, but these errors were encountered:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
If we pass two same keys in metrics: the latter one will overwrite the former one.
If we call report_metrics() twice and report the same metrics: they won't interfere with each other since they have different timestamp and GetObservationLog will retrieve both of them to the return value.
What you would like to be added?
We decide to add some conditional checks in
report_metrics()
to ensure it works as expected when encounting some tricky corner case and enhance its robustness.Why is this needed?
In the AutoML and Training WG Community Call, @tenzen-y asked what would happen if we pushed the same metrics twice in a single container. However, the current version of the
report_metrics()
API does not process this corner case.Thus, we decided to raise an issue discussing the possible corner case that
report_metrics()
might meet with. Everyone is welcome to put your valuable insights and suggestions here!Love this feature?
Give it a 👍 We prioritize the features with most 👍
The text was updated successfully, but these errors were encountered: