Translation endpoint fails intermittently with:
/{domain}/v1/article/creation/translation/{source}{/seed} (article.creation.translation - normal source and target) is CRITICAL: Test article.creation.translation - normal source and target returned the unexpected status 404 (expecting: 200)
Further investigation revealed that it's caused by an error in MW API we started hitting
{"error":{"code":"internal_api_error_BadMethodCallException","info":"[XFjJ5wpAIDYAAFo57poAAACF] Caught exception of type BadMethodCallException","errorclass":"BadMethodCallException"},"servedby":"mw1342"}
Example log on MW side can be found here.
It appears to be a bug on multiple levels - mostviewed API in MW should not crumble like this, Recommendation-API should probably report situations like that as an internal server error (500) instead of a 404, even though the alert was seen in icinga, it didn't go to any mailing lists or IRC channels AFAIK.
Mentors
- @bmansurov (IRC channel: Research)
Skills Required
- Javascript
Acceptance Criteria
- Find out what's causing the problem and fix it. The codebase is here. The bug is most likely in lib/article.creation.translation.js or routes/article.creation.translation.js.