I too think I've been facing this issue – happened twice over the past 3 days, though IIRC those have been the only two occurrences this year. The bot's process remains active, but the onopen and onerror event listeners catch nothing.

T274656 is closely related to this, I guess.

Still occuring, yes. This bot log crudely suggests a rate of 2 in 100.

@GWicke The image https://hub.docker.com/r/wikimedia/mediawiki/ is under wikimedia account (hence looks official) but the description is misleading as it says "This image tracks latest production" though it was last updated 4 years ago.

The issue has been occurring with other bot libraries too, not just pywikibot. In a few cases, the issues recurs even after waiting for 5 seconds and retrying the API request.

In T270959#6714870, @Reedy wrote:

Along with that, i18n tools such as mw.language and jquery.18n should give a choice between using wgUserLanguage or wgContentLanguage, rather than always using wgUserLanguage.

Seems like a seperate request

ApiQueryLanguageInfo is related. Would it be acceptable to expand this API to also provide the i18n rules data?

In T268266#6635408, @DannyS712 wrote:

Of the supported browsers, the desktop browsers allow using the pagevisibility api, but the mobile ones don't always

Encountered this error on testwiki today. Error code is lockmanager-fail-acquirelock and error text is something like Could not acquire lock for "mwstore://local-multiwrite/local-deleted/f/a/e/fae7og4zcjppicvqojoaqgnkl8mzl6j.png".

In T263914#6703109, @Sportzpikachu wrote:

For those wanting a temporary solution, https://github.com/wikimedia-gadgets/types-mediawiki is available to use.

PageTriage appears to be using Date.js just for the single function Date.parseExact, that too for parsing the yyyyMMddHHmmss timestamp format only. This functionality can be easily made available through a utility function that extracts the date parts from the string and feeds them into Date.UTC(), and the library can then be removed.

I have requested a Rapid Grant to take on this project. Please see https://meta.wikimedia.org/wiki/Grants:Project/Rapid/SD0001/Twinkle_localisation.

T261290 is related (the number of active users per Special:ActiveUsers / ApiQueryAllUsers are much less than what Special:Statistics claims).

I have a bot that queries ORES a lot (I believe most of its requests are probably being fulfilled from the caches) and indeed it's persistently been running into 500 errors since 25 Sep.

A kinda reverse bug now seems to be occurring. Deepcat searches on enwiki in Category:Articles needing expert attention gives: "A warning has occurred while searching: Deep category query returned too many categories". No results are actually displayed (not even a limited set of results).

The problem appears to be on line 207:

$editform.find( '.templatesUsed .mw-editfooter-list' ).detach().empty().append( newList ).appendTo( '.templatesUsed' );

This is assuming that $editform.find( '.templatesUsed .mw-editfooter-list' ) exists. But that's correct only while editing the whole page. While editing a section, .templatesUsed exists but is an empty div.

It's worth noting that enwiki is currently considering making the userscript a gadget - see VPT discussion.

Is this being fixed? This bug is affecting the work of bots on wikipedia, so it would be great if this could be looked into. Thanks.

It is also very useful on Special:EditWatchlist.

@Anomie I've uploaded a simple patch that adds the autoMerge and fail options. For the overwrite option, I think it would be acceptable to merely null the basetimestamp and starttimestamp fields, since it seems that these two fields are only being used for conflict resolution?

@Anomie that link is no longer accessible, but I guess the if condition you were referring to is around L2242? Just changing that condition to if ( !$this->noAutoMerge && $this->mergeChangesIntoContent( $content ) ), and adding a noAutoMerge flag (set by ApiEditPage) would be acceptable?

Another pseudo-duplicate: T177150: Add IP range support to list=usercontribs API

@JTannerWMF I have written a patch for this. It is fairly simple. Could you review it?

Instead of adding yet another item in mw.config, it would also help if the timestamp in the page html were machine readable - enclosed in a span tag with a data-ts attribute or something with the mediawiki timestamp ("YYYYMMDDHHMM") in UTC.

In T234450#5669094, @Xaosflux wrote:

I think @Green_Cardamom is suggesting a userland "tool" (likely client-side javascript API shunt) to workaround this new limitation, such would not have any sort of direct database access?

In T234450#5622708, @MER-C wrote:

Why not make the higher limits a privileged action, just like it is in the API?

In T231357#5625810, @MaxSem wrote:

@dom_walden, looking at the above nomination:

• Log page - not sure if edit summary was present before
• Discussion page
• Template on the page itself
• Creator notification

Templates look to be working to me.

In T231357#5625610, @MusikAnimal wrote:

It's a wild guess, but I was wondering if what you're seeing is from https://meta.wikimedia.org/wiki/MoreMenu, which looks for AfD/MfD on every page, and maybe you misattributed the API call to Page Curation? I don't see any such API calls being made when in safemode.

It looks as if PageCuration is preemptively making an API call for getting prior AfD/MfD nomination page names on every single page (even on pages not in the new pages feed, and even in namespaces where it is not required). This isn't exactly a good idea performance-wise, is it? Shouldn't this be delayed until the user actually tries to mark the page for deletion?

Localhost URLs should be added to the CSP. Not being able to load javascript from a local server would severely impede development of user scripts and gadgets. Thanks.

@Reedy, @ItSpiderman can you look into this again, please. While no internal error appears now, I am still unable to to enable 2FA: the message "Failed to validate two-factor credentials" comes up every time. I have tried using both Google Authenticator as well as 2FA Authenticator apps.