Although the A category within x-trusted-request flag includes WMCS (as well as other wikimedia network traffic), it would indeed be valuable to better differentiate internal processes from true WMCS tools and services.
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
Today
Change #1214981 had a related patch set uploaded (by Adarsh2406; author: Adarsh2406):
[mediawiki/extensions/Gadgets@master] Fix: avoid unescaping entities in packaged .vue files (T404370).
Change #1214981 had a related patch set uploaded (by Adarsh2406; author: Adarsh2406):
[mediawiki/extensions/Gadgets@master] Fix: avoid unescaping entities in packaged .vue files (T404370)Treat .vue pages as data resources so ResourceLoader won't runscript-processing that can unescape HTML entities like { and }.That prevents Vue from seeing decoded {{...}} and mistakenly trying tointerpolate it in the client, which caused missing literal text.Bug: T404370Change-Id: I80ce3bd9b162a395fe3e714db4fb32e180e07bb6Signed-off-by: Adarsh Kesharwani <[email protected]>
In T376845#11132545, @Jdlrobson-WMF wrote:in short articles with big infoboxes, where the graphs end up on the left of the infobox in desktop view.
Thanks for the example. I assume in this resolution we'd want the chart to become full width? Not sure right now if this is a template issue or the chart itself. (Note getting the responsive behaviour right here is the main challenge)
In T409402#11431569, @MusikAnimal wrote:Is it still there in safemode?
Note this task concerns non-WMF wikis so should be resolved once it become the default of OATHAuth extension.
db1169 is in s1
Oh, with respect to the patch, we should also get https://gerrit.wikimedia.org/r/c/operations/cookbooks/+/976163/1/cookbooks/sre/hadoop/reboot-workers.py reviewed and merged at the same time since it's directly relevant to this
Change #1214971 merged by jenkins-bot:
[translatewiki@master] Update the location of Monaco Sidebar from GitHub to Gerrit
an-worker* partially done. made https://gerrit.wikimedia.org/r/c/operations/cookbooks/+/1214664 to allow us to reboot a subset of a cluster's hosts while still handling the need to restart one journal node at a time properly. patch needs a bit of fixup.
In T409402#11422655, @Diskdance wrote:
Change #1214971 had a related patch set uploaded (by Abijeet Patro; author: Abijeet Patro):
[translatewiki@master] Update the location of Monaco Sidebar from GitHub to Gerrit
In T411559#11427873, @Urbanecm_WMF wrote:. . . From my perspective, I understand how the labels can be misleading, especially in edge cases.
Internally, we have a mentor pool, which contains usernames of registered mentors. By default (when on the "Average" setting), everyone is in the pool twice. If someone changes their settings to "twice the average", their username will be in the pool four times. In case they set themselves to "half the average", their username will be in the pool only once. Whenever a new account registers, a random username is taken from the pool, which is the mentor we're assigning to that user. The number of times a mentor's username is in the pool is called the mentor's weight.
Re: The heading area (label, description, aliases) is unreadable (dark on dark).
@Tgr Math appears in codesearch but not in the list. Could you either add it or remove the Math tag?
@ppelberg: I’ve completed an analysis of Reference Check priority leading indicators as described in T405421.
See the summary of findings below; the full report includes expanded metrics and breakdowns by platform, number of checks, and user experience.
Note: Data reflects events logged in the first two weeks of the Reference Check A/B test on English Wikipedia. As with other Edit Check leading-indicator assessments, additional event volume will be required to confirm statistical significance. Full A/B test results will be reviewed in the forthcoming analysis for T400101.
I've restarted the php8.2-fpm service, and wsexport.wmcloud.org is at least responding again (it was offline for 21 hours).
so I rolled out that braintree patch & I think the one I was looking at cleared but I have a new one...
Change #1214750 had a related patch set uploaded (by Kimberly Sarabia; author: Kimberly Sarabia):
[mediawiki/extensions/ReaderExperiments@master] Adds ignore lines to suppress warnings
Just checking - is the bug in this task description fixed? If you can read all of the text now, and it doesn't bounce back behind the pinned buttons, I suggest moving this along to QA. If not, we should keep it here and continue to work on fixing the bug described in the task description. We can continue to work on P2 design tweaks in the punchlist as a separate effort.
I've put the emails on hold for the contacts that were Invalid E-mail address (except the couple that had recent Mailings) and now disabled the field, to be deleted in the next maintenance window (after trigger updates have been done so we lose the insert for this field).
tonisevener opened https://github.com/wikimedia/wikipedia-ios/pull/5580
tonisevener opened https://github.com/wikimedia/wikipedia-ios/pull/5580
tonisevener opened https://github.com/wikimedia/wikipedia-ios/pull/5580
Change #1214740 had a related patch set uploaded (by Cstone; author: Cstone):
[mediawiki/extensions/DonationInterface@master] Pass through app_install_id from donate wiki
We intentionally use position: sticky and scroll-margin / scroll-snap to implement the sticky header.
We’ve tested on iPhone 11 Safari 13 via BrowserStack and behaviour is normal.
The stylelint warnings are about Chrome 49–68; those are below MediaWiki’s modern grade-A target, so we’re treating these features as progressive enhancement and will:
- either adjust browserslist to match MediaWiki’s grade-A support, or
- configure plugin/no-unsupported-browser-features to ignore css-sticky / css-snappoints for this module.
@EMartin the fix seems to have worked! I was just able to charge that CID's reactivated recurring and got Gravy txn ID faaed75a-f5f3-4927-8587-c60147404eae.
Change #1214730 had a related patch set uploaded (by Eileen; author: Eileen):
[wikimedia/fundraising/SmashPig@master] Add ability to prioritise pendings by gateway_txn_id, message string
Change #1214730 had a related patch set uploaded (by Eileen; author: Eileen):
[wikimedia/fundraising/SmashPig@master] Add ability to prioritise pendings by gateway_txn_id, message string
thanks a lot :)
why am i blocked?
This is pretty much the biggest issue for charts in Russian Wikipedia.
Change #1214724 merged by jenkins-bot:
[mediawiki/core@REL1_45] REST: add explicit cast to sitemapSize calcuation to avoid warning
Oh, I just noticed how old this ticket is. We don't seem to be getting these in the last few days, so whatever was creating the bad URLs is probably fixed at least.
Change #1214590 merged by jenkins-bot:
[mediawiki/extensions/UploadWizard@REL1_43] build: fix QUnit test that requires an H1 element
Looks like that ';' is part of the reason it's looking up. I'll have it add quotes around the reason in the log for clarity.
@Pcoombe did the donate wiki piece today, so it will get to payments wiki
Change #1214724 had a related patch set uploaded (by Reedy; author: BPirkle):
[mediawiki/core@REL1_45] REST: add explicit cast to sitemapSize calcuation to avoid warning
If we retrieved Pending using sql that prioritises the correct one it looks like
Change #1214718 had a related patch set uploaded (by Krinkle; author: Krinkle):
[mediawiki/core@master] Auth: Change debug context for autocreate from $user to $performer
Change #1214626 merged by jenkins-bot:
[wikimedia/fundraising/SmashPig@master] Also apply intent=capture for recurring
Change #1214589 merged by jenkins-bot:
[mediawiki/extensions/UploadWizard@REL1_44] build: fix QUnit test that requires an H1 element
Change #1214588 merged by jenkins-bot:
[mediawiki/extensions/UploadWizard@REL1_45] build: fix QUnit test that requires an H1 element
OK - looking at it the error happened in the Smashpig processing from the IPN


