-> T234450#5629763

See https://meta.wikimedia.org/wiki/Abstract_Wikipedia/Plan#Task_P1.1:_Project_initialization, which explicitly mentions a bug (i.e. Phabricator) component.

Please make sure data does not got deleted when only a history revision is suppressed.

I don't like this solution, as community also want these data (T208425#5994513). I even think we should have a Hadoop installation in Labs.

https://meta.wikimedia.org/wiki/Wikirecords is a proposed project that will help to find upstream errors.

Pywikibot should allow infinite retry on maxlag timeout (unless in unit tests). At least the default number of retries should be increased to 1000.

For users familiar with English Wikipedia short descriptions, they may not easily understand the difference.

I mean e.g. to see the history of all pages created by one specific user.

I oppose using "blocklist" as it is easily misspelled.

See https://gerrit.wikimedia.org/g/mediawiki/extensions/Wikibase/+/HEAD/lib/includes/Store/WikiTextPropertyOrderProvider.php#47

Adding a character to $wgInvalidUsernameCharacters will not affect existing users. Still, I oppose adding it.

"Not so many users are aware of a workaround like this" is only a social problem, so I oppose any technical solution.

So adding to global Title blacklist will make it unusable in new accounts but does not require any change in MediaWiki software or Wikimedia config.

As this don't think a technical requirement (i.e. creating new accounts will not make these accounts unusable), I propose to only add it to https://meta.wikimedia.org/wiki/Title_blacklist. Other MediaWiki may not have ping template, and those having it can easily workaround via 1=Username.

We have https://en.wikipedia.org/wiki/Module:Suppress_categories and interwiki may be suppressed in a similar way.

In https://www.wikidata.org/wiki/Wikidata:Property_proposal/approval_of_subject, it is proposed that an agreement may be appended in a signature. For example, when a explicit waiver of privacy is needed and explicitly agreenment for any reuse of 3rd-party is required.

But for Wikidata maxlag issue a higher number of retry. For example for a lag of one hour we need 180-720 retries (this is only an extreme situation).

In T242081#5853949, @Dvorapa wrote:

$ python pwb.py shell
Welcome to the Pywikibot interactive shell!
>>> s=pywikibot.Site('wikidata', 'wikidata')
>>> s
DataSite("wikidata", "wikidata")
>>> s.namespaces
Sleeping for 5.0 seconds, 2020-02-05 22:13:51
Sleeping for 5.0 seconds, 2020-02-05 22:13:56
Sleeping for 5.0 seconds, 2020-02-05 22:14:01
Sleeping for 5.0 seconds, 2020-02-05 22:14:07
Sleeping for 6.0 seconds, 2020-02-05 22:14:12
Sleeping for 7.2 seconds, 2020-02-05 22:14:19
Sleeping for 8.4 seconds, 2020-02-05 22:14:26
Sleeping for 9.6 seconds, 2020-02-05 22:14:35
Sleeping for 10.8 seconds, 2020-02-05 22:14:45
Sleeping for 12.0 seconds, 2020-02-05 22:14:56
Sleeping for 13.2 seconds, 2020-02-05 22:15:08
Sleeping for 14.4 seconds, 2020-02-05 22:15:21
Sleeping for 15.6 seconds, 2020-02-05 22:15:36
Sleeping for 16.8 seconds, 2020-02-05 22:15:52
Sleeping for 18.0 seconds, 2020-02-05 22:16:09
Traceback (most recent call last):
  File "<console>", line 1, in <module>
  File "/home/pavel/pywikibot/pywikibot/site.py", line 1019, in namespaces
    self._namespaces = NamespacesDict(self._build_namespaces())
  File "/home/pavel/pywikibot/pywikibot/site.py", line 2618, in _build_namespaces
    for nsdata in self.siteinfo.get('namespaces', cache=False).values():
  File "/home/pavel/pywikibot/pywikibot/site.py", line 1660, in get
    preloaded = self._get_general(key, expiry)
  File "/home/pavel/pywikibot/pywikibot/site.py", line 1606, in _get_general
    default_info = self._get_siteinfo(props, expiry)
  File "/home/pavel/pywikibot/pywikibot/site.py", line 1529, in _get_siteinfo
    data = request.submit()
  File "/home/pavel/pywikibot/pywikibot/data/api.py", line 2243, in submit
    self._data = super(CachedRequest, self).submit()
  File "/home/pavel/pywikibot/pywikibot/data/api.py", line 2089, in submit
    raise TimeoutError(
pywikibot.exceptions.TimeoutError: Maximum retries attempted due to maxlag without success.

LOL

The number of second was current Unix time/60, which means unavailable server are treated as have a epoch of zero.

This user should email stewards@wikimedia.org, who will be able to create an account for the user. He should explicitly ask for the "captcha-exempt" user group which stewards may assign.

MediaWiki itself does not define a "steward" group.

@Ammarpad Unless there are other reasons not to do it, this should be revisited after the subtask is resolved.

Are there any other use cases other than this? If there're no other use case this should be reopened with a blocking task.

This breaks Widars too as Widar sleeps 3*maxlag+1 seconds before edits, and now Widar sleeps 919 days.

Maxlag now climbed to 300+ days again: https://grafana.wikimedia.org/d/000000170/wikidata-edits?orgId=1&from=1589485983686&to=1589486256637

Notes backend QuickStatements batches seems broken for this reason.

This is a issue of https://www.wikidata.org/wiki/MediaWiki:Gadget-AuthorityControl.js.

Please use https in $wgWBClientSettings['repoUrl']. WikibaseClient.example.php is only an example, you should add the setting to InitialiseSettings.php (after any require_once) instead.

Option 1: We should bundle URL shortener to the container.
Option 2: We should build a small standalone service as a replacement.
Option 3: The Short URL feature should be removed completely.

getEntity is expensive, usage should be avoided.

Possible duplicate: T251457: LoadBalancer: Transaction spent [n] second(s) in writes, exceeding the limit of [n]

Do you see anything in your browser console?

Please use https://phab.wmflabs.org for testing.