Sat, Jul 22
Thu, Jul 20
@EBernhardson sounds good to me, better chances of combining Varnish hits with another feature is definitely the most important optimization
Wed, Jul 19
Tue, Jul 18
@MarkTraceur I'm going on vacation for 2 weeks at the end of this week. But before I leave I have time to walk you through how you would go about writing this, and @fgiunchedi can review your Thumbor plugin for STL.
OK, finally found the right command to invoke it:
I think I've found the actual command in mediawiki-config, but xvfb-run is missing:
Thumbor has no support for STL yet, and it can't get it until 3d2png is available. The first step is getting 3d2png to be on the server at all and function properly. I see that the sources are there now:
Yes, I noticed that, it's definitely a great thing that the bulk of the work happens async. There is one caveat to using jobs and I wanted to make sure that your current approach was deliberate.
I use EL occasionally to investigate performance incidents, I would like to retain access.
Mon, Jul 17
Thanks for the reminder, done: https://github.com/grafana/grafana/issues/8874
The Thumbor servers, in this case, but yeah. I guess I can file a task for that...
Doesn't seem to be the source of the problem anyway, after further inspection.
Trying a stretch machine on labs, which runs 2.40.16-1+b1, works fine. And the source for it looks identical to 2.40.16-1+wmf1
These county maps show up disproportionately in the failing thumbnail logs. The issue with them predates Thumbor, because it's a problem at the rsvg-convert level (which is also what Mediawiki uses). They make rsvg-convert segfault:
Thu, Jul 13
@Jeff_G please create a separate task for this issue with more details (which browser, browser version, a screenshot of the error, etc.). It's unrelated to this task.
It's not more severe, it's exactly the same problem. Lack of body applies to all error responses.
Wed, Jul 12
Thumbor doesn't support those yet, you guys have to figure out how to deploy 3d2png properly first. There's a change cherry-picked for it on beta, but it keeps generating errors: T166013: deployment-imagescaler01 has no mwdeploy user and the executable is nowhere in sight.
All good now. Affected files should just start working once they get out of the 429 throttling.
We can and should just depool a server before restarting all its Thumbor instances.
As far as I can tell, it has to do with Varnish or Swift URL-encoding the request, where thumbor expects "seek=4" and gets "seek%3D4". All the existing integration tests are Thumbor only, without Swift or Varnish in front of it.