In T239067#5888081, @Alicia_Fagerving_WMSE wrote:

In T239067#5887729, @JeanFred wrote:

In T239067#5835510, @Alicia_Fagerving_WMSE wrote:

(Note that the dashboards only work on Wikidata so they can't be stored directly on meta, see also T243780)

Per T243780, they now (mostly) work on Meta :)
(It should actually be somewhat faster on Meta, because of the maxlag handling for Wikidata)

AMAZING <3

In T239067#5835510, @Alicia_Fagerving_WMSE wrote:

(Note that the dashboards only work on Wikidata so they can't be stored directly on meta, see also T243780)

🎉 https://meta.wikimedia.org/wiki/User:Jean-Fr%C3%A9d%C3%A9ric/Red_pandas

In T244977#5881963, @Fralambert wrote:

For the Wikipedia page, I created https://fr.wikipedia.org/wiki/Projet:Protection_du_patrimoine/image_du_R%C3%A9pertoire_du_patrimoine_culturel_du_Qu%C3%A9bec_non_utilis%C3%A9es

Closing as Resolved, the grouping-type works as expected.

Thanks! I have most of the information needed to make a config.

Trying to chart a path here:

In T243701#5834751, @jcrespo wrote:

While I understand the need of "slowing bot edits" in case of lag, I can see a problem making MW api and WDQS equivalent in SLA at the moment.

Yep, looks all good.

did someone beat me to it?

Contents of logs/update_monuments.log

2020-01-04_20:18:06 Done with the update!
[Sun Jan  5 03:00:14 2020] there is a job named 'update_monuments' already active
[Mon Jan  6 03:00:12 2020] there is a job named 'update_monuments' already active
[Tue Jan  7 03:00:18 2020] there is a job named 'update_monuments' already active
[Wed Jan  8 03:00:15 2020] there is a job named 'update_monuments' already active
[Thu Jan  9 03:00:16 2020] there is a job named 'update_monuments' already active
[Fri Jan 10 03:00:15 2020] there is a job named 'update_monuments' already active
[Sat Jan 11 03:00:14 2020] there is a job named 'update_monuments' already active
[Sun Jan 12 03:00:12 2020] there is a job named 'update_monuments' already active
[Mon Jan 13 03:00:16 2020] there is a job named 'update_monuments' already active
[Tue Jan 14 03:00:13 2020] there is a job named 'update_monuments' already active
[Wed Jan 15 03:00:14 2020] there is a job named 'update_monuments' already active
[Thu Jan 16 03:00:20 2020] there is a job named 'update_monuments' already active
[Fri Jan 17 03:00:11 2020] there is a job named 'update_monuments' already active
[Sat Jan 18 03:00:16 2020] there is a job named 'update_monuments' already active
[Sun Jan 19 03:00:16 2020] there is a job named 'update_monuments' already active
[Mon Jan 20 03:00:18 2020] there is a job named 'update_monuments' already active
[Tue Jan 21 03:00:17 2020] there is a job named 'update_monuments' already active
[Wed Jan 22 03:00:16 2020] there is a job named 'update_monuments' already active
[Thu Jan 23 03:00:12 2020] there is a job named 'update_monuments' already active
[Fri Jan 24 03:00:13 2020] there is a job named 'update_monuments' already active
[Sat Jan 25 03:00:13 2020] there is a job named 'update_monuments' already active
[Sun Jan 26 03:00:14 2020] there is a job named 'update_monuments' already active
[Mon Jan 27 03:00:17 2020] there is a job named 'update_monuments' already active
[Tue Jan 28 03:00:15 2020] there is a job named 'update_monuments' already active
[Wed Jan 29 03:00:18 2020] there is a job named 'update_monuments' already active
[Thu Jan 30 03:00:14 2020] there is a job named 'update_monuments' already active
[Fri Jan 31 03:00:14 2020] there is a job named 'update_monuments' already active
[Sat Feb  1 03:00:14 2020] there is a job named 'update_monuments' already active
[Sun Feb  2 03:00:16 2020] there is a job named 'update_monuments' already active
[Mon Feb  3 03:00:16 2020] there is a job named 'update_monuments' already active
[Tue Feb  4 03:00:13 2020] there is a job named 'update_monuments' already active
[Wed Feb  5 03:00:14 2020] there is a job named 'update_monuments' already active

I guess so! I think it’s somewhat broken to execute these PHP statements in a Python container, but oh well :)

I was really confused when not seeing Ukraine in [[Commons:Monuments database/Categorization/Statistics]], as I was under the impression that all country_config entries would be displayed 🤔

Tentatively pinging @Lokal_Profil: in case you have an opinion, really not sure how to best proceed here ^_^

In T244030#5842411, @zhuyifei1999 wrote:

So you mean read accesses should ignore maxlag? hmm
MediaWiki does respect maxlag even in a read.

In T244030#5842328, @zhuyifei1999 wrote:

So this is https://www.mediawiki.org/wiki/Manualst:Maxlag_parameter I guess in theory you could increase it to make it more aggressive, but I think it's better to get the lag fixed.

Something I forgot to mention which may be relevant: I was using packaged pywikibot 2019.11.28.

(If anyone is interested in reproducing my tests, I threw this onto a branch https://github.com/JeanFred/inteGraality/tree/jaeger − docker-compose up -d and visiting http://localhost:5000/queries?page=User:Jean-Fr%C3%A9d%C3%A9ric/Red_Pandas&property=P50&grouping=Q3359737 should be enough (the Jaeger UI will be on localhost:16686 )

I’m really not too sure how to solve the periodic update issue. I would not exactly be keen to support potentially every wiki out there to see if there is {{Property dashboard}} on it!

I think the use-case is reasonable − had not really thought about it. It is also fairly easy to do.

DeepCat is now removed from Commons.

@Daniel_Mietchen As the original requester, what do you think?

Typical Toolforge error >_> Restarted the tool and things seem to be better now :)

Nope, let’s close :)

In T237966#5654511, @Lokal_Profil wrote:

In T237966#5653274, @JeanFred wrote:

You can now pass a prefix to the template ; can you give me a test case @Lokal_Profil ?

• Example 1: Template:Monumento_Nacional_de_Chile, Property = P1186 (WLM ID), prefix=CL-

Pywikibot upgrade to latest version did not help :-( . I’ll dig deeper and file an issue upstream.

Thanks for reporting this :)

In T212573#5711073, @Andrew wrote:

As per https://wikitech.wikimedia.org/wiki/News/Cloud_VPS_2019_Purge, this project is now a candidate for deletion since no one has claimed it on wiki or responded to my emails. It's not too late to indicate otherwise on that page if it's still of use to someone.

Is that the same as T221685: Edit summary for claims on Wikimedia Commons should use Labels, not only Q-items (and P-items) and T219954: [Desired feature] Show labels instead of entity numbers on recent changes/view history pages ?

Per https://wikidata.org/wiki/Special:Diff/1068199302 this is solved :)

Closing as resolved − please file more tickets if there are other issues :)

The manual update is running − and it’s using the same script as the weekly-one. Closing as resolved.