Hii @Ifeatu_Nnaobi_WMDE, this ticket is done and is currently tracking the "From Wikidata" clicks using TestKitchen. The ticket can be closed.

Update: T417510 is scheduled to go on prod by 19 March for all wikis and will start collecting metrics on 20 March using TestKitchen. Thanks @Sfaci for the help along the way!

Update: This patch is scheduled to go on prod by 19 March 2026 for all wikis and will start collecting metrics on 20 March 2026 using TestKitchen.

Hii @ldelench_wmf, T344984 is not within our team's (Wikidata Integration Team) scope at the moment and will not be working on it in the near future. But we're happy to discuss it to see where it might fit in. Thanks!

This will be a migration from eventLog to using Test Kitchen
https://wikitech.wikimedia.org/wiki/Test_Kitchen/Measure_product_health#

Due to the rapid increase in wb edits in wbc_entity_usage (-23% -> -12%) compared to the initial measurement before any intervention (which we think is due to the pages being purged after 1 month). We will be increasing the frequency of measuring the changes to once every week.

Thanks @Dzahn!

Verified the key out of band and added more details to the ticket description as part of the conversation with @Dzahn

Hi, thanks @Dzahn. The ticket has been changed from "restricted" to "deployment", as this is part of the requirements to be a deployer, and "restricted" is a subset of "deployment".

Hi @Strainu, did you experience a faster change time when you were doing the same action previously?

NDA signed on my end. Thanks!

After some research, it seems like the problem lies in the masking tables, the schema of the object is different after the patch. This causes different output behavior between pairs and ipairs. We will share more updates asap. Thanks!

Thanks for the info, @dancy! We will keep this in mind for future patches.

Updated the paste to include a better non-duplication script

Thanks @Volker_E!

Hi @Volker_E @DTorsani-WMF, we were checking the codex release, and didn't find any new release. Is it updated here, or are there other places that we should be checking? Sorry for bothering you, we just want to understand the schedule when the icons will be present in the MW codebase.

Thanks @DTorsani-WMF, appreciate the help!

Hi @DTorsani-WMF! Unfortunately, no one on my team has the right access to create a branch in the Figma file. Could you let us know the best way to proceed?

Hi @Volker_E @DTorsani-WMF, thanks for the updates. Should we add both icons directly to the Figma file? Would the icons be included in the next Codex release tomorrow?

Yes, it seems like it is related to our patch. But this will only occur if we go from wmf.18 to wmf.17, but it will not happen when we are going from wmf.17 to wmf.18. This is because the latter version already knows about "A" aspects, but when the version is going backwards, it doesn't know about the "A" aspects.

As the migration phase might take more than a month, probably even years, plus we have no guarantee that all the "O" aspects that are related to aliases will be fully migrated to "A.xx" within the period. Therefore, we will be writing a script to do the migration to force a refresh.