Kafka-based JobQueue doesn't use PHP serialization as there's a general move towards eliminating it from the codebase (T161647), so the TranslationsUpdateJob has to use JSON-serialization and instantiate any classes it was PHP-serializing when executing.
|mediawiki/extensions/Translate : wmf/1.32.0-wmf.2||Refactor TranslationUpdateJob to use only primitive types for parameters|
|mediawiki/extensions/Translate : master||Refactor TranslationUpdateJob to use only primitive types for parameters|
|Resolved||Pchelolo||T157088 [EPIC] Develop a JobQueue backend based on EventBus|
|Resolved||Pchelolo||T190327 FY17/18 Q4 Program 8 Services Goal: Complete the JobQueue transition to EventBus|
|Resolved||Nikerabbit||T192107 Unable to mark pages for translation in Meta|
|Resolved||Nikerabbit||T192111 Make TranslationsUpdateJob JSON-serializable|
Sorry, this slipped my mind yesterday. How important is it to speed this up? My concern is that the patch might not be simple nor low risk (nor easy to confirm) as required for SWAT deployments.
The job is broken on test.wikipedia.org for unrelated reason. On MediaWiki.org I re-marked one page for testing purposes and it worked: https://www.mediawiki.org/w/index.php?title=At-ease/de&diff=2776172&oldid=2595342&diffmode=source (+no errors in LogStash).