I plan to carve out time to look at this on Monday, Jan. 14
Jan 12 2019
If we align mobile design with Upload Wizard layout, we'll get more width for the caption input fields:
For future readers, if you've encountered a similar issue, here are some tips that you might find helpful:
Change 483852 merged by jenkins-bot:
[mediawiki/core@REL1_32] rdbms: avoid transaction status errors from ping() in rollback()
Jan 11 2019
It is working now, for me. Thanks!
We discussed this in our triage meeting this week, and decided to decline this task because filled/unfilled bullets are not being used to communicate anything meaningful on RecentChanges (unlike Watchlist, where filledness does mean something).
@Jdlrobson @pmiazga apologies for the switch up / sneak attack here. When we initially discussed the idea of an incremental/progressive AMC release I mentioned that one counter-balance I'd like is an explicit call-out on the settings page to let users know what we're up to, roughly what's coming, and a place to submit feedback. I should've explicitly mentioned to y'all that I was following through with that idea here, with these updated mocks. It sounds like we've got things sorted now.
On deployment-mwmaint01 I've checked /var/log/mediawiki/puge_abusefilter.log (last 500 lines) and I didn't see anything wrong. Should I grep for errors as well?
We discussed this with the team earlier this week.
We're planning to address this in the coming few months, possibly later this month.
In our triage meeting this week, we decided to decline this, because the help panel is aimed at new users, who generally don't know how to switch to a non-default skin like Monobook.
@Milimetric Good news from my end too :D I am able to see the events in the log file.
Probably downgrade it from UBN, since it seems it mostly stopped happening:
Changing to High as the backport was deployed.
Raising priority to UBN because parent task is UBN, and this also requires some extra work (although 1. and 2. are easy). I'll try to send a new patch today/tomorrow; @tstarling any chance you'll review this again?
Change 483037 merged by jenkins-bot:
[apps/android/wikipedia@master] Edit Tasks Activity UI tweak
So as per https://meta.wikimedia.org/wiki/Tech/News/2018/47 are we good to go now and drop these tables? Realistically I don't think this will happen before February anyways, but, do we (DBAs) have green light to drop them from now on?
Closed in favor of https://www.mediawiki.org/wiki/Wikimedia_Release_Engineering_Team/Book_club
Change 483876 had a related patch set uploaded (by MarcoAurelio; owner: MarcoAurelio):
[operations/puppet@production] [WIP] mediawiki: Stop logging each run of purge_abusefilter.pp
I just want to re-iterate our simpler way of handling build steps in Wikistats 2. In light of the problems described here, I think it deserves a second look. It's pretty standard on other nodejs projects I've looked at. We basically factor out most of our common build config and use it in two kinds of builds:
Change 483877 had a related patch set uploaded (by Jforrester; owner: Jforrester):
[mediawiki/extensions/WikibaseMediaInfo@master] CaptionPanel: Factor out Publish enable/disable, call when row deleted
Unless there are performance concerns we (Phabricator admins) generally do not care what people subscribe to using Herald.
I concur with this. I've had this same error on my browser with PHP 7.3
Change 482759 merged by jenkins-bot:
[apps/android/wikipedia@master] Switching order of Announcement and onboarding cards
Setting priority to low since the backend work for this seems quite complicated and the workaround of using MW API seems sufficient currently.