- Our logs get clogged with unhandled json errors such as wikilambda_fetch threw a fetching error: invalid json response body at http://localhost:6501/w/api.php?action=wikilambda_fetch&format=json&uselang=content&zids=Z27244 reason: Unexpected token 'u', "upstream c"... is not valid JSON. We can add error-handling for this type of error and reduce the log severity.
- We also get a lot of noise on 'error's such as: TypeError: Cannot read properties of undefined (reading 'Z6091K1'). We can also reduce the severity on this so we don't have weed through these logs every day.
- Lower severity on Skipping setting page property for label in unknown language... warnings in WikiLambda
Description
Details
| Title | Reference | Author | Source Branch | Dest Branch | |
|---|---|---|---|---|---|
| handle json fetch errors and demote those logs | repos/abstract-wiki/wikifunctions/function-orchestrator!459 | ecarg | grace/T403993/handle-json-fetch-errors | main |
Related Objects
Event Timeline
We can add error-handling for this type of error and reduce the log severity.
We already have error handling here; I agree we should reduce the log severity.
We also get a lot of noise on 'error's such as: TypeError: Cannot read properties of undefined (reading 'Z6091K1'). We can also reduce the severity on this so we don't have weed through these logs every day.
Do we understand why these are happening? Maybe this task should be about that?
Lower severity on Skipping setting page property for label in unknown language... warnings in WikiLambda
That's not relevant to this task, and it's already covered in T402670.
ecarg opened https://gitlab.wikimedia.org/repos/abstract-wiki/wikifunctions/function-orchestrator/-/merge_requests/459
Draft: handle json fetch errors and demote some logs
ecarg closed https://gitlab.wikimedia.org/repos/abstract-wiki/wikifunctions/function-orchestrator/-/merge_requests/459
handle json fetch errors and demote those logs