Blog: https://addshore.com
Twitter: https://twitter.com/addshore
Meta: https://meta.wikimedia.org/wiki/User:Addshore
Wikitech: https://wikitech.wikimedia.org/wiki/User:Addshore
🦓🐝🐢
Blog: https://addshore.com
Twitter: https://twitter.com/addshore
Meta: https://meta.wikimedia.org/wiki/User:Addshore
Wikitech: https://wikitech.wikimedia.org/wiki/User:Addshore
🦓🐝🐢
I did some experimenting last week, and seemingly this might not be working for custom domains?
Navigating to https://potato.wikibase.cloud/ in an incognito window, I see Anubis right away
Navigating to https://wikibase.world/ I do not
In T400807#11093115, @Anton.Kokh wrote:Just my 5 cents: the scope of this specific ticket is to start with Wikidata. But, of course, we are looking for a solution that could eventually be applied to other Wikibases in the ecosystem. So we will have to make trade offs :)
In T400046#11083427, @Ollie.Shotton_WMDE wrote:In T400046#11051915, @Addshore wrote:Is there a downside to doubling the max connections for these mysql users and see what happens?
I did wonder about this, but given the CPU utilization was way above the resource limits we have set, I doubt increasing the number of connections would help.
This is a bit backwards given that MW already knows the DB schema and can create new DB instances.
Reading the steps, it would be very nice if the manager would also be sent an email / "notified " when the instance / instances are suspended, and why, as a follow-up context reminder.
With a slightly more wikibase ecosystem hat on
Just a thought, as I see this moving around.
As with T401826 it would be great if this didn't just end up in a private WMDE spreadsheet! :)
Will these spreadsheets be public?
It would be nice to have the aggregated data from the graphQL be accessible to all
Would there be some way to add a new permission that potentially allows "allowed" people to add values of longer lengths?
perhaps thats a compromise?
I gave it a quick shot today, and it did pertty well, however I think more context is needed as part of the MCP / cli docs for it to make the best / better decisions.
@SLyngshede-WMF, I hear from IRC that you mgiht be the "main developer of Bitu"
Does Bitu IDM have any sort of API I might be able to use?
I spent another little time looking at this today, and created a ssh command.
A user can now do mw auth developer create, and they will be guided through the IDP user creation flow.
Another couple of use cases based on some "fun" I have had with the new iceberg revision datasets is collecting metrics on the state of Wikimedia commons depicts, and instance types on wikidata and feeding that data back into mediawiki to display static pie charts and line charts showing growth in those areas over time.
This would for example allow wiki projects to see the impact they have having when adding depicts statements on masa.
And would allow wikidata to monitor the content split, particularly with bibliographic items.
One could argue some of this is possible via the query service, however the data lake is likely a better fit
Appears resolved for me!
[1678219.142803] Out of memory: Killed process 1245181 (houndd) total-vm:10779176kB, anon-rss:2384156kB, file-rss:0kB, shmem-rss:0kB, UID:0 pgtables:8884kB oom_score_adj:0 [1696463.221680] Out of memory: Killed process 3634851 (houndd) total-vm:10250760kB, anon-rss:4105284kB, file-rss:0kB, shmem-rss:0kB, UID:0 pgtables:13220kB oom_score_adj:0
It would certainly be less confusing for me :D
But I guess thats a Wikidata / Wikidata-Omega question
Same as T401459, duplicate created in error
Cross linking from the source https://www.wikidata.org/wiki/Wikidata:Project_chat#Character_limit_too_short
Is there a downside to doubling the max connections for these mysql users and see what happens?
I'm going to do a bit of a brain dump here while reading through a bunch of things...
I was reading through the code for fun while sipping a coffee, and saw some things of note that I figured I may as well mention here...
I'd love to see into https://docs.google.com/spreadsheets/d/1okCL1QeGpOp5VyZynM_CxuEA6fg7_4Y0b3eR7_HKXwM/edit?gid=0#gid=0 and see how
Does that need to be private / can the interesting bit about how be published somewhere?
Looks like your number of connections in prod is 240 https://github.com/wmde/wbaas-deploy/blob/41da54ee2e28906c6f3bc670aab64b9b5ba0120f/k8s/helmfile/env/production/sql.values.yaml.gotmpl#L42
Can confirm my access is back, many thanks all!
I re recorded one of the gen cli commands today, and can confim this behaviour has gone back to what it used to be
Though now I realize that this is indeed generated
Either I would only document /v1/tool/{toolname}/deployment/{deployment_id}/cancel once, and have latest be a "magic" deployment_id as it is technically a string.
Or the operation ID of the latest path should change.
@Dzahn so I don't actually use these images any more, as the golang ones from docker hub are accessible on the runners now.
So I'd be happy to just close this now if noone else wants it open!
Based on my request at T399152: Requesting access to analytics-privatedata-users for addshore you might want to hold off on this one :)
@dcaro want to schedule a call to walk through it all in more detail?
Is this relating to the wikibase-metadata tool?
And if so, is it relating to the graphql endpoint?
I was thinking that we wouldn't want
to change the skin where the user has specified it but that we might
want to change it where they've left it unchanged.
Cross linking to T329096: Support existing Wikibase REST API routes for Lexemes
In T321919#10939110, @dcaro wrote:Can that be split from the cli?
Just going to decline this one for now! :)
Well, I'll forever be curious about this one 😆
Looks like it went down at 2:40
Briefly worked at around 3:40 and 3:45
Then down until 10:10
I seem to remember the old default behaviour if you typed into the box quickly and hit enter that you would end up on Special:Search but with the default namespaces / more namespaces being searched
Am I miss remembering, or was there something else doing this for me 😄
So, I still experience this, currently on 2.7.50536-beta-2025-06-18
I feel like some of the messages have changed or I. Just seeing it expose itself slightly differently.
In T321919#10724833, @aborrero wrote:I like this idea, and the semantics that it brings. I would be able to copy/paste kubectl commands from the internet and just prefix them with toolforge, and that feels like a nice thing to have_
Just curious, but I didn't see the failed data reload get logged in the SAL at all? (But I did see entries for other failed data reloads)
Did it fail in some other, even more unexpected way?
2025-06-04 21:24 <ryankemper@cumin2002> START - Cookbook sre.wdqs.data-reload reloading wikidata_main on wdqs1022.eqiad.wmnet from DumpsSource.HDFS (hdfs:///wmf/data/discovery/wikidata/munged_n3_dump/wikidata/main/20250526/ using stat1009.eqiad.wmnet)
Apr 20, 2023 Removed @Tarrow (1620) @thcipriani (2321)
How about SCoT?
The 2 hosts in question
In T378943#10677876, @Olea wrote:As a user, I would like to have a dedicated place to read WBS documentation matching the version of a product I am currently using.
Also, as a user I would like to find this information in my running instance or, at least, the external links matching the version running.
And a wikibase user, that often tries to tweak and improve user facing wikibase documentation, I would like and encourage the end result to be user editable.
You can see your docker compose env with this command
So you will get a warning saying that the arch doesn't match, however everything should continue working due to the compatibility layer being used?
Is there some way I can turn on verbose logging to a file? Or can I only really achieve this by connecting to my own build dev build of the app?
Pixel 9 pro, android 15
I can neither confirm or deny that it was also happening on my pixel 7 pro and android 14 I was using last week
So, this continues being a topic that people seem to be very interested in in general.
There are already various efforts around of trying to collect this info to make it easier and automate various parts of setup for people.