imo, the problem here is that this error is reported at all. We have 7 retries at each API call - if one of them fails due to some error, we retry. I mean, you need _good_ credentials to post the error on github in the first place :) Which means, whatever the error _was_ - it's not there anymore. And since everything else seems to be working - the error has transient nature and is mitigated by retries. It just doesn't need to be reported and confuse people. Why it occurs in the first place is a different question, and there is a separate bug for that. Anyways, if you would like to see _more_ of the error and debug it - I am not the one to stop you :) Dustin also wanted to see moar info in that error. If this, in your opinion, is the perfect resolution of this bug - I'm fine with that. So, This is [an example of a log entry](https://console.cloud.google.com/logs/viewer?interval=JUMP_TO_TIME&project=moz-fx-taskcluster-prod-4b87&folder&organizationId&minLogLevel=0&expandAll=false×tamp=2020-04-23T02%3A07%3A22.643878295Z&customFacets=jsonPayload.Fields.runningCapacity%2CjsonPayload.Fields.workerPoolId%2CjsonPayload.Fields.duration%2CjsonPayload.Fields.queueName&limitCustomFacetWidth=true&scrollTimestamp=2020-04-23T01%3A50%3A36.343351599Z&advancedFilter=resource.type%3D%22k8s_container%22%0Aresource.labels.project_id%3D%22moz-fx-taskcluster-prod-4b87%22%0Aresource.labels.cluster_name%3D%22taskcluster-firefoxcitc-v1%22%0Aresource.labels.pod_name%3D%22taskcluster-github-worker-6fdd5dcb8b-j44w2%22%0Aresource.labels.container_name%3D%22taskcluster-github%22%0Aresource.labels.namespace_name%3D%22firefoxcitc-taskcluster%22%0Aresource.labels.location%3D%22us-west1%22%0Atimestamp%3D%222020-04-23T01%3A17%3A14.796335451Z%22%0AinsertId%3D%22vvwce4z8mdljai8jl%22&dateRangeStart=2020-04-23T00%3A11%3A42.184Z&dateRangeEnd=2020-04-23T02%3A11%3A42.184Z) - what kind of information do you want to see in that error message, what would be interesting?
Bug 1631099 Comment 7 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
imo, the problem here is that this error is reported at all. We have 7 retries at each API call - if one of them fails due to some error, we retry. I mean, you need _good_ credentials to post the error on github in the first place :) Which means, whatever the error _was_ - it's not there anymore. And since everything else seems to be working - the error has transient nature and is mitigated by retries. It just doesn't need to be reported and confuse people. Why it occurs in the first place is a different question, and there is a separate bug for that. Anyways, if you would like to see _more_ of the error and debug it - I am not the one to stop you :) Dustin also wanted to see moar info in that error. If this, in your opinion, is the perfect resolution of this bug - I'm fine with that. So, This is [an example of a log entry](https://console.cloud.google.com/logs/viewer?interval=JUMP_TO_TIME&project=moz-fx-taskcluster-prod-4b87&folder&organizationId&minLogLevel=0&expandAll=false×tamp=2020-04-23T02%3A07%3A22.643878295Z&customFacets=jsonPayload.Fields.runningCapacity%2CjsonPayload.Fields.workerPoolId%2CjsonPayload.Fields.duration%2CjsonPayload.Fields.queueName&limitCustomFacetWidth=true&scrollTimestamp=2020-04-23T01%3A50%3A36.343351599Z&advancedFilter=resource.type%3D%22k8s_container%22%0Aresource.labels.project_id%3D%22moz-fx-taskcluster-prod-4b87%22%0Aresource.labels.cluster_name%3D%22taskcluster-firefoxcitc-v1%22%0Aresource.labels.pod_name%3D%22taskcluster-github-worker-6fdd5dcb8b-j44w2%22%0Aresource.labels.container_name%3D%22taskcluster-github%22%0Aresource.labels.namespace_name%3D%22firefoxcitc-taskcluster%22%0Aresource.labels.location%3D%22us-west1%22%0Atimestamp%3D%222020-04-23T01%3A17%3A14.796335451Z%22%0AinsertId%3D%22vvwce4z8mdljai8jl%22&dateRangeStart=2020-04-23T00%3A11%3A42.184Z&dateRangeEnd=2020-04-23T02%3A11%3A42.184Z) - that's the information we have access to and can put into that message. What kind of information do you want to see in that error message, what would be interesting?