Hello all
tld: if you don't use GitLab at the moment, you can skip this message.
We will change the login in GitLab from cas3 to OIDC, to stay compatible
with the upcoming GitLab release. For end-users this change should not be
noticeable. idp.wikimedia.org is still used for single sign-on. Most
changes happened under the hood.
If you have problems logging in, please reach out at
https://phabricator.wikimedia.org/T320390 or on IRC at #wikimedia-gitlab.
Thanks again @John Bond <jbond(a)wikimedia.org> and @Simon Lyngshede
<slyngshede(a)wikimedia.org> for the hard work to make that possible.
Greetings
Jelto
Hey,
In case it's interesting for anyone, the Future Audiences team at the
Wikimedia Foundation will host an office hour to talk among the Wikimedia
Foundation work around generative AI and the ChatGPT plugin experiment
(seeing if we can make sure that people who ask ChatGPT fact questions can
be made aware of when information is coming from us and be given links to
the article), among other things.
Next one is on Thursday, 14:00 UTC. More information:
https://meta.wikimedia.org/wiki/Talk:Wikimedia_Foundation_Annual_Plan/2023-…
Best,
*Johan Jönsson*Manager, Product Ambassadors
Wikimedia Foundation <https://wikimediafoundation.org/>
Hi there,
The 1.41.0-wmf.19 version of MediaWiki is blocked at group0.
The new version can proceed no further until the following is resolved:
- https://phabricator.wikimedia.org/T342747 -> Special:UserRights in
interwiki mode: Wikimedia\Assert\PreconditionException: Expected
MediaWiki\User\UserIdentityValue to belong to the local wiki, but it
belongs to 'metawiki'
Thank you for your help resolving this issue!
-- Your humble train toiler
--
Jaime Nuche
Software Engineer III
Wikimedia Foundation <https://wikimediafoundation.org/>
HINT: This is a crossposting from mediawiki-l
Hello everyone!
With this message I am reaching out to the developers/maintainers of Extension:VisualEditor. I have already tried the mw.org support desk [1] and IRC without much success.
1. I was wondering if there were any technical reasons for Extension:VisualEditor not inserting a `<br />` element on `SHIFT+ENTER`. This seems to be standard functionality in most other visual HTML editors, plus `<br />` is supported by wikitext.
2. If there was no technical reason, I'd ask for support to implement a Gadget that allows for this behavior. I have already tried a couple of things, but it looks like the `SHIFT+ENTER` event can not be handeled easily. Apparently some core code handles the event and always creates a new paragraph. I did not succeed to stop propagation and override this behavior from my handler.
Maybe I am just missing something here. Any help would be much appreciated.
[1] https://www.mediawiki.org/wiki/Topic:Xhywmkd6b0mnwjk7
Greetings,
Robert Vogel
The 1.41.0-wmf.18 version of MediaWiki is blocked[0].
The new version is currently deployed to group1[1], but can proceed no
further until the issue is resolved.
* T342282 - "View 1 notice" not working
- https://phabricator.wikimedia.org/T342282
Once the issue is confirmed and resolved the train can resume.
Thank you for any help resolving this!
-- Your humble train operator
[0]. https://phabricator.wikimedia.org/T340246
[1]. https://versions.toolforge.org/
Hi all,
Tool developers may be interested to know that Codex [1], the design
system for Wikimedia, is now available on the Toolforge CDNjs Mirror [2]
(and on upstream CDNjs [3], but you should prefer the Toolforge mirror
:P). This means you can relatively easily use the Codex components,
icons, and/or design tokens in your tools if you want, just like e.g.
Bootstrap. See [4] for an example in one of my tools. (The most
important technical bits are the importmap, import statements, createApp
call, and `components: codex` and `...codexIcons`, if you want to search
for those parts in particular.)
The Codex maintainers would probably like me to remind you that Codex
has not reached version 1.0 yet ;) I gather that it’s coming up (and
not, like, years away), but until then you should probably be ready for
breaking changes to happen. Once version 1.0 is out, CDNjs and the
Toolforge mirror should pick it up automatically, but you’ll need to
adjust the URLs in your tools like for any version upgrade (since the
version number is part of the URL – CDNjs doesn’t offer auto-updating
“latest” URLs).
The Phabricator task for Codex being available on CDNjs is T338834 [5];
if you experience any issues, you can bring them up there.
Enjoy!
Lucas
[1]: https://doc.wikimedia.org/codex/latest/
[2]: https://cdnjs.toolforge.org/
[3]: https://cdnjs.com/
[4]:
https://gitlab.wikimedia.org/toolforge-repos/wd-image-positions/-/commit/0e…
[5]: https://phabricator.wikimedia.org/T338834
Hi y'all,
Now that we are up to 1% of global traffic
<https://phabricator.wikimedia.org/T341463> and soon to be 5%
<https://phabricator.wikimedia.org/T341780> on our Mediawiki-on-Kubernetes
infrastructure <https://wikitech.wikimedia.org/wiki/MediaWiki_On_Kubernetes>,
we would like to ask deployers and developers to test MediaWiki patches on
it as well as the usual mwdebug servers.
To that end, scap, at the testserver stage, also synchronizes the mw-debug
MW-on-K8s deployment. You can reach that deployment by either:
- setting your WikimediaDebug extension's dropdown menu to
k8s-experimental
- setting the X-Wikimedia-Debug header with backend=k8s-experimental.
It would help us tremendously in diagnosing potential issues early.
You can reach out to us with any question or issues, either via phabricator
with the #serviceops and #MW-on-K8s tags, or on IRC in the
#wikimedia-mw-on-k8s channel.
Thanks in advance from the ServiceOps team, and the whole MW-on-K8s group
--
Clément Goubert (they/them)
Senior SRE
Wikimedia Foundation
TL;DR: The tests/phpunit/phpunit.php script is deprecated. Use `composer
phpunit:entrypoint` instead.
Thus far there have been three ways to run PHPUnit tests in MediaWiki:
1. Via simple composer command: `composer phpunit` / `vendor/bin/phpunit`
(only for non-DB tests)
2. Via composer entrypoint: `composer phpunit:entrypoint`
3. Via custom PHP script: `php tests/phpunit/phpunit.php`
The third method is now deprecated [1]. The `composer phpunit:entrypoint`
command, previously pointing to the phpunit.php script, now uses
`vendor/bin/phpunit`, specifying a config file that can be used with
integration and database tests. Where you would previously use phpunit.php,
you should now use `composer phpunit:entrypoint`.
The rationale behind this change is to make it easier for developers to run
PHPUnit tests, without having to determine what entry point they should use
for a given test. The previous setup also made it more difficult to
configure IDEs, because you had to switch between the available entry
points to make sure that tests were run with the expected config.
After this change, the only difference between `composer phpunit` and
`composer phpunit:entrypoint` is the config file they use (phpunit.xml.dist
and tests/phpunit/suite.xml, respectively). Note that we are also planning
to phase out the latter; you can follow the conversation in [2]. When that
happens, we will truly have a single entry point for all PHPUnit tests!
The switch from phpunit.php to composer comes with a small but potentially
significant difference: LocalSettings.php is no longer loaded in the global
scope. This should work transparently to you. If one of your settings
appear to have no effect, please report this on Phabricator [1]. The main
scenario where these issues may arise is if your configuration variable is
read early during MediaWiki setup, for instance in an extension function
[3]. You can temporarily workaround this by making the config variable
explicitly global in the place where it's being set, with `global
$wgMyGlobal;`.
Huge thanks to Timo, James F., Kosta, Antoine, Umherirrender, and everyone
who helped with this long-overdue change.
----
[1] - https://phabricator.wikimedia.org/T90875
[2] - https://phabricator.wikimedia.org/T227900
[3] - https://www.mediawiki.org/wiki/Manual:$wgExtensionFunctions
--
https://meta.wikimedia.org/wiki/User:Daimona_Eaytoy
"Daimona" is not my real name -- he/him
Hi all,
We will perform a short maintenance on contint hosts tomorrow 11 Jul 2023
08:00-9:30 UTC. We will switchover from the old host contin2001 to the new
host contint2002 due to a hardware refresh.
The machines host integration.wikimedia.org, an instance of jenkins and
zuul. Services have to be stopped and restarted, so expect some
unavailability. Alias/cname contint.wikimedia.org also maps to these
machines.
If you have any questions, reach out to me or @Antoine Musso
<amusso(a)wikimedia.org> in https://phabricator.wikimedia.org/T324659.
Greetings
Jelto