@Dzahn: So fast! Thanks! Test email looks as expected.

Digging more into code history related to T379376, it looks like rPHEXbc14cc06e1176db0a89deab7ffcf58b68ad36060 hid the issue in T379376 in the past, as we had H295 and H296 avoiding this situation by automatically changing task subtype. However I disabled these Herald rules as the internal implementation of custom fields had somehow changed (I'm not aware of details though) and is now broken only showing "Unknown Field" in the Herald settings (and rPHEXbc14cc06e1176db0a89deab7ffcf58b68ad36060 not doing anymore what it was supposed to do?), which made me file https://we.phorge.it/T15885 and https://we.phorge.it/T15887 in upstream to potentially make Phorge code more robust.

Code triggering this behavior is custom hasTagView() in https://gitlab.wikimedia.org/repos/phabricator/extensions/-/blob/wmf/stable/src/customfields/DeadlineEditEngineSubtype.php not checking that the storage value can be empty, basically:

This might be a duplicate of T243119: Diacritics on letters horizontally shifted in Windows/Chrome browsers in article names and section headings.

Hi @Guseynaga, thanks! This seems to be about https://tly.wikipedia.org/wiki/Ǧulam_Ələkbərov (please always include steps to reproduce).

Please see the "file a task" link on https://www.mediawiki.org/wiki/Phabricator/Creating_and_renaming_projects for required data

I also now merged this into upstream: https://we.phorge.it/rP828ea9bca0309b01164af0bee90860bc06abdc0b

Not sure why this was tagged with WMF-Legal?

@Sophivorus: Thanks. Does that mean that no ContributionCredits issues should be reported in Wikimedia Phabricator, and ContributionCredits issues in Wikimedia Phabricator should be closed as invalid and reporters be pointed to the Talk page? Asking as it takes manual triage efforts to look up maintainers and subscribe them on Phabricator tasks due to the missing Phabricator project (the project would allow maintainers to watch the Phabricator project, thus no manual triage efforts required).

+ Recommendation-API (please add project tags so other people who don't know or don't care about team tags can also find tasks. Thanks!)

+ Recommendation-API (please add project tags so other people who don't know or don't care about team tags can also find tasks. Thanks!)

11 years later I assume that most people somehow managed Google's 2013 change.

Duplicate of T326042: Synchronise state of notifications between tabs?

@Gbergamin: Please do not create empty tickets but always fill out all fields - otherwise there is nothing that developers can do. Thanks!

@mehtab.ahmed: Please edit the task description so it has

• a clear and complete list of exact steps to reproduce the situation, step by step, including full URLs, so that nobody needs to guess which page is shown where
• what happens after performing these steps to reproduce,
• what you expected to happen instead,
• a full link to a web address where the issue can be seen,
• the web browser(s) and web browser version(s) that you tested.

All in separate (!) sections.
You can edit the task description by clicking Edit Task. A clear description should allow any other person to follow these steps (without having to interpret anything) and see the same results. Problems that others can reproduce can get fixed faster. Thanks again!

@Bethany: Assuming this is within the Research basket, so adding that project tag so other people can also find this task when searching via projects or looking at workboards. Please set appropriate project tags when possible. Thanks! :)

See also T152840, T138136.

I don't immediately see how this is related to the Translate extension but feel free to correct me

I wouldn't say so. :)

Hi @Mahabarata73, thanks for taking the time to report this!
We do not use this upstream Phorge code in Wikimedia Phabricator, and other places in the codebase also use in %sms.' without a space, so it's consistent and I am declining this report.
For future reference, please set the project tag #phabricator on your tasks in Wikimedia Phabricator about Wikimedia Phabricator. Thanks!

@Calebgcooper: "Visibility" of what exactly, and why these uninvolved folks?

Cannot reproduce with Firefox 132 on Linux, being logged in

Why 7 years and not 6 or 8? Why introduce a timeframe?

See https://www.mediawiki.org/wiki/Phabricator/Code ; this should be solved in https://we.phorge.it/

@Nikerabbit Please bring this up either on https://www.mediawiki.org/wiki/Talk:Phabricator/Help for discussion, or as a request in a dedicated task so it's not buried as a comment in an unrelated task - thanks!

This seems to be about https://www.mediawiki.org/wiki/Extension:AIEditingAssistant but that page doesn't link to an issue tracker. It should...

Done

In T376745#10337419, @Jdlrobson-WMF wrote:

My account Jdlrobson is a legacy account inherited from Bugzilla and associated with my volunteer account Jdlrobson.

@SBisson: See https://phabricator.wikimedia.org/project/profile/161/

Resolving. There was some discussion about the rate of ResourceLoader Backend Requests on https://grafana.wikimedia.org/d/000000066/resourceloader decreasing slower than usually on Thursdays after deploying to group2 but according to Krinkle "it's not unsustainable and not clear if it's even branch related".

[Please use the feature form linked at the top to create feature requests - thanks!]

In T378451#10307350, @Yann wrote:

May I know how long this will take?

Until someone finds time to volunteer to do this. No need to remind about weeks.

I can reproduce the problem locally with latest librsvg 2.59.1 on Fedora 41 so might be worth to upstream to https://gitlab.gnome.org/GNOME/librsvg/-/issues/ if not already existing there:

ak@ac:~/$ wget https://upload.wikimedia.org/wikipedia/commons/d/d0/Asiatischer_Monat_2019_Goldmedaille.svg
ak@ac:~/$ RUST_BACKTRACE=full rsvg-convert -w 200 -f png -u -o Asiatischer_Monat_2019_Goldmedaille.png Asiatischer_Monat_2019_Goldmedaille.svg 
Error rendering SVG Asiatischer_Monat_2019_Goldmedaille.svg: rendering error: NoMemory
ak@ac:~/$ rpm -q librsvg2
librsvg2-2.59.1-1.fc41.x86_64

Only potentially related one in upstream I found is https://gitlab.gnome.org/GNOME/librsvg/-/issues/658

See also recently reopened T115430: Undeploy the 'Cologne Blue' and 'Modern' skins from Wikimedia production.