Reading/Web/Chores

< Reading‎ | Web

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

Rotation (new schedule starting 6/24/21 - reminders in local time zones set in Slack):

  • Mon - Olga
  • Tues - (alternating every 3rd Tuesday) Nick, Bernard, TBD (formerly Sam's turn)
  • Wed - (alternating every 3rd Wednesday) Jon, Clare, Jan
  • Thurs - (alternating every 3rd Thursday) TBD (formerly Sam's turn), Nick, Bernard
  • Fri - (alternating every 3rd Friday) Jan, Jon, Clare
Chore Status Notes Last updated
Regressions/Site
Browser tests Looks good!

Previously:

Related Articles and Popups selenium tests failing with the same error Filed: https://phabricator.wikimedia.org/T306924

NRay (WMF) (talk) 23:21, 10 May 2022 (UTC)
Logstash

Filtered "TypeError: jQuery(document).foundation is not a function. (In 'jQuery(document).foundation(function(response){if(window.console)console.log(response.errors);})', 'jQuery(document).foundation' is undefined)" error since it is a user script affecting one person


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.

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

Jdlrobson (talk) 22:25, 11 May 2022 (UTC)
EventLogging validation errors Nothing

Still seeing T283881 which makes sense with the recent TOC A/B test config - about 137 in last 12 hrs https://logstash.wikimedia.org/goto/cec3c4b8a0c3d9af22cf73990e21cff1

Added filter to exclude.

Previously:

  • The eventlogging_QuickSurveyInitiation bug is still firing ALOT of errors (~126k in last 12 hours - see logstash) but it should be resolved if/when T305498 gets backported.
NRay (WMF) (talk) 23:21, 10 May 2022 (UTC)
Visual regression ⚠️ Desktop: All green

Mobile: 4 failures/16 pass because of flaky layout shift of footer and sidebar animation


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:
./pixel.js reference -b latest-release
./pixel.js test
NRay (WMF) (talk) 23:21, 10 May 2022 (UTC)
Triaging
Review dashboard
  • Moved T308055 to backlog
Jdlrobson (talk) 22:25, 11 May 2022 (UTC)
Check volunteer patches on Phab
  • Nada
Jdlrobson (talk) 22:25, 11 May 2022 (UTC)
Check patches on Gerrit have attention or hashtags
  • Lots of patches from editing team. Unclear if they need our input.


DO NOT DELETE: In future, we will use this query when https://bugs.chromium.org/p/gerrit/issues/detail?id=14856#c1 is resolved.


Note:

  • Make sure all tasks have reviewers and attention
  • distractions use hash tags: "team:qte", "team:product-infrastructure", "team:wikimedia-de","team:growth","team:editing","status:blocked" or "priority:low"
Jdlrobson (talk) 22:25, 11 May 2022 (UTC)
Check Slack for bug reports for code in production without Phabricator ticket Often we might report bugs initially on Slack and submit patches. For issues that have hit production, our team norm is to make sure there a bug is created so that the issue can be tracked. Check the back scroll for the last week and create Phabricator tasks where needed. Jdlrobson (talk) 22:25, 11 May 2022 (UTC)
Grooming
Review the Reading Web Backlog
  • Triaged incoming and cleaned up needs prioritization
Jdlrobson (talk) 22:25, 11 May 2022 (UTC)
Ensure goals are current Looks good OVasileva (WMF) (talk) 13:04, 11 April 2022 (UTC)
Performance Active banner campaigns are listed at Special:CentralNotice. Readers Web performance dashboards are listed here.
Page previews dashboard

Looks good

Previously:

  • API request failures seems to be higher since 02/01. It might be noise, but worth monitoring
  • Note well that the most recent HighTimeToPreview alert was triggered by a backend error.
  • We've been getting alerts for HighTimeToPreview. Looks like p95 TTP chart started going a bit haywire (up + down between 780ms - 860ms) about a week ago. Is this something to be concerned about? Jon adjusted threshold (every 5 mins for 2 mins) and haven't seen a HTTP alert since
NRay (WMF) (talk) 23:21, 10 May 2022 (UTC)

Generic dashboard

Looks good

Previously:

  • web_ui_scroll events are back since 4/26
  • Not sure if this is a known issue - web_ui_scroll events dropped starting 4/7/22
  • QuickSurveyInitiation events dropped due to T305498 - again hopefully resolved if/when backported or with train rollout.
  • Some big spikes in the "Mobile beta opt in/outs" graph (note, this is inative and likely non-Wikimedia sites and should be ignored)
  • MobileWebUIActionsTracking looks right around ~200 events/second
  • The spike in MobileWebUIActionsTracking is from the newly added init logging. We should make sure it doesn't come close to 1000 events per second and ideally is around ~200 events/second though
  • Schema:DesktopWebUIActionsTracking errors have been steadily increasing the past month
  • There was an issue with some gadgets relating to the jQuery migration (T280944). More client errors than normal.
  • EventLogging Schema errors have been down on average for the last week!
  • VirtualPageViews went offline. Now fixed. Updated Reading/Web/Notable_incidents.
NRay (WMF) (talk) 23:21, 10 May 2022 (UTC)
Mobile performance dashboard Looks good

Previously:

  • Timing metrics look much better after T305572 was resolved on 4/7/22
  • In Timing Metrics, desktop graph has significant jumps on "Fully loaded" graph starting 3/30/22 on both production and beta cluster. Logged T305572 and assigned to performance team.
  • T294871 seems to be rearing up again
  • Looks like T300075 is getting addressed, back down to normal
  • p75 backend time has increased since Jan 11: T300075
  • Regarding the below point, looks like for whatever reason data was lost during that drop
  • Interesting drops on Barack Obama on 3G and Facebook on 3Gfast -- not sure if this means something's wrong or if some recent change made them blazing fast ¯\_(ツ)_/¯
  • Obama and Facebook SpeedIndex has increased by 1.3x-1.5x since Nov 1: T294871
  • Nice to see edit response times coming back down to pre-spike levels 🎉
  • Last visual change increase on mobile Barack Obama production site, Facebook mobile production site and Obama desktop production site since Oct 1 but is most likely related to banner campaign. FYI, a noticeable layout shift involving the infobox happens on the mobile site which is related to T190083.
  • Looks ok, slight increase around Oct 1 for Barack Obama Desktop
  • edit response times have more than doubled since 9/13. Do editing know... if not let's create bug?
  • Didn't find a ticket so loggedT292082
  • VisualComplete99 [Obama, BC] is all over the place since Aug 16 though production seems relatively unaffected. Banner is running on both.

Please note anything significant on Reading/Web/Notable_incidents

NRay (WMF) (talk) 23:21, 10 May 2022 (UTC)
Search performance dashboard

Looks good.


Previously:

  • NR: I updated the graphs to show 30 days rather than 7
  • Interesting drop between 2/1/22 - 2/8/22 for the legacy search graph - what would account for this?
    • NR: I think that is when vector skin split stuff happened and no data was being collected for legacy since `useskinversion=1` no longer worked
  • Search Query to Render is lowering, looks good
  • Should we be concerned that Search Query to Render has been creeping up? - hard to say at this point as past 30 days has shown similar spike, will be interested to see next week's data


Note this is a new dashboard that displays the results of synthetic tests (not measuring real users) and is based on the work from T251544 . These metrics currently measure Vue and Legacy search performance on frwiki.

NRay (WMF) (talk) 23:21, 10 May 2022 (UTC)
Other
Check talk pages Jdlrobson (talk) 22:25, 11 May 2022 (UTC)
Say something nice to a team member! 🎉 please output on Slack and update the date! :) Jdlrobson (talk) 00:26, 24 February 2022 (UTC)
Document notable events 🎉 Documented pilot wiki roll outs. Jdlrobson (talk) 22:16, 29 April 2022 (UTC)


Archived choresEdit

Design backlog ⚠️ yeaaa, the design backlog is overgrown. I will need to work on this a bit more over the next month or two. AHollender (WMF) (talk) 18:43, 10 March 2020 (UTC)
Review #mobile Archived. Now part of the dashboard chore.


Moved T290440 into Triaged column but previous Q still stands

Previously:

Unsure if T290440 is specific to MinervaNeue or MobileFrontend

CMing (WMF) (talk) 3:46, 8 September 2021 (UTC)
Logstash beta (credentials) ⚠️ Stopped working. Jdlrobson (talk) 16:09, 13 September 2021 (UTC)

HelpersEdit

Status fields:

is fine
⚠️ needs attention
🚨 is on fire
🎉 For your attention but positive

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: