User Details
- User Since
- Oct 24 2014, 10:10 PM (496 w, 22 h)
- Availability
- Available
- LDAP User
- Platonides
- MediaWiki User
- Platonides [ Global Accounts ]
Sat, Apr 20
Jan 7 2024
Jan 1 2024
I don't think passing the generation to a background process and check within a loop every second if it was generated would be the proper way.
Dec 19 2023
Dec 11 2023
@grin my point is to configure the antispam (spamassassin) run by ticket.wikimedia.org to trust the single ip that chapter uses to forward mail to VRTS (well, assuming it can be trusted)
Nov 15 2023
Oct 19 2023
What Referer would be provided by such app? Would the requests from the app have a User-Agent identifying it? Which one?
If alice@example.com forwards to alice@example.net, then example.net should be aware of that, so that it considers example.com as a valid relay. Otherwise, this happens, and is expected.
The outgoing ip of that chapter (or any such entity forwarding to vrts) should be added to trusted_networks, so that SpamAssassin processes it correctly, see https://cwiki.apache.org/confluence/display/SPAMASSASSIN/TrustedRelays
Sep 23 2023
@Tommy_Kronkvist you may also PGP-sign a statement that you are indeed requesting this in T346513, signed by the PGP key you listed here: https://species.wikimedia.org/wiki/User:Tommy_Kronkvist/PGP so there's no need to share secrets in private pastes.
Aug 25 2023
But it does fail if we also add --limit-rate 1M
The file can be curled down from all dcs:
for site in ulsfo eqiad codfw esams eqsin drmrs; do curl -o $site.pdf https://upload.wikimedia.org/wikipedia/commons/9/9f/ZHSY000097_%E5%AE%8B%E6%9B%B8%E4%B8%80%E7%99%BE%E5%8D%B7_%28%E6%A2%81%29%E6%B2%88%E7%B4%84_%E6%92%B0_%E5%AE%8B%E5%88%BB%E5%AE%8B%E5%85%83%E6%98%8E%E9%81%9E%E4%BF%AE%E6%9C%AC.pdf --connect-to ::upload-lb.$site.wikimedia.org ; done
Aug 24 2023
Aug 12 2023
Sorry @JTannerWMF, I had missed your comment. The user has replied informing that the image is now gone in his iOS app.
I can reproduce (using the snippet from T343795#9083114) the slowness (100% CPU) on chromium 90.0.4430.212-1~deb10u1 from Debian buster (15 May 2021), so it doesn't seem to be a bug recently introduced in Chrome.
Aug 8 2023
You should probably file it at https://github.com/znuny/znuny/issues
I see no mention of a problem of znuny (or otrs) with iso-8859-8 / iso-8859-8-i mails.
Aug 2 2023
What do you mean?
Jul 31 2023
Jul 21 2023
No problem connecting to commons.wikimedia.org from Germany.
Jun 24 2023
¿Conseguisteis encontrar/arreglar el problema?
May 25 2023
May 21 2023
May 13 2023
This variant allows choosing the target url:
I can easily reproduce the issue against wmfprod and the beta cluster.
May 5 2023
Ran
$ toolforge-jobs run ltsa-status --command /data/project/status/src/run.sh --image bullseye --schedule "1,16,31,46 * * * *" $ toolforge-jobs run ltsa-pull --command /data/project/status/src/pull.sh --image bullseye --schedule "6 2,14 * * *"
Direct locations, both "File not found":
I also hope it's not something doing MITM into the https connection without you being aware. It seems unlikely, though, and listing the https certificate you see will let us discard that idea.
Mar 24 2023
img_media_type ENUM( 'UNKNOWN', 'BITMAP', 'DRAWING', 'AUDIO', 'VIDEO', 'MULTIMEDIA', 'OFFICE', 'TEXT', 'EXECUTABLE', 'ARCHIVE', '3D' ) DEFAULT NULL,
Mar 12 2023
Feb 6 2023
After some scanning, out of 270975 articles using ficha de persona, only 264 have that bad image (< 0.1%).
Feb 5 2023
A null edit does fix it.
Feb 3 2023
Aha,! They went through acl*sre-team I had been looking in the acl*security ones. Missing puzzle pieces found.
Thanks, @Dylsss
Feb 2 2023
In T326752#8583804, @Zabe wrote:
Thats just a bit weird because then they would have been able to view protected tasks.
Error message received by a test account with no privileges
Not really. I was just testing it, and it is not. acl*security_sre is joinable by people in acl*security, so he must have already been in acl*security to be able to join there.
@Stevemunene is a member of acl*security_sre (he added himself?!)
Jan 31 2023
I think there weren't so many people with CheckUser powers in the first year and a half. With that list, you would have:
Accounts with just 1 edit will probably be just . Even those that are experienced wikipedians (e.g. a cross-wiki user from another language) and would thus perfectly know how to edit their preferences and change the skin, would probably not bother changing the skin if they are just passing by for doing a single edit, even if they didn't like the skin. The cost of editing the preferences is actually larger than standing with it for their brief interaction. It's after some editing that it would pay back. Maybe worth checking for people that edited for at least N days.
Jan 18 2023
Note that the ssh key to access wmcloud is a different one than the one for prod (ending in OLLJY vs YvU/Z), so you might be trying to log in there with the wrong key.
From the small portion, it would seem that the files were uploaded and when they were later deleted at MediaWiki, the files would be copied into the archive, and rmed from swift storage but in some cases the contents disappeared from swift but not the "filename".
Jan 8 2023
Jan 7 2023
Jan 3 2023
I agree 20k is not money for this.
Dec 31 2022
I can confirm the behavior.
It's funny, I would have probably fallocate --dig-holes <database> to reclaim the actual space from h2 behind their back.
Dec 16 2022
Regarding the naming terminology, Special:CentralAuth uses "Registered:". e.g. https://en.wikipedia.org/wiki/Special:CentralAuth/Jimbo_Wales
(that page can actually be used to find out the edit count of an user in the current wiki, albeit it is an odd path)
Nov 27 2022
(The Tangled Web is a 2012 by Michal Zalewski)
Nov 20 2022
This seems a complaint that the diff of wiki pages misinterprets some cases as delete and readd instead of noting a new line was added in the middle. _In some cases_, since I think it does properly identifies them sometimes. But with no actual example, it's difficult to determine what's happening. Not that it will necessarily be fixable for all instances, diffing is not a simple task.
Oct 26 2022
Sep 17 2022
Both https://gerrit.wikimedia.org/r/c/mediawiki/extensions/Thanks/+/593204 and https://gerrit.wikimedia.org/r/825339 look good and pretty straightforward. The default value of ThanksAllowedLogTypes isn't overriden in InitialiseSettings/CommonSettings. Yet, it is failing for a log entry which does have type rights/rights.
A bug in https://gerrit.wikimedia.org/r/825339 when implementing T191599 ?
The underlying API call returns:
Sep 12 2022
Sep 6 2022
Sep 5 2022
I suspect it's a timeout at Varnish level, and it then got cached somewhere. I was always getting 200, even when asking every dc:
Aug 30 2022
@Mentxuwiki: si reduzco el tamaño del viewport (ventana), la foto no se reduce (hace scrolling) pero el resto de componentes sí. Parece correcto. No veo por qué te desaprovecha la mitad del espacio disponible (entiendo que es ese el problema). ¿Qué estás haciendo?
Aug 25 2022
Aug 24 2022
Cairo/Downtown showed: "Africa > North Africa > Egypt > <span class="mw-page-title-main">Lower Egypt</span> > Cairo > Cairo/Downtown"
Aug 23 2022
Aug 17 2022
You are not the first one to notice it. This is basically a duplicate of T122097
Aug 11 2022
I think we should push for replacing http:// links with https:// if the external site is serving https. It removes a redirect from every reader (it adds up really easily, see T120085), and it's much more secure for the readers as well.
Aug 10 2022
Aug 9 2022
SQLite? I'm surprised it uses that, it may not be the best performant option for such a queue...
Aug 4 2022
Changing the ordering (perhaps coupled with varnish redirecting all '?title=X&action=history' to the new '?action=history&title=X' to avoid old forms) would cause an stampede in that it's like no history page is cached. I would need planification, but (partially rolled-out per wikis) I think that could be acceptable. history page requests are much lower than to articles, and they are cheap to produce at MediaWiki layer
Jul 23 2022
The SQL query uses querycachetwo (to find which users are 'active users'), which is not exposed in toolserver replicas (should it?), nor are 'gadget-%' up_property values (which would reveal the gadgets each one has enabled).
So this would have to run in the cluster.
Jun 15 2022
May 10 2022
Instead of clearing the handlers, why not avoid registering the handlers again?
Feb 2 2022
Jan 13 2022
@MoritzMuehlenhoff, did you see https://www.spinics.net/lists/stable/msg509296.html ?
Apparently upstream identified the issue as 09e856d54bda5f288ef8437a90ab2b9b3eab83d1 and reverted it on all stable trees (Debian might not have picked the revert though).
I would have expected the wikitech timeline to contain a final entry for "mx2001" back into (i.e. T297128)
Jan 12 2022
Vector was created in 2009 (became the default in 2010), so instead of vector19 it would have made more sense to call it vector2009.
If I understand this task correctly, currently the Ganeti cluster is running on stretch nodes. The VM themselves have no explicit kvm:machine_version set, which on stretch nodes means "pc-i440fx-2.8" but on buster nodes that would default to "pc-i440fx-3.1" and thus they would be incompatible.
Jan 2 2022
Dec 28 2021
I think it should be something to set at the *BagOStuff level. MediumSpecificBagOStuff has the concept of a configurable keyspace, which is then inherited by the other classes, but MediumSpecificBagOStuff::makeGlobalKey() hardcodes the keyspace to global.
Dec 7 2021
@Pealhasan.x2 one would generally mark the second report of a bug as a duplicate of the first one. However, in this case it was tracked on T293556, and only determined to be the same as this later. Marking it as a duplicate means "this is the same problem as T293556". It makes sense to put them in this orer since the work was done there. even though in this case it does happen that your report came earlier.
Oct 30 2021
Just noticed it again, this time on a page with an ampersand in the title it is shown as & (html &#38;)
Oct 4 2021
Aug 26 2021
Aug 24 2021
If we are going to make that the default for Japanese, I think it would be best not to manually add some manual markup for forcing it into every score.
Aug 22 2021
We may submit it again if needed. I would expect findActorIdInternal to be a quick action. I guess the db connection timed out while it was doing all the slow file work so the next db action (which happened to be that findActorIdInternal) failed.
Thanks. That's weird. :/
I find that the Article & Talk links that appear are a bit out of place. I would put it as a 'Discuss' link besides the edit link (which would then requires getting a suitable icon).
$wgMaxUploadSize is set on InitialiseSettings.php to 4 GB. I was under the impression that it was 1 GB, but it is set to 4 GB per 46e69532.
@Mojtaba-kd, please wait a few working days so that people may catch up. This is not so urgent it needs to be done during the weekend
What about:
It may indeed be a filesize issue.