OK, that makes sense, thanks.

In T106282#7981660, @Legoktm wrote:

+1 to the change on technical merits, but as noted, this is a breaking change for anyone using this API, which is a non-zero amount of people.

@Dreamy_Jazz thanks for the ping. Yes, this change would break SPI-Tools. When I was building that part of the code, I did notice that things were wrapped in an extra layer. At the time, I just assumed something was strange on my end and worked around it (code here).

When I try to log into grafana using my toolsadmin credentials, I get "Invalid username or password"

@JeanFred do you have some example code where you use this? I tried

If you're going to talk about this on Monday, I'll hold off deploying the new key on the production instance until then.

Interesting, I'll give that a look. The last time I asked about this, the answer was essentially, "There is such a system, but it's for official WMF use only, not for toolforge". Which made me sad.

Copying my comment from T278097, and requesting that this be given a higher priority.

I'd just like to add my support to this idea. Many of the tools that run in toolforge are critical parts of the technical infrastructure that keeps the project going. They deserve all the normal logging, alerting and monitoring support that any serious production system has.

The underlying problem is described in T302357. The short version is that apparently some large and/or complicated SVG images time out during rendering. In the particular case reported in T302357, this was a featured image on the enwiki front page, so this failure occurred frequently, which apparently triggered some failure throttling code, preventing additional attempts to re-render, exacerbating the problem.

Cool, thanks. That sounds like it would be exactly what I was looking for. Even better:

For those of us less familiar with Toolforge internals, what's SAL?

This was discussed briefly in IRC. Copying the relevant snippets for reference...

That did the trick, thanks.

The file appears to be incorrectly formatted.

OK, I see it now, thanks.

Hmmm, I see the file, but it's empty:

Could I get a status update on this?

In T298655#7599988, @Majavah wrote:

On the other hand, User:2A01:4C8:1488:8B62:0:0:0:0/64 and User:2A01:4C8:1488:8B62:F997:1338:1555:BB9F/64 are both valid separate page titles in the User: namespace.

In T298655#7599892, @Jdforrester-WMF wrote:

Would you expect the request to the second to silently redirect to the first?

See also T127367

T256426 is related to this.

I assumed the spinning wheel was a progress indicator, and the fact that it never stops spinning means something is failing to complete. If that's an incorrect assumption, I'm fine with renaming this. In any case, it should show some sort of placeholder giving the user appropriate feedback.

Ooops, looks like a must have double-clicked or something and generated two copies of this. T295839 is the other. I'll leave it to those with more phab-fu to figure out how to clean that up properly.

I saw a few instances of this on checkuser.wiki a few minutes ago. It's intermittent, and seems to happen more frequently on queries with large numbers of namespaces. Discussed briefly on IRC #wikimedia-tech.

I've started a thread at https://en.wikipedia.org/wiki/Template_talk:Reflist to see if this can be fixed from the template side.

Thanks. Opened https://github.com/wikimedia-gadgets/MoreMenu/issues/17

Sort-of related to this, we've now got on enwiki both 120.29.97.74 and 120.29.97.74/32 blocked. If you go to https://en.wikipedia.org/wiki/Special:Contributions/120.29.97.74, you get:

@Jdlrobson I'm sorry, I didn't realize this was waiting on me for a response. I'm not entirely sure what to tell you. My involvement here was mostly noticing somebody else describing the problem on Village Pump and doing some initial troubleshooting.

@Cryptic showed me how to do this on my own:

There's been three different threads on the enwiki Village Pump today talking about changes to search behavior.:

If you could generate the URLs for the other size images, I'd be happy to give them a try from here.

Could you please clarify what software (e.g. Firefox, Chrome, some other tool) you're using to access pages/images that is returning 429s?

My only concern here is that showing thumbnails in a larger size might be valuable for vision-impaired users. At the other end of the spectrum, showing them in a smaller size might be valuable to people on exceptionally slow links and/or small screen sizes such as wearable devices.

In T279141#6986316, @Tacsipacsi wrote:

Firing wikipage.content may however cause new issues as well. As far as I know, currently wikipage.content is always fired with the one and only content block on the page (although the documentation doesn’t state this). If it’s fired with the preview, this expectation is broken and this may cause undefined behavior regarding the rest of the page (as scripts may consider it to be removed from the DOM tree).

In T285103#7161421, @Ammarpad wrote:

Is this duplicate of T261087?

I'm not sure who's supposed to be prioritizing phab tickets, but I've taken the liberty of marking this as high priority. One look at https://www.mediawiki.org/wiki/Talk:Talk_pages_project/Replying shows the lack of ping functionality is the run-away top item of discussion.

Just got one:

Yup, thanks for your help.

No, I've been well-behaved lately. But, I'll be happy to nail a tmux session up on one of the bastions for as long as it takes to generate an example if you like :-)

I'm assuming the attached screenshot from https://en.wikipedia.org/wiki/Wikipedia:Deletion_review/Log/2021_May_10#Category:CS1_maint:_discouraged_parameter is another example of the same issue.

Done

Got another one today:

Thanks for the quick response. That looks like it covers most of the questions I had.

I agree with @DED in their May 24, 2020 comment. I stumbled upon this while exploring the dumps. Their estimate of half the data being incorrect seems accurate. As such, I would suggest that this dump is worthless and should be eliminated. I can't imagine anybody making use of this in its current form. Producing it is a waste of machine resources, but worse than that, it's a time sink for people like me who are trying to understand the dumps.

Oh, never mind. PEBKAC. I had a ssh config file on my end which auto-mapped my local username (roy) to roysmith on the bastion. Everything is working now, thanks.

$ ssh -i $HOME/.ssh/id_rsa_wikimedia dev-buster.toolforge.org
roy@dev-buster.toolforge.org: Permission denied (publickey,hostbased).

For my personal need, either option would be fine. I can't speak for other users, but my gut feeling is nobody's going to miss 24. It really is ancient history.

Is the apostrophe being used on iOS the one from the keyboard?

Cool, thanks. I see the file systems mounted now. I'm told today was a WMF holiday, so extra thanks for taking care of this on your day off. Very much appreciated.