Import now in progress. Really sorry for the massive delay.

I hope ASAP. @Universal_Omega will need to make some changes to the script before we're able to resume them.

Since as mentioned above, it now Discards the majority of spam email, this is less-necessary. Therefore, closing as resolved. If you still want to go the other route as well, please do reopen it.

Unfortunately this isn't possible as Miraheze isn't able to provide services effectively to as many wikis as we have if we didn't compress DBs. We are hoping to eventually have ElasticSearch/CirrusSearch once some version issues are sorted out. Sorry for the inconvenience.

Fixed

Fixed by running

CREATE TABLE /*_*/linktarget (
  lt_id BIGINT UNSIGNED AUTO_INCREMENT NOT NULL,
  lt_namespace INT NOT NULL,
  lt_title VARBINARY(255) NOT NULL,
  UNIQUE INDEX lt_namespace_title (lt_namespace, lt_title),
  PRIMARY KEY(lt_id)
) /*$wgDBTableOptions*/;

and then https://github.com/wikimedia/mediawiki/blob/REL1_39/maintenance/archives/patch-templatelinks-target_id.sql . Thanks to @Universal_Omega

Everything is now done for this.

I switched it to the master branch and updated it.

Fixed.

Fixed.

The availability was likely caused by cloud14 being down at one point and therefore so was mwtask141 and mw141/mw142 jobrunners. The issue with availability does not seem present so far in the past 30 days now.

This was originally due to the cloud14 outage, as every wiki hitting the down wikis returned a 500 status code. This was outside of our control.

PR got merged, only thing missing now is to add the copyToClipboard class to any elements whose text should be copied when clicked.

Reopening this, because at the time the MH skin version was downloaded, Wikimedia folks had renamed the skin folder, unknowingly causing several embedded skin assets to give 404s, which was reported and remedied here:

You can mark it as fixed, it fixed itself

Not a bug, and the TOC is also on the sidebar in Wikipedia (https://en.wikipedia.org/wiki/Gilman_Square_station), though you may see some Wikipedia articles in the Vector-2011 skin because of caching.

I'll open a task upstream about ProtectSite and see if I can find the issue with it also.

It never had anything to do with ProtectSite but another issue with templatelinks and cascading protection. The ProtectSite issue is something else in that case, but I fixed the original issue now.

Still an issue. See here: https://worsttvnetworks.miraheze.org/w/index.php?title=Boomerang_(2015-present)&curid=51&diff=2213&oldid=2069

In T10327#208325, @Void wrote:

Any chance it could be the same problem as T10338? Some of those links look a bit weird for me for this to just be a simple mistake.

Any chance it could be the same problem as T10338? Some of those links look a bit weird for me for this to just be a simple mistake.

In T10219#208245, @John wrote:

https://grafana.miraheze.org/d/pfjAbhf7k/mediawiki-slos?orgId=1&from=now-3h&to=now&viewPanel=22 now shows no data.

This needs to be resolved before the next round of reporting on Jan 31st.

I temporarily disabled Lingo, which fixed it.

oops... my wiki wasnt linked so https://wawaforthewin.miraheze.org/wiki/Wawapedia

Should be fixed. Let me know if you encounter more issues. Thanks!

For the record, Tech:Incidents looks good to me.

Per what @Ugochimobi says, this is very likely not to be a "bug" but simply an error with the way you transcluded things. If you need help fixing it please see:
IRC: #miraheze (recommended)
Discord: https://miraheze.org/discord
On-Wiki: Community noticeboard (questions/discussions)

Can't reproduce, resolving as likely transient error. If that's not the case feel free to reopen and link us to a page where this happens./

Ok will do, thanks.

Then you should do it on ManageWiki.

I just found that there is a setting in ManageWiki for this:

https://github.com/miraheze/mw-config/pull/5082

Would this be different if access only concerned GitHub and only allowed ssl-admins to run puppet and nothing else on ns* (via salt).

@Universal_Omega This could be related to T10335.

[529fbc593ac05bfdf182a866] 2023-01-22 12:52:59: Fatal exception of type "LogicException"

Boldly going to mark as declined due to concerns raised above.

The script is at https://s1.hdslb.com/bfs/seed/log/report/log-reporter.js, it is included on every page at the main website.

https://grafana.miraheze.org/d/pfjAbhf7k/mediawiki-slos?orgId=1&from=now-3h&to=now&viewPanel=22 now shows no data.

By the way, I'm trying to contact the Bilibili technology team through their official account on Bilibili itself and invite them to join our discussion here. Here are my current messages:

• Hello, I'd like to know information about the data collection of Bilibili's external embedded HTML5 player(player.bilibili.com).
• Here's the background. I'm hosting a wiki on Miraheze, and I really want to embed Bilibili's HTML5 player in it. However, Miraheze has strict rules on data security and requires all external contents in wiki pages must comply with GDPR strictly, so they can add them to the CSP whitelist. Previously we tried to request adding bilibili.com to the whitelist, but was finally declined due to lots of uncertainty and the source code leaking affair. Now we are trying to request adding only player.bilibili.com to the whitelist because we find that it's simpler and sets fewer cookies. Now Miraheze needs to confirm whether the HTML5 player strictly complies with GDPR or an equivalence policy and whether the player's script contains fingerprint tracking stuff, so I hope I can know about it.
• Our discussion about this issue is public, so if you don't want to tell me something about it, you can visit our discussion page and reply to it. Here's the link: https://phabricator.miraheze.org/T9953
• Really hope for your early reply!

@OrangeStar Could you please show me which script includes the fingerprint tracking method, and where it is? I tried beautifying the Javascript from player.bilibili.com and searching "fingerprint" in it, but nothing was found.
I doubt you are visiting www.bilibili.com instead of player.bilibili.com. The whole bilibili website is too huge, contains lots of complex stuff, and is definitely hard for Miraheze T&S Team, so we narrowed it down to player.bilibili.com - only the embedded player itself.

The content should be restored shortly, though due to newer backups it will be necessary for us to download it which will take time.

And also I cannot access this wiki at all, although I'm its creator.

The message is pretty self-explanatory, are you sure the page isn't transcluded on a page that has cascade protection enabled?

Now ProtectSite doesn't work again

Can you please check if it is fixed now? Thanks!