Appears to be a duplicate of T253053: Make it possible to add references to statements in Structured Data on Wikimedia Commons ?

Appears to be a duplicate of T230315: Allow adding references to structured data (MediaInfo) statements ?

As of today December 16th, M8979671 is still present in that query’s results.

Even logged-out, only the front-page seems accessible, eg https://quarry.wmflabs.org/query/runs/all returns 500 Internal Server Error

I can confirm this behaviour − noticed it a few hours ago.

Thanks for the answer @Trizek-WMF,

Relates to T262750: Allow to exclude bots from watchlist notifications

Relates to T167224: Implement 'User' filters and filter menu in the new UI and its subtask T209589: Have a way to exclude a bot-flagged account

There is at the moment significant friction on Wikimedia Commons: as part of StructuredDataOnCommons, a couple of bots are making millions of edits. As they are marked as bot edits, users can filter them out, but some users do want to audit bot activity on files of interest. User would thus like to exclude edits from these two bots only.

What is the status of this?

I can confirm this.

Ah ah − turns out the uploader’s username has been oversighted.

Because of T264217 , several datasets disappeared and could not be recreated. I paused the general nightly update and triggered by hand update for a handful of datasets − including monuments2019.

I’m boldly closing this as Resolved, per my comment at T20871#4311283 and the additional comments by @Gilles.

Thanks for the ping :)

The configuration had been helpfully done by @Romaine (Special:Diff/446490283) ; I had forgotten I had disabled the general upgrade cron the other week when investigating issues with the Wiki Science Competition data...

(Quick not that this error was mentioned in https://www.wikidata.org/wiki/Wikidata:Project_chat#Countries_vs._sovereign_states)

This seems reasonable ; indeed WLE 2020 Ukraine achieving 100% usage is probably not what is expected :)

In T246885#6379176, @Lokal_Profil wrote:

Looks like this still hasn't been deployed to isa.toolforge.org. Anything stopping that?

Let’s close ; these things sometimes happen with new configurations pending a webservice restart.

Unassigning myself, leaving it to @TheDJ :)

Redis caching has been live for a while now ; follow-up work can be filed as other tasks.

Thanks @bd808 for the investigation and hints!

So:

• crontab invokes jsub with the run.sh script (jsub -mem 1000m -once -j y -o /data/project/integraality/logs/update.log -N update /data/project/integraality/integraality/bin/run.sh)
• run.sh:
  • sources the virtual environment (via /data/project/integraality/www/python//venv/bin/activate)
  • runs the python script (via python integraality/pages_processor.py)

(Just lurking here ^_^)

In T194953#6232984, @Bstorm wrote:

I know when I'm messing with go, I never compile inside Toolforge directly. I just rsync things after cross-compiling on my Mac. I haven't tried that with rust.

https://wudele.toolforge.org/hQ6hmSe2Hiy79d5x works

Tentatively fixed by altering the .lighttpd config ; let’s see what users say.

Tentatively closing as invalid − something must have been fixed somewhere by someone :)

I updated a bit https://commons.wikimedia.org/wiki/Commons:Monuments_database/Harvesting − it’s not the best docs but looks fairly up to date. The one really missing part is how to configure Wikidata-based sources.

@bd808 Good point re:toolinfo.json, forgot about that. Added at https://tools-static.wmflabs.org/wudele/toolinfo.json and it’s now showing up in https://tools.wmflabs.org/hay/directory/#/search/wudele

During the hackathon I emailed back and forth with the original author, Raquel Smith. She kindly accepted to license it under MIT license \o/

• Service accessible at https://wudele.toolforge.org/
• Code at https://github.com/JeanFred/wudele-toolforge/
• Some background/recap on https://commonists.wordpress.com/2020/05/09/wudele-a-framadate-instance-in-the-wikimedia-cloud/

As far as I can tell, this is resolved − please reopen if there are additional issues.

Closing this as resolved, as most of the functionality is there. Follow-up work can be filed as separate tasks.

Good catch, fixed in 1a7a6c8 and kicked off another update:

With R2566:b74b35227cf9, the queries feature is working as well.