Change #1321650 had a related patch set uploaded (by Bartosz Dziewoński; author: Bartosz Dziewoński):
[oojs/ui@master] Update Arabic-language 'info' icon to new lightbulbOutline.svg
Change #1321650 had a related patch set uploaded (by Bartosz Dziewoński; author: Bartosz Dziewoński):
[oojs/ui@master] Update Arabic-language 'info' icon to new lightbulbOutline.svg
Change #1321658 had a related patch set uploaded (by Jforrester; author: Jforrester):
[operations/deployment-charts@master] wikifunctions: Lower ORCHESTRATOR_HEAP_SIZE for staging
Change #1321656 merged by jenkins-bot:
[mediawiki/extensions/WikimediaCustomizations@master] Explicitly set useParsoid to avoid being affected by changing defaults
Recently in T399175, a new 'lightbulbOutline' icon was added alongside existing 'lightbulb' (which is used instead of 'info' in Arabic). That icon is much closer in visual weight, and I think it will look a lot better in this context.
Cookbook cookbooks.sre.hosts.reimage started by swfrench@cumin2002 for host conf1009.eqiad.wmnet with OS bookworm completed:
Change #1321642 had a related patch set uploaded (by SomeRandomDeveloper; author: Fomafix):
[mediawiki/extensions/StaffEdits@master] Use RequestContext::getMain()->getRequest() instead of $wgRequest
Change #1321656 had a related patch set uploaded (by Arlolra; author: Arlolra):
[mediawiki/extensions/WikimediaCustomizations@master] Explicitly set useParsoid to avoid being affected by changing defaults
@MatthewVernon i mean deleting old score files, specifically their png version, as we mostly use svg now since a couple of weeks, so left unattended, we would be doubling the score storage that way, if we never delete old stuff. (which based on the other ticket, i'm assuming we still don't do)
In the frame of my Wikimania 2026 volunteer inverstment, I uploaded 4 video thanks to video2commons. The video was on google drive : https://docs.google.com/spreadsheets/d/1meykA6oXOjzmeQc_NHZ_jNpwuEU0pYCQqabom_-vvZ8/edit?pli=1&gid=1149501822#gid=1149501822 and everyting worked perfectly. So, if Google don't want to collaborate with us to improve the contains of Wikimedia projects, why Wikimedia projet still collaborate with Google by the use of Google's tools ? Can't we say during a meeting with Google that their behaviour is unfaire and the consequence of it could be the stop of use Google product by the Wikimedia movement ? Since the begining our movement accept all unfaire behaviour without any kind of reaction. The same thing happen with the extraction of the works made by wikimedians by the AI. Maybe it's time to stop being the obedient servants of the big tech companies. Why is the foundation so passive in the face of all this dishonesty in the commercial and business sectors?
This is 3 years old and lots of changes have been made to the uploading stack since then. Boldly closing as obsolete - file a new task if it recurs.
Change #1321653 had a related patch set uploaded (by Ahmon Dancy; author: Ahmon Dancy):
[operations/puppet@production] scap: Add optional logstash credentials file
Interesting, I can now only reproduce it if I make some change that affects the link (changing its target, label, or un-linking it), but edits elsewhere on the page or even within the same paragraph do not cause the ref to disappear.
@EAlbizzati-WMF gotcha! You already said that on the original ticket, my bad.
Data validated see https://phabricator.wikimedia.org/T433629 - closing this task
Verifying we are seeing events in beta and production app data.
Change #1321651 had a related patch set uploaded (by Dzahn; author: Dzahn):
[operations/puppet@production] admin: add ealbizzati to analytics-privatedata-users, level 1 access
The file seems to be back now. No idea what happened.
Test wiki created on Patch demo by TheDJ using patch(es) linked to this task:
https://109db81e54.catalyst.wmcloud.org/w/
Add support for creating hourly dbt DAGs
Change #1321649 had a related patch set uploaded (by Arlolra; author: Arlolra):
[mediawiki/services/parsoid@master] Explicitly set useParsoid in GetTOC tool
Closing this - data has been validated in prod data.
Add YAML job config option to run dbt test after model run
Validating that we are seeing the requested action_context.invoke_source values in iOS data in Prod data for app version 6137-r-2026-07-31
Cookbook cookbooks.sre.hosts.reimage was started by swfrench@cumin2002 for host conf1009.eqiad.wmnet with OS bookworm
Change #1321648 had a related patch set uploaded (by Arlolra; author: Arlolra):
[mediawiki/extensions/ParserMigration@master] Always affirmatively set useParsoid onArticleParserOptions
Closing since this was the parent task that was fixed in https://phabricator.wikimedia.org/T432495
Host conf1009.eqiad.wmnet rebooted by swfrench@cumin2002 with reason: Test restart of conf1009 before reimage
@Ladsgroup my comments at T362123#11515612 are relevant as well, for understanding what is and what is no longer in use.
Test wiki created on Patch demo by CMedelius-WMF using patch(es) linked to this task:
https://cb6b54e86f.catalyst.wmcloud.org/wiki/Regent's Park
Cookbook cookbooks.sre.hosts.reimage started by swfrench@cumin2002 for host conf1008.eqiad.wmnet with OS bookworm completed:
In T432983#12189685, @Scott_French wrote:@Jdforrester-WMF - Indeed, populating component/php85 is a work in progress as the builds progress. Specifically, we need to fill the component incrementally in order to satisfy build-depends for the extension packages (and things like php-defaults). @Raine will give a heads-up here when it's actually ready to be used.
Verified the fix locally and on patchdemo (https://1fc44a46e6.catalyst.wmcloud.org/w/index.php?title=Polar_bear&minMinToolbar=1).
Change #1321643 had a related patch set uploaded (by Jforrester; author: Jforrester):
[mediawiki/extensions/WikiLambda@master] metadata: Show warnings raised by a function call and flag them, if present
@Jdforrester-WMF - Indeed, populating component/php85 is a work in progress as the builds progress. Specifically, we need to fill the component incrementally in order to satisfy build-depends for the extension packages (and things like php-defaults). @Raine will give a heads-up here when it's actually ready to be used.