Reading/Web/Release Manager updates

This records the current state of chores as defined in the chore list. View team norms

{| class="wikitable" !Chore !Who !Status !Notes !Last updated
 * colspan="5" |Monday
 * Browser tests
 * All
 * Looks good
 * All
 * Looks good
 * Looks good

PLEASE UPDATE Reading/Web/Release timeline/Visual Changes with any expected or unexpected changes.
 * Jdlrobson (talk) 20:20, 30 June 2023 (UTC)
 * Visual regression
 * Developers
 * Developers

Visit https://pixel.wmcloud.org/ to see the latest visual diff between the latest release and master. This report is updated every hour. Update Reading/Web/Release timeline/Visual Changes with any expected or unexpected changes.

If needed, you can also run the following locally on the latest pixel version to compare the latest release to master: Previously:
 * Jdlrobson (talk) 21:53, 26 June 2023 (UTC)
 * colspan="5" |Wednesday
 * Review dashboard
 * All
 * Run through the list in "Needs triage" and tag tasks with the relevant team. If in doubt add tag #readers-web-backlog to every task here.
 * Jdlrobson (talk) 23:36, 28 June 2023 (UTC)
 * colspan="5" |Wed/Thursday/Friday
 * Logstash (client errors)
 * Developers
 * Looks good
 * colspan="5" |Wed/Thursday/Friday
 * Logstash (client errors)
 * Developers
 * Looks good
 * Looks good
 * Looks good
 * vague "Script error responsible for > 200 errors in last 12 hours. Filed T336599

Do not remove these instructions: Bugs with > 100 occurrences per 12hrs:

1) create a ticket (unless gadget - in which case use slack channel or gadget talk page).

2) Create a filter for the bug labeling the filter with the open ticket number if it belongs to.

3) If the bug does not belong to us, enable the filter by default and exclude it from the view. If the bug belongs to us, disable the filter.

For banner errors see CentralNotice/FAQ

Investigate bugs < 100 optional if have time and interested.

'When investigating bugs filter those errors out ideally using a stack trace wildcard. If a bug belongs to reading web change the label to the phab ticket number. If not add it to one of the existing team or gadget filters.'

'As part of chores we'll check and remove existing pins where the task has been resolved. The less pins at the top the cl'

Previously:
 * Jdlrobson (talk) 20:20, 30 June 2023 (UTC)
 * Logstash (PHP errors)
 * Developers
 * Looks good (most error are timeouts)
 * Looks good (most error are timeouts)
 * Looks good (most error are timeouts)
 * Mostly just slow API responses on long page.
 * Jdlrobson (talk) 20:20, 30 June 2023 (UTC)
 * EventLogging validation errors
 * Developers
 * Fiile https://phabricator.wikimedia.org/T338491
 * Fiile https://phabricator.wikimedia.org/T338491
 * Fiile https://phabricator.wikimedia.org/T338491

Previously:
 * Filed https://phabricator.wikimedia.org/T336944
 * Filed https://phabricator.wikimedia.org/T336078
 * Filed https://phabricator.wikimedia.org/T328681
 * Filed https://phabricator.wikimedia.org/T328680
 * Tagged above with team name
 * Filed https://phabricator.whttps://phabricator.wikimedia.org/T321329ikimedia.org/T321329
 * Still many errors from T317343
 * Filed T318249
 * Filed: https://phabricator.wikimedia.org/T317343
 * Dashboard was broken. I restored it by filtering type:eventgate_validation_error
 * Jdlrobson (talk) 20:20, 30 June 2023 (UTC)

Helpers
Status fields: Last updated (Use four tildes to autosign)

Link someone's username in the edit-summary to ping them! This will send them an Echo notification! Please list your preferred ping username below:

Participants:


 * User:Jdlrobson
 * User:JDrewniak (WMF)
 * User:OVasileva (WMF)
 * User:NRay (WMF)
 * User:BWang (WMF)
 * User:MAbualruz-WMF