User Talk: Redalert2fan

Server-side rendered snapshot of this editor's Wikipedia talk page discussions.

{{User:MiszaBot/config
|archiveheader = {{talk archive navigation}}
|maxarchivesize = 75K
|counter = 30
|minthreadsleft = 2
|minthreadstoarchive = 1
|algo = old(90d)
|archive = User talk:Redalert2fan/Archive %(counter)d
}}

{{User:Redalert2fan/header}}
{{talkheader}}
{{YesAutosign}}

A barnstar for you!

{| style="background-color: var(--background-color-success-subtle, #fdffe7); border: 1px solid var(--border-color-success, #fceb92); color: var(--color-base, #202122);"
|rowspan="2" style="vertical-align: middle; padding: 5px;" | 100px ↗
|style="font-size: x-large; padding: 3px 3px 0 3px; height: 1.5em;" | '''The Technical Barnstar'''
|-
|style="vertical-align: middle; padding: 3px;" | Very nice job getting {{noping|Citation bot}} fixed and unblocked, and all the other little bug fixes. Hard to believe a bot with 6 million edits was blocked for 2 months, since this bot is one of the most used bots in wiki history. Your efforts fixed it. Bravo. –'''Novem Linguae''' (talk) 23:23, 30 March 2026 (UTC)
|}

:Thanks! When I started to help out a couple of months ago my knowledge of coding was pretty much limited to changing variables, perhaps using a command line. With some help from AI, I've managed to come this far since then. Atleast I can read what PHP code means now, the code suggestions from me probably aren't the cleanest but they got the job done. Don't have the skills yet to actually maintain a bot, but happy to help out.
:Perhaps one day somebody with actual good knowledge of PHP can clean the code up, I still find it hard to believe that there was not a single other person attempting to fix the bot though. Redalert2fan (talk) 14:14, 31 March 2026 (UTC)
::I was keeping an eye on it and would have tried to tackle that eventually if needed. I'm glad you got to it first though!
::Sometimes AI patches are terrible, but the final one you submitted seemed nice and concise.
::You and I are both lucky that AManWithNoPlan reviews pretty much everything in 24 hours. Most projects do not review that fast.
::The flaky tests on that repo drive me nuts. A red X should always mean "this PR breaks something". Right now a red X means "who knows" and everyone just ignores it, which makes the thousands of tests a lot less useful. –'''Novem Linguae''' (talk) 21:22, 31 March 2026 (UTC)
:::Just happen to be working on the tests right now! fixed a couple that failed each time in the last 20 PR's. Right now its a mix of: The external API changed, or we suddenly get a different response from before. In those cases I would consider the red X sort of correct; the code is fine but the test itself if now broken. But the most common cause for fails is an API time out, which shouldn't be giving us the red X so to say, since the code is working fine.
:::Probably happens because we either don't have API keys set because they were never obtained and also because we use the same API keys for production and testing... Redalert2fan (talk) 21:37, 31 March 2026 (UTC)
::::Thanks for working on it! In my opinion this is so important that I would just ->skip() every test that ever fails until master branch is back to green. But I submitted some PRs to do that and they were declined.
::::There is also a lot of committing directly to master going on, instead of using PRs, which runs the test suite AFTER merging to master, which means untested/bad code can get merged to master. Then any PR based on that commit or newer commits also fails.
::::I think there is also a lot of aborting the test suite before it runs fully going on, in order to not use up so many of our free credits per month.
::::Overall testing in this repo is frustrating and doesn't provide a great developer experience. –'''Novem Linguae''' (talk) 22:31, 31 March 2026 (UTC)
:::::We got some seperate API keys for the test suite now, and I implemented skips for the worst offenders. First time we got a green check mark in a while. It's possible there are some more test candidates that need skips which I will add if the red x comes back. I think after a couple more different pulls to see said candidates we should no longer get them. Redalert2fan (talk) 16:34, 4 April 2026 (UTC)
::::::Status update: We are now up to intermittently getting green check marks. Redalert2fan (talk) 22:52, 28 April 2026 (UTC)
:::::::Yay. Progress is good. Would still be best to fix all the flakiness though. –'''Novem Linguae''' (talk) 23:14, 28 April 2026 (UTC)

New pages patrol May 2026 Backlog drive

{| style="border: 2px solid #36c; border-radius: 4px; background: linear-gradient(to right, #ffffff, #eaf3ff); padding: 10px; color: #000;"
| style="vertical-align: middle; font-size: 130%" | May 2026 Backlog Drive ↗ | '''New pages patrol ↗''' 
| rowspan=3 | right|100px ↗
|-
|

On 1 May 2026, a one-month backlog drive for New Page Patrol will begin.

Barnstars will be awarded based on the number of articles patrolled.

Barnstars will also be granted for re-reviewing articles previously reviewed by other patrollers during the drive.

Each review will earn 1 point.

Interested in taking part? '''Sign up here ↗'''.

|-
|colspan=2 style="font-size:85%; padding-top:15px;"|You're receiving this message because you are a new page patroller. To opt-out of future mailings, please remove yourself here. ↗
|}
MediaWiki message delivery (talk) 11:24, 29 April 2026 (UTC)

New Page Patrol Newsletter - May 2026

<div style="border:2px solid #90C0FF; background:#F0F0FF; width:99%; padding:4px">

Hello {{BASEPAGENAME}},

thumb|400px|New Page Review queue November 2025 - May 2026 ↗

'''Backlog update'''

At the time of this message, there are 15,282 articles and 32,951 redirects awaiting review.

After the January–February drive the article backlog was reduced to 15,179 articles and the redirect backlog to 19,053 respectively. Great job! However, both queues are growing rapidly and any additional reviews are highly appreciated.

'''2024 and 2025 NPP Awards'''

74px|left ↗{{no ping|JTtheOG}} was selected as the NPP reviewer of the year for both 2024 and 2025, for reviewing the most articles amongst all reviewers.
{{no ping|Hey man im josh}} and {{no ping|MPGuy2824}} won the Redirect Ninja Master Award for 2024 and 2025 respectively, for reviewing the most redirects.

Overall in 2024, one Platinum, two Gold, eight Silver, 12 Bronze and 45 Iron Barnstars were awarded. Additionally, 66 reviewers got the NPP barnstar for doing more than 100 reviews through the year. In 2025, one Platinum, ten Silver, 13 Bronze and 38 Iron Barnstars were awarded. Additionally, 38 reviewers got the NPP barnstar for doing more than 100 reviews through the year.

{{no ping|BoyTheKingCanDance}}, {{no ping|Rosiestep}}, {{no ping|SunDawn}}, and {{no ping|Vanderwaalforces}} were inducted into the NPP Hall of Fame ↗ for having two separate years of 2,000+ article reviews.

'''January–February backlog drive'''

The experimental two-month long backlog drive concluded with 183 reviewers patrolling over 27,761 articles and 35,309 redirects, earning over 36,836 points. Congratulations to {{no ping|JTtheOG}}, who achieved first place with 6,484.6 points in this drive.

'''May backlog drive'''

An article-only backlog drive is currently underway. We are hoping to make a big dent in the backlog. You can read more about it or join at Wikipedia:New pages patrol/Backlog drives/May 2026 ↗.

'''PageTriage'''

An attempt was made to get the New Pages Feed ↗ to sort by date marked as reviewed instead of date created. However we had to revert it due to bugs. We may try again in the future. You can subscribe to the Phabricator ticket ↗ if you're interested in following along.

{{refbegin}}
'''Reminders:'''

You can access live chat with patrollers on the New Page Patrol Discord ↗.

Consider adding the project discussion page ↗ to your watchlist.

To opt out of future mailings, please remove yourself here ↗.

{{refend}}
</div>

MediaWiki message delivery (talk) 23:38, 14 May 2026 (UTC)