Fixed by Paladox with https://gerrit.wikimedia.org/r/c/mediawiki/extensions/Math/+/952438.

This should be exponentially better now. If issues continue, this task will be reopened. We deeply apologise for all the issues that has occurred over the past weeks/months.

Not to mention the numerous slowdowns.

Closing this task per the a above now.

Thanks for the review @Universal_Omega!

Okay, so I did a review on this, as best I could. And to be honest a lot of this extension I understood very little. But due to the fact that severe issues have been proven to occur in the past I am recommending the following:

Will confirm that I randomly got a 503 while saving a change.

When reporting this, please be sure to provide the information below.

@Universal_Omega Seeing as this is high priority and has been open since July 1, do you have any plans to work on it soon?

(-Infra as tasks shouldn’t be dual tagged for responsibility)

@Paladox Universal Omega says that this is unlikely to get better before the Swift migration. Do you have a timeframe in mind for when that would happen?

In T9360#192966, @Funa-enpitu wrote:

The bug is not fixed, so I'm moving it to a new wiki.

Hello, sorry for the delay here. Is the issue still persisting?

Per above:

In T9581#194853, @Theguythatwrites wrote:

Could you open this again? It's obviously not solved yet.

Edit: I opened the task again.

Could you open this again? It's obviously not solved yet.

They will still happen, just less frequently, or at least I would hope they are less frequent.

Just happened to me again:
Error 503 Backend fetch failed, forwarded for 118.208.135.232, 127.0.0.1
(Varnish XID 38998613) via cp30 at Wed, 10 Aug 2022 10:08:57 GMT.

Everything works perfectly now, thanks for fixing!

Bugs and slowdowns are not fixed at all. Impossible to navigate or even do anything.

Yeah, it just happened again despite the completion of the migration. I did receive 502/503s after, but it did not cause an outage that lasted for minutes and prevented me from accessing sites. Right now, I just bumped right into one and could barely navigate the site.

In T9581#194790, @Theguythatwrites wrote:

Still seem to happen to me.

Still seem to happen to me.

The migration is now complete. If 503s once again become quite frequent, this can be reopened. Thank you everyone for your patience with this and once again, we deeply apologise for all the issues over the past days.

40GB left to transfer. Hopefully it will be done soon.

82 Hours Left ****

For me, it doesn't slow down at all. Bugs are still frequent, it's a disaster.

Thank you - I'll update sitenotices the next time the 503s stop.

In T9581#194749, @Robkelk wrote:

We're coming up on the end of this period. Could we have a status report, please?

In T9581#194512, @Universal_Omega wrote:

We deeply apologise for the issues. The time the system gave us was incorrect. It was about 90 hours off by my own estimate, and based on the progress it has already done. There should be about 82 hours left based on how much as already completed.

Again, on behalf of SRE, we truly apologise for all the issues this has caused to the community, and understand the frustration it has also caused.

You guys are not alone, 'cause I keep getting bombarded by those 503s as well...

Still happening here too...
Error 503 Backend fetch failed, forwarded for 118.208.135.232, 127.0.0.1
(Varnish XID 228099867) via cp20 at Mon, 08 Aug 2022 10:36:31 GMT.

Me too, I am still frequently getting 503 errors.

In T9581#194720, @ZeusDeeGoose wrote:

Seems like the 503s are finally starting to let up. I haven't got one this afternoon.

Seems like the 503s are finally starting to let up. I haven't got one this afternoon.

Took me over a minute for an OAuth token to log in here. The wiki is seriously slow, if it works at all.