ORES passes around a lot of context for a score job. Implement a ScoreResponse and ScoreRequest object to manage this information and a few utility functions to build the objects. This will be a big refactoring that will make work like T159502 easier.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Halfak | T162892 Deploy ORES mid-April | |||
| Resolved | Halfak | T159502 Exclude precaching requests from cache_miss/cache_hit metrics | |||
| Resolved | Halfak | T161526 Implement ScoreRequest/ScoreResponse pattern in ORES |
Event Timeline
Comment Actions
Here are some notes about what's going on here: https://etherpad.wikimedia.org/p/ores_request_response_refactor