@komla I'm aware of those, but does this mean that using/running crontab from the command line in tool accounts is going away? I have a script (which drives my recurring database reports) that requires awk, mariadb, and python3.11. Obviously, I'd have to use different containers for each command. Ideally, I'd like to run sequential toolforge jobs (using the --wait arg) driven by this script. This would make migrating fairly straightforward. Otherwise, I'll have to more-or-less rewrite the entire thing which would be a heavy lift.

@nskaggs Do you know if the cron (i.e. crontab) functionality of toolforge tool accounts is going away with the deprecation of Grid Engine? Thanks!

@komla @nskaggs Going to need additional time to rewrite my tool. Could I please get a time extension on the shutdown? Thanks.

Sure, and would probably also be good to mention this on the mediawiki-api-announce mailing list

Did some more testing, and I'm only seeing this occurring with URLs consisting of a bare domain (e.g. https://www.apple.com -> https://www.apple.com/); according to this superuser post, these are equivalent. As @LucasWerkmeister correctly points out above, this is a serious problem only if https://github.com/foo becomes https://github.com/foo/ because depending on the website, these could be routed differently.

Tried implementing a little over a month ago, however I need an environment that has both python 3.9 & the mysql/mariadb command

I think this task should be closed as premature. Mike's proposal lacks community consensus on enwp, doesn't fix an actual problem, and should therefore not be enacted in any way, shape or form.

Any progress on this? Upload by url has literally been around for years and being unable to import from *.wikimedia.org is a pretty massive oversight.

When I try to delete File:Dr. Richard Pierzchajlo, Head Shot, 2017.jpg I get

Error deleting file: The file "mwstore://local-multiwrite/local-deleted/q/q/2/qq22rrn3rkspulntfholqkxlpie4wo1.jpg" is in an inconsistent state within the internal storage backends

probably related: T200402

Another example: Category:Candidates for speedy deletion; at the time of writing, here are 10 items in the category, but wikitext {{PAGESINCATEGORY:Candidates for speedy deletion}} yields 484.

Sorry, but I'm not sure what you mean by that.

Seems to have fixed itself; I'm able to delete the file now.

Fixed in August last year: 1, 2. Didn't know someone had created a ticket for it. Anyways, all is good now.

In T132650#3297350, @Revent wrote:

@Fastily I think the main concern here, really, is simply Commons.... for any other wiki, the volume of 'valid' audio or video uploads should be sufficiently low that abuse would be easily recognizable.

How could this possibly work for Wikis that permit fair-use? Concerned there will be *many* false alarms.

Not entirely relevant to this task, but worth mentioning that I'm working on a cross-platform, standalone tool, MTC!, which is designed to simplify and correctly perform the Transfer to Commons process.

Tim just took care of this.

In T89807#1193619, @scfc wrote:

Could you please go through and archive/delete the remaining files of the tool? Thanks!

any updates?