Thanks for working on this, @JJMC89!
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Today
Change 904389 had a related patch set uploaded (by Krinkle; author: Krinkle):
[mediawiki/core@master] es6-polyfills: Remove scripts, replace with deprecated stub
Front-end PR merged.
PR merged
I have a few questions on how to proceed with this ticket:
PR merged.
In T333469#8740059, @Reedy wrote:Is the clock on your device up to date?
Change 904387 had a related patch set uploaded (by Eileen; author: Eileen):
[wikimedia/fundraising/crm@master] CiviCRM port
Change 904386 had a related patch set uploaded (by Ejegg; author: Ejegg):
[mediawiki/extensions/DonationInterface@master] WIP: Enable CZ online banking for Adyen
@KStoller-WMF please confirm that the following is an expected scenario (checked in testwiki wmf.2)
Brian says we can add a second file, but with a different primary key:
Yep I think that would be much easier… do email and checksum as you are keyed on email right now
They replied quickly!
We have configured CZ / CZK bank transfers for WikimediaDonations (LIVE).
... but there's a catch:
Do note that there is no test environment for CZ / CZK bank transfers. To test the full flow, merchants are recommended to penny test (i.e. test in live with small amounts) on their live environment.
This is still open because flake8-colours was merged to flake8 but does not work with the CI output any longer.
Change 904385 had a related patch set uploaded (by Ejegg; author: Ejegg):
[wikimedia/fundraising/crm@master] Add new custom field for initial scheme txn ID
@Jclark-ctr when you are back on site can you please check the network mgmt cable for db1209 and db1210.
Thanks
The production role for ci::master is now applied on contint2002.
01:20 <+jinxer-wm> (ProbeDown) resolved: (7) Service miscweb1002:443 has failed probes (http_commons_query_wikimedia_org_ip4) -
01:20 <+jinxer-wm> (ProbeDown) resolved: (7) Service miscweb1002:443 has failed probes (http_commons_query_wikimedia_org_ip4) -
also see T333510
I'm recording here the result of feature testing in older browsers, based on the demo page at https://people.wikimedia.org/~krinkle/T178356.html.
Change 904384 merged by Dzahn:
[operations/puppet@production] microsites: do not expect 301 for commons-query.wikimedia.org
Change 904384 merged by Dzahn:
[operations/puppet@production] microsites: do not expect 301 for commons-query.wikimedia.org
Change 904384 merged by Dzahn:
[operations/puppet@production] microsites: do not expect 301 for commons-query.wikimedia.org
Change 904384 had a related patch set uploaded (by Dzahn; author: Dzahn):
[operations/puppet@production] microsites: do not expect 301 for commons-query.wikimedia.org
@KHernandez-WMF I did a pass over all the other sections in pretix. I made some changes, and some I left for now. I think it's helpful if you can do a pass before we connect on Friday (if you have time) and make as many changes as possible. Please take a note of the sections we have to review together. This way we can use the time together only for the parts that you need my input.
Change 904384 had a related patch set uploaded (by Dzahn; author: Dzahn):
[operations/puppet@production] microsites: do not expect 301 for commons-query.wikimedia.org
Change 904384 had a related patch set uploaded (by Dzahn; author: Dzahn):
[operations/puppet@production] microsites: do not expect 301 for commons-query.wikimedia.org
Hey all - just wanted to note that this is stalled on the outcome of the discussion in https://en.wikipedia.org/wiki/Wikipedia_talk:Requests_for_comment/Rollback_of_Vector_2022#Proposal_for_next_steps_following_the_closure_of_the_Vector_2022_RfC which might change the way we want to implement the width defaults.
@GMikesell-WMF Thanks! It looks like the Minerva scroll bar is a separate issue; can you create a new task for it?
Change 904383 had a related patch set uploaded (by Cory Massaro; author: Cory Massaro):
[mediawiki/services/function-orchestrator@master] Advance Avro schema semver to 0.0.4 and pass remaining time in calls to evaluator.
Change 904382 merged by Dzahn:
[operations/puppet@production] microsites: commons-query.wm.org only works on port 80/http
Change 904382 merged by Dzahn:
[operations/puppet@production] microsites: commons-query.wm.org only works on port 80/http
Change 904382 merged by Dzahn:
[operations/puppet@production] microsites: commons-query.wm.org only works on port 80/http
In T324602#8712185, @GMikesell-WMF wrote:@TThoabala I do have a few more questions too as seen below, thanks!
Temporary user does not have any IPs in the database - This happens if they have not made an edit in the last 90 days. Should this be blank or say something else?
CheckUserMaximumRowCount- Is it supposed to use the number I have in my Local or is it supposed to be my most recent 3 IP addresses?
Change 904382 had a related patch set uploaded (by Dzahn; author: Dzahn):
[operations/puppet@production] microsites: commons-query.wm.org only works on port 80/http
Change 904382 had a related patch set uploaded (by Dzahn; author: Dzahn):
[operations/puppet@production] microsites: commons-query.wm.org only works on port 80/http
Change 904382 had a related patch set uploaded (by Dzahn; author: Dzahn):
[operations/puppet@production] microsites: commons-query.wm.org only works on port 80/http
In T325768#8738762, @Tchanders wrote:@Tchanders , thoughts on how we should go about a temporary user link on a reverted edit?
This would be tricky since the link comes from a row in the comment table, rather than being generated as a user link by Linker::userLink (which adds the data we need to display the correct IP address). Hopefully it's not needed since there would likely be other references to this user on the history page, and at worst an admin/patroller could click through to Special:Contributions and find the IP addresses there. Tagging @Niharika and @Prtksxna for visibility.
Change 904381 had a related patch set uploaded (by Ssingh; author: Ssingh):
[operations/puppet@production] pybal: port check_pybal_ipvs_diff.py to urllib2
Flagging my comment here: T333473#8740476 because it feels like the reveal functionality should be an additional task.
In T332505#8740342, @TheresNoTime wrote:Now, I might be missing something obvious here [...]