Missing timestamp validity checks in get_metric_range_dataSee original GitHub issue
To Reproduce Steps to reproduce the behavior:
- Using this object call the
get_metric_range_datafunc with end_time < start_time
- See empty list
If the user were to make this timestamp switcharoo while using the
custom_query_range function, then the HTTP code 400 would returned with the message
end timestamp must not be before start time. So maybe something similar should happen for
get_metric_range_data as well?
- Created 2 years ago
- Comments:12 (11 by maintainers)
Top GitHub Comments
please take it
@sesheta: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity. Reopen the issue with
/reopen. Mark the issue as fresh with
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.