Issue metadata
Sign in to add a comment
|
Innocuous error pollutes CrOS infra logs |
||||||||||||||||||||||
Issue description
I see a lot of:
"05:40:41: WARNING: HttpsMonitor.send received status 400: {
"error": {
"code": 400,
"message": "Operation was attempted past the valid range.",
"status": "OUT_OF_RANGE"
}
}"
errors on almost every CrOS infra log. Is it necessary to show those errors? It makes it harder to focus on what actually went wrong.
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by pho...@chromium.org
, Jul 17 2017Status: Duplicate (was: Untriaged)