For SDE: Until more information is available, it's hard to tell whether this is rooted in general page deletion logic or the Swift/multimedia backend. If the former, you may want to collab with CPT on this one.

Change 627900 had a related patch set uploaded (by Jeena Huneidi; owner: Jeena Huneidi):
[integration/pipelinelib@master] fix typo

Change 542604 abandoned by Arlolra:
[mediawiki/services/parsoid@master] [WIP] Enable phan-taint-check-plugin

per mw:Mainainers.

Change 627899 had a related patch set uploaded (by Volans; owner: Volans):
[operations/software/netbox-extras@master] dns: split public zones per DC

Change 627898 had a related patch set uploaded (by Volans; owner: Volans):
[operations/software/netbox-extras@master] dns: make logging less noisy

No known owner per mw:Maintainers..

Change 627895 merged by Ottomata:
[operations/puppet@production] Add razzi to ops group

In T261635#6467051, @jijiki wrote:

I have enabled it, but I still don't see any metrics, so something else is missing. I will take a look tomorrow

Change 627895 had a related patch set uploaded (by Razzi; owner: Razzi):
[operations/puppet@production] Add razzi to ops group

Change 627893 merged by jenkins-bot:
[blubber@master] .pipeline/config.yaml: add promote step

In T262452#6448600, @ssastry wrote:

Very likely a deleted / suppression revision. Nothing to do.

Hi @schoenbaechler, the APK is the same as the one in T261668#6467563

This was merged, thanks @He7d3r

Hi @schoenbaechler, the APK is the same as the one in T261668#6467563

Dashboard is now updated and fully working, see https://grafana.wikimedia.org/d/NQO_pqvMk/push-notifications?orgId=1&refresh=1m&from=now-3h&to=now&var-dc=eqiad%20prometheus%2Fk8s-staging&var-service=push-notifications

While it's correct to fail on a deleted / suppression revision, that should not be a fatal error. This kind of event should not go to the error log since it's expected behavior. The REST endpoint should probably return a 404.

Hi @schoenbaechler
https://drive.google.com/file/d/1EoFhzbtoihwByQHZPax33XiqGpBFIQE3/view?usp=sharing
Please download the APK to see the changes.

Hi @schoenbaechler, the APK is the same as the one in T261668#6467563

Is this causing CI failures in MF: https://gerrit.wikimedia.org/r/c/mediawiki/extensions/MobileFrontend/+/627877?

Thanks @Marostegui for the outline and @Papaul for the verbal context. The email's sent out to our account rep for escalation, so let's see what they can do. Thanks, Willy

DiscussionTools should be fine with that, the effect here is basically the same as having a "list gap" and it deals fine with that.

In T260330#6408193, @tstarling wrote:

Has anyone got an idea for giving the HMAC key to the server without allowing the command to have access to it? Otherwise an attacker can use a command to exfiltrate the key and then spoof requests. If it's not possible, maybe we should think about asymmetric encryption.

Per discussion in log triage meeting, doesn't warrant a rollback but should be fixed before we roll forward to all wikis.

FYI, for the Beta Cluster deployment, just yesterday I added a local commit to labs/private.git on deployment-puppetmaster04 to add a push_subscription_manager_password value to hieradata/common.yaml that is now being referenced from the instance config on deployment-push-notifications01. T262552#6464770

We've been exploring this in tech talk and unfortunately there's a lot of trickiness. Basically, the current fix will allow more donors to see translations but it will actually block some from seeing further localization, like in the case of Brazilian Portuguese. I updated my patch to get the currency translation working again but we may want to look again at whether there's anything that we can do on the mediawiki end.

It still exists, it's just hidden behind an information badge.
Picture for context: https://i.imgur.com/bRjNZgo.jpg

Thanks, @Dmantena. I'd say as long as we're able to run through the basic workflow by, say, Friday, that's fine. Good luck with today's release!

I can confirm that this works correctly now, testing on the same page as before (https://en.wikipedia.org/wiki/Animism#Old_animism) and looking at the quote box:

Thanks for picking that up, @MSantos. I guess we can close this ticket out now that we know the metrics are indeed being collected (and we have a dashboard for them).

Update

• REMOVED the following from the task description's "Done" section: "Product has the ability to run the "Query" above, independent of Product Analytics"
  • Reason: to start, a snapshot of this data is sufficient assuming it fluctuates on the timescale of years rather than months.
• ADDED the "Timing" section to the task description. We would value having this analysis completed next quarter (Q2).

Change 627893 had a related patch set uploaded (by Jeena Huneidi; owner: Jeena Huneidi):
[blubber@master] .pipeline/config.yaml: add promote step

Change 622231 merged by jenkins-bot:
[integration/pipelinelib@master] Enable deployment-charts update for published image