| Jdforrester-WMF | |
| Aug 30 2023, 6:53 PM |
[Spun out from T344747.]
The currently-deployed version of Mathoid is from February. Someone (who?) should update us to the latest, ahead of changing the hosting / base image generating system from gerrit to GitLab.
Questions:
Who should do this as a one-off?
@akosiaris is the only person I am aware of who has experience in doing it.
Is there a runbook for doing this?
https://wikitech.wikimedia.org/wiki/Mathoid
I guess it is pretty much up to date. However as we are changing the node version I am unsure if additional steps are required. As this is on the container level the node version should not matter, but you never know.
How do we know if it worked or if it broke things?
We can render a *new* equation on Restbase or send requests as described in the readme.
Who should own doing this more regularly?
I don't know. However, there are only fixes "planned" for mathoid.
If there's no-one else, I'm happy to do the one-off and help with on-going deploys if needed. I'll see if I can get us to current this next week.
I think that the subject is misleading. Per https://gerrit.wikimedia.org/r/plugins/gitiles/operations/deployment-charts/+/33520a1a4409a9b0cef71a0b4baba148f64f2d40 (gerrit change is https://gerrit.wikimedia.org/r/c/operations/deployment-charts/+/809194) deployed mathoid version isn't 2023-02-21 but 2022-06-28-144716-production (which is even older).
Mentioned in SAL (#wikimedia-operations) [2023-09-04T09:49:00Z] <akosiaris> T345290. Update mathoid to 2023-05-13-192519-production
I 've merged and deployed the change mentioned in T344747, alongside the dependent changes. curl call listed in the Mathoid page returns succesfully an SVG, and openapi checks are apparently also fine. I 'll resolve this one but I 'll note that for
Who should own doing this more regularly?
I 've tried and did manage to find an owner in the past, but we are back to square 1 regarding this. I just hope that the plans to fully migrate math rendering in the browser will materialize and we 'll be able to undeploy this service at some point.
It will take a while. While we will be ready for opt-in very soon (maybe even this month), it will be a long way to fix all issues. To convince people that a browser is not TeX engine, will be even harder and to advocate for the advantages of inherent math display will take some time as well.
Understood. Fingers crossed it will go more smoothly that anticipated! And my thanks for pushing this forward.