Looks right to me.

Awesome, looking forwarding to seeing the that.

I've just deployed the fixes:

• https://github.com/WikiEducationFoundation/WikiEduDashboard/pull/7060
• https://github.com/WikiEducationFoundation/WikiEduDashboard/pull/7056

Thanks! For this one, I don't have proof of what went wrong, but it doesn't seem to be the same problem as the one discussed above. It's likely a race condition bug on the Dashboard side, where another change to that course clobbered the event sync flag right after it got set. I'm going to make it robust against that on the Dashboard side.

Do you have the Dashboard event page for which this happened? I did some investigation with Claude, and at least one of the problems was because a course was deleted on the Dashboard and then recreated with the same name shortly afterwards. Details from the Claude Code investigation:

In T436984#12300618, @LGoto wrote:

On a side note: this is minor, but could you please edit the "AI tool usage policy" so that the links are clickable? It's important that applicants review this information, so we'd like to make it easily accessible. Thanks!

In T436984#12299721, @LGoto wrote:

@Ragesoss thank you for submitting your proposal to the Outreachy site! Could you please add Brianda as a mentor for the project?

I copied this description of the checks we implemented from our IRB form below. The source code for our userscript is currently in a private repo, but I'm checking in with the research team to see if there's any reason not to make that public. (The actual userscript is https://en.wikipedia.org/wiki/User:Sage_(Wiki_Ed)/wickie.js but it's AI-coded and not easy to make sense of directly.)

Excellent, thanks for letting me know about this!

@LGoto confirmed! Brianda is no longer provisional.

Yes, working on confirming second mentor.

Great, thanks! If there details about those remaining edge cases on Phabricator, I'd love to follow along.

When are we expecting to roll out to en.wiki? Wiki Education is trying to strongly encourage page numbers in citations, and we're trying to figure out whether it's worth it to update our training modules to explain how to use the {{rp}} template for the Fall 2026 semester that is starting soon, or whether we should just wait for this to deploy and build our new instructions around it.

I think an easy way to get from the dashboard to the linked Event page would be very helpful, especially since it would make it more obvious when a course is linked. @Formasit-chijoh: please file a GitHub issue for that.

I agree, we shouldn't regenerate the pickles.

I'm looking at the examples from the Meta talk page as well, and did find one regression that was introduced by the recent algorithm changes, but I think it should be practical to fix it. (The bug is that in internal link with a namespace prefix, like File:, breaks highlighting, so anything after that link doesn't get any highlighting data.)

A few things... this particular example had its pickle generated in March, so it was serving data based on the old algorithm.

@MusikAnimal i'll see if i can debug it.

Added.

It means previous week. I will add a qqq entry to clarify.

In T432147#12148263, @jsn.sherman wrote:

Okay, we're back up and running; expect things to be shaky as the box warms up and tries to handle requests. @Ragesoss can you check your dashboard?

We're seeing CORS errors today on Wiki Education Dashboard, like this:

Moving to gitlab makes sense to me @jsn.sherman . I'm not aware of how it would use elasticsearch. The codebase we inherited had a lot of features that don't need for the applications we support with it, and that might be one of them.

I believe this already fixed, just not yet deployed, from:

@Tgr thanks! I haven't heard any reports of this happening in recent years.

Confirming, I have access and I see the others on the list. Thanks @Volans !

@Volans they will not be; we want a separate project so that @JGonzalez_EdWH can be an admin of the new one, without access to the production instances.

Yep! https://www.wikifunctions.org/wiki/Z36261?uselang=en&oldid=282025

I'd love to see this get taken care of soon. There's a Programs & Events Dashboard program that's trying to track uwikisource, and it won't be able to pull any revision data until Replica can connected to to it. (Incidentally, this led to flooding the Dashboard's logging system, as we hadn't had to deal with an existing wiki with replica connection errors before.)

In T423788#11839220, @Geertivp wrote:

It seems that the original error still appears when the user does not have an active Wikimedia session.

Fixed and deployed with https://github.com/WikiEducationFoundation/WikiEduDashboard/commit/76edcd4c408552d45d17974d83ed3a21668c8b4e

I prototyped something similar today (vibe coded), and took some ideas from yours: https://ragesoss.github.io/zblocks/

In T423781#11835994, @GrounderUK wrote:

I think this duplicates T419561 or, at least, it’s a subset.

Abstract Wikipedia team: I've tried to get everything in as near-complete shape as I could all at once, and do all the things I could think to do to make it usable, but I don't know whether all this AI code and description is worth your time. If it's not, please just close this and accept my apologies for the Phab and GitLab noise. I'm trying to scratch my own itch for what I want to do on Wikifunctions, and thought I'd give it a shot, since Claude did well enough with https://www.wikifunctions.org/wiki/Talk:Z16684

In T307878#11709728, @TheDJ wrote:

This makes sense. Thanks for the clear description! I've added an issue on the Dashboard's GitHub repo.

@LGoto I know that I missed the February 25 deadline, but I hope you can make an exception. I mistakenly thought the deadline was the Outreachy one (March 7). I've already posted this project on outreachy.org.

@LGoto done!

In T407660#11556351, @HMonroy wrote:

Hi @Ragesoss ! Is this something you are looking into? We are wondering if Community-Tech should take a look. Thank you for your help in advance :)

The vast majority of the storage is on the two mounted volumes, so I think a command like that would be hard to get useful info from unless it's scoped to /dev/sda1.

See also https://phabricator.wikimedia.org/T415603

@Joe checking my Sentry logs, I see we're still getting 429 for some types of queries, including Commons API queries and fetching page content (but not the OAuth login flow). Are there requests we're still making that don't meet the UA policy requirement? (We have several different libraries involved for requests, and I think I addressed these ones, which go through the mediawiki_api Ruby gem, but it's possible that I missed something.)

I did a quick simple intervention today, deleting a portion of the pickles that hadn't been accessed in 90 days or more. Any that get requested will be regenerated, so it should only cause some minor inconvenience when the data isn't available on first request. (I ran a simple script that was looping through the en directory, and deleting each file if its atime was earlier than 90 days ago. I was disconnected with a broken pipe before it finished, so I don't know how much more it would have deleted it it ran to completion.)

@ssingh I've just deployed an update that should fix it. Now the user agent is Wiki Education Dashboard/1.0 (dashboard.wikiedu.org; sage@wikiedu.org).

Thanks! Unfortunately, the OAuth library we use doesn't support setting the User Agent, so I'm going to have to figure out how to monkey patch it. :-(

Day 5: 2025-12-08

In T411890#11438103, @Cookroach wrote:

Thanks you very much Ragesoss for your restoration work. Which data records or which time period have actually been lost and cannot be restored? Background: We have a challenge that started on December 1. best regards

Day 2: 2025-12-05

Day 1: 2025-12-04

Excellent, thanks for creating the GitHub issue.

Sounds like a good idea. I've created an issue for it.

It's worth noting that we could enable additional languages without an initial processing run; in that case, every new request would trigger processing that particular article (and result in slower, but still usable, performance for the first request for each article for Who Wrote That and Dashboard end users). I think that strategy would be fine for enabling all additional languages; the only blocker would be making sure we have appropriate storage for handling the gradual accumulation of processed articles files for the additional languages (and clearing some headway for continued growth of storage requirements for the already-enabled ones).

@ccasilli @LGoto we're getting close to the deadline here; the community signup deadline is less than 24 hours away (September 17 at 4pm UTC) and the mentor project listing deadline is September 27.

When will we start listing projects?

I think I have a good guess at what happened, a race condition of sorts.

In T401873#11095223, @Daimona wrote:

@Ragesoss Hi! This course was associated to this event on-wiki on July 28th. However, it looks like it is no longer linked. This did not happen on our side AFAICT. Do you have an idea of how it might have happened, and if it could be prevented going forwards? Thanks!

Here's a nice visualization of the progress we made on performance problems since the start of the internship, in the form of the downtime monitor for Programs & Events Dashboard.

Thanks! I was unable to implement this last week, as I was travelling.

When does your edit-a-thon start?

Yes, that one seems like the same thing to me.

@Seb35 it seems closely related, but not quite the same. T280078 is about parameters that should be allowed to be empty without automatically getting removed, and this one is about preventing the addition of undocumented (and non-functional) parameters.

Thanks! I just processed the backlog of account requests on Programs & Events Dashboard, and things are working normally again.

Any update on this? We still have account requests coming in regularly on Programs & Events Dashboard for editathons and such, and can't process them.

Wiki Education continues to get reports of this error from new student editors. This is the most common error we hear about from users lately.

@Ladsgroup thanks! Do you have any more details about the ones still happening, like an example request?

@MusikAnimal thanks! I just pulled in the change and restarted all the services, so it should be live now.

I've implemented a fix here: https://github.com/wikimedia/wikiwho_api/pull/20/files