Items within a group with a given label
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Apr 24 2020
Apr 16 2020
Regarding the syntax I brainstormed with @VIGNERON and the QS syntax is the winner :)
Apr 3 2020
Thanks @Aklapper, that sounds good.
In T180566#6024333, @bd808 wrote:@JeanFred is this still an active problem, or just a phab task that never got closed?
Mar 30 2020
In T184000#6007325, @RexxS wrote:It is unfortunate that Wikidata chose to use prose fragment case, as that never gets used in any application that I'm aware of.
Mar 29 2020
Mar 10 2020
Mar 4 2020
Mar 3 2020
In T246696#5936204, @GuillaumeG wrote:The contest dates seem ok.
It’s only used to 'discard' pictures taken too early / too late − the logs only indicate a couple of such pictures so it should be fine.
Hmmm, strange. @Chicocvenancio can you post the URL where this happens?
Here we go:
Good call @GuillaumeG, had forgotten about that. :-)
Feb 24 2020
Feb 20 2020
Feb 17 2020
Periodic upgrades also work, closing as resolved.
Feb 16 2020
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)
Feb 15 2020
Feb 13 2020
In T244977#5881963, @Fralambert wrote:
Closing as Resolved, the grouping-type works as expected.
Thanks! I have most of the information needed to make a config.
Feb 12 2020
Feb 11 2020
Feb 8 2020
Feb 7 2020
Feb 6 2020
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.
Feb 5 2020
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 🤔
Feb 3 2020
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.
Feb 2 2020
Jan 31 2020
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 )
Jan 27 2020
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.