If you use Wiki Replicas to query wikidata termstore tables (wbt_*),
be aware that those tables are not currently getting live updates.
The Data Persistence team is working on setting up the new "x3"
section in Wiki Replicas hosts,[0] that is expected to take multiple
days to complete.
In the meantime, you can start using the following new endpoints:
- termstore.wikidatawiki.analytics.db.svc.wikimedia.cloud
- termstore.wikidatawiki.web.db.svc.wikimedia.cloud
Those endpoints are already returning data, but the data returned will
not be up-to-date. As soon as the replication of those tables is
restarted on Wiki Replicas, those endpoints will start returning live
data.
For more information, refer to the News page on Wikitech.[1]
[0] https://phabricator.wikimedia.org/T390954
[1] https://wikitech.wikimedia.org/wiki/News/2025_Wikidata_term_store_database_…
--
Francesco Negri (he/him) -- IRC: dhinus
Site Reliability Engineer, Cloud Services team
Wikimedia Foundation
Hi everyone!
We are happy to announce that from today, you can start testing the new push-to-deploy features on Toolforge.
This has been implemented as the `components` subcommand of the `toolforge` CLI on the bastions. That will give access to creating a tool configuration for the deployment, creating the deployments themselves and creating a deploy token to be used from external CI systems (ex. GitLab).
You can find more details on the features and how to start using it on the Wikitech page [1].
Notice though that this is still under active development, so we will still be working on fixing any bugs found, and adding more features during the beta itself. This means that it might be somewhat unstable and break from time to time. So we encourage you to try it out, explore it and give feedback, but right now we don't recommend relying on it.
You can keep an eye on the Toolforge changelog[2] and the wiki page[1] for the latest features and updates on it.
There's also an approximate timeline of when we will consider it as stable in the task [3], aiming for a stable system by the end of the calendar year.
Thanks a lot!
[1] https://wikitech.wikimedia.org/wiki/Help:Toolforge/Deploy_your_tool
[2] https://wikitech.wikimedia.org/wiki/Portal:Toolforge/Changelog
[3] https://phabricator.wikimedia.org/T393564
--
David Caro
SRE - Cloud Services
Wikimedia Foundation <https://wikimediafoundation.org/>
PGP Signature: 7180 83A2 AC8B 314F B4CE 1171 4071 C7E1 D262 69C3
"Imagine a world in which every single human being can freely share in the
sum of all knowledge. That's our commitment."
While investigating an ongoing issue with volume attachment (see, for
example, [0]) I reinitialized our backend messaging system[1]. This
reset should have been only barely user-facing, but for reasons yet
unknown this restart caused many network agents to crash and, along with
them, some of the cloud-vps and toolforge network.
After the initialization completed everything came back online, but it
was rough for a few minutes there. Most toolforge and cloud-vps users
should not need to do anything in response to this outage, but if your
services are sensitive to network outages and don't know how to restart
themselves, you may need to restart them.
Sorry for the downtime! Please let me know if you see any unexpected
symptoms from this outage.
-Andrew
[0] https://phabricator.wikimedia.org/T397517
[1] https://wikitech.wikimedia.org/wiki/Portal:Cloud_VPS/Admin/RabbitMQ
Starting next month, we are going to upgrade all the Wiki Replicas [0]
servers from MariaDB 10.6 to MariaDB 10.11.
We don't expect any impact to users, as there are no big breaking
changes in the new version. If you are curious, you can check the full
list of changes on the MariaDB website. [1]
I will send an update before we start the upgrade, you can also follow
the upgrade on Phabricator. [2]
[0] https://wikitech.wikimedia.org/wiki/Help:Wiki_Replicas
[1] https://mariadb.com/kb/en/changes-improvements-in-mariadb-1011/
[2] https://phabricator.wikimedia.org/T394372
--
Francesco Negri (he/him) -- IRC: dhinus
Site Reliability Engineer, Cloud Services team
Wikimedia Foundation
Cross posting for wider visibility. Please respond to the wikitech-l
thread if you have concerns or questions.
Bryan
---------- Forwarded message ---------
From: Gergo Tisza <gtisza(a)wikimedia.org>
Date: Wed, Jun 4, 2025 at 3:27 PM
Subject: [Wikitech-l] Please update your bot is if is using
(non-bot-)password-based login
To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>
Hi!
Since the introduction of AuthManager in 2016, there are two
officially supported authentication methods for bots:
obtaining a session cookie using the action=login API with a bot password;
loginless authentication using OAuth 1.0 or 2.0 with an owner-only consumer.
action=login with a normal password has been deprecated for a decade,
and action=clientlogin API was never supported for non-interactive
login. Still, in the past, these methods worked most of the time -
often enough that many bots kept using them.
This is going to change very soon as we are introducing more
interactive challenges during login to improve account security. If
your bot still uses one of the non-supported methods, please change it
now. Usually this only requires generating a bot password via
Special:BotPasswords and giving the bot that instead of your normal
password.
For the change that prompted this email, see T395205. There will
probably be more such changes in the future, and they won't be
announced separately.
Thanks for your understanding, and for your help in evolving the
Wikimedia developer ecosystem.
_______________________________________________
Wikitech-l mailing list -- wikitech-l(a)lists.wikimedia.org
To unsubscribe send an email to wikitech-l-leave(a)lists.wikimedia.org
https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/