[01:29:31] Analytics-Backlog, Labs, wikitech.wikimedia.org, Varnish: https://wikitech.wikimedia.org/beacon/statsv 404 Not Found - https://phabricator.wikimedia.org/T104359#1426895 (Krinkle) [01:31:24] Analytics-Backlog, Labs, wikitech.wikimedia.org, Varnish: https://wikitech.wikimedia.org/beacon/statsv 404 Not Found - https://phabricator.wikimedia.org/T104359#1426898 (Krinkle) Related: {069716447f35c4aee6} > https://gerrit.wikimedia.org/r/221969 Though that didn't fix it. [02:03:40] Analytics-Kanban, MediaWiki-extensions-ExtensionDistributor, Patch-For-Review: Set up graphs and dumps for ExtensionDistributor download statistics {frog} [3 pts] - https://phabricator.wikimedia.org/T101194#1426920 (MZMcBride) >>! In T101194#1412253, @Milimetric wrote: > Please don't rename this card,... [03:18:09] PROBLEM - Difference between raw and validated EventLogging overall message rates on graphite1001 is CRITICAL 20.00% of data above the critical threshold [30.0] [03:20:08] RECOVERY - Difference between raw and validated EventLogging overall message rates on graphite1001 is OK Less than 15.00% above the threshold [20.0] [06:13:29] Still dead. :( https://metrics.wmflabs.org/static/public/dash/ [07:34:41] Quarry, Patch-For-Review: Quarry does not respect ORDER BY sort order in result set - https://phabricator.wikimedia.org/T87829#1427061 (MahmoudHashemi) Awesome dude. Appears to be working on my end from the queries I tried. And hey, believe me, I know a thing or two about software development processes an... [11:04:26] Quarry, Patch-For-Review: Quarry does not respect ORDER BY sort order in result set - https://phabricator.wikimedia.org/T87829#1427207 (yuvipanda) :) part of the problem was the lack of a local dev environment - I just fixed that problem yesterday (vagrant!) - fixing things should be easier now :) [11:54:39] Quarry: Allow filtering of the final report - https://phabricator.wikimedia.org/T61764#1427229 (yuvipanda) @valhallasw how does this translate to quarry? [11:57:30] (PS1) Yuvipanda: Do not unconditionally redirect to home page after login [analytics/quarry/web] - https://gerrit.wikimedia.org/r/222891 (https://phabricator.wikimedia.org/T100162) [11:57:43] (CR) Yuvipanda: [C: 2] Do not unconditionally redirect to home page after login [analytics/quarry/web] - https://gerrit.wikimedia.org/r/222891 (https://phabricator.wikimedia.org/T100162) (owner: Yuvipanda) [11:57:48] (Merged) jenkins-bot: Do not unconditionally redirect to home page after login [analytics/quarry/web] - https://gerrit.wikimedia.org/r/222891 (https://phabricator.wikimedia.org/T100162) (owner: Yuvipanda) [12:00:30] Quarry, Patch-For-Review: Return to the starting Quarry page after login - https://phabricator.wikimedia.org/T100162#1427240 (yuvipanda) Open>Resolved a:yuvipanda Fixed! [12:09:45] (PS1) Yuvipanda: Autosize description field to expand with content [analytics/quarry/web] - https://gerrit.wikimedia.org/r/222894 (https://phabricator.wikimedia.org/T77945) [12:09:59] (CR) Yuvipanda: [C: 2] Autosize description field to expand with content [analytics/quarry/web] - https://gerrit.wikimedia.org/r/222894 (https://phabricator.wikimedia.org/T77945) (owner: Yuvipanda) [12:10:04] (Merged) jenkins-bot: Autosize description field to expand with content [analytics/quarry/web] - https://gerrit.wikimedia.org/r/222894 (https://phabricator.wikimedia.org/T77945) (owner: Yuvipanda) [12:11:27] Quarry, Patch-For-Review: Make the query description window expanable - https://phabricator.wikimedia.org/T77945#1427250 (yuvipanda) Open>Resolved a:yuvipanda Done and deployed! Thank you for reporting this and apologies for the delayed fixing. [12:12:00] Quarry: Quarry shows old username after user was renamed - https://phabricator.wikimedia.org/T73064#1427253 (yuvipanda) Hmm, good question. I'm not particularly sure how to do this... [12:12:11] Quarry: Make it possible to link to latest resultset for a query - https://phabricator.wikimedia.org/T75883#1427254 (yuvipanda) p:Triage>Normal [12:28:38] (PS1) Yuvipanda: Add a redirect to get latest output of a query [analytics/quarry/web] - https://gerrit.wikimedia.org/r/222896 (https://phabricator.wikimedia.org/T75883) [12:28:49] (CR) Yuvipanda: [C: 2] Add a redirect to get latest output of a query [analytics/quarry/web] - https://gerrit.wikimedia.org/r/222896 (https://phabricator.wikimedia.org/T75883) (owner: Yuvipanda) [12:28:55] (Merged) jenkins-bot: Add a redirect to get latest output of a query [analytics/quarry/web] - https://gerrit.wikimedia.org/r/222896 (https://phabricator.wikimedia.org/T75883) (owner: Yuvipanda) [12:33:31] Quarry, Patch-For-Review: Make it possible to link to latest resultset for a query - https://phabricator.wikimedia.org/T75883#1427273 (yuvipanda) Open>Resolved a:yuvipanda http://quarry.wmflabs.org/query/2157/result/latest/0/json w00t :) [13:06:28] Quarry: Allow filtering of the final report - https://phabricator.wikimedia.org/T61764#1427324 (valhallasw) I think allowing users to do a LIKE '%xx%' on each column would be the nicest, but I'm not sure if that's doable without killing a database server in the process. [13:21:31] Quarry: Allow filtering of the final report - https://phabricator.wikimedia.org/T61764#1427330 (yuvipanda) We can do client side filtering with the data tables library that is already being used? [13:26:50] Quarry: Allow filtering of the final report - https://phabricator.wikimedia.org/T61764#1427334 (valhallasw) If that works with pagination it sounds like a good option. [13:58:30] PROBLEM - Difference between raw and validated EventLogging overall message rates on graphite1001 is CRITICAL 20.00% of data above the critical threshold [30.0] [14:00:29] RECOVERY - Difference between raw and validated EventLogging overall message rates on graphite1001 is OK Less than 15.00% above the threshold [20.0] [14:12:15] Quarry: Quarry shows old username after user was renamed - https://phabricator.wikimedia.org/T73064#1427353 (He7d3r) I don't know if it is related but, I have a similar problem with the Wikidata Game, which also uses OAuth: https://bitbucket.org/magnusmanske/wikidata-game/issue/153/stats-are-lost-after-a-glo... [14:13:29] PROBLEM - Difference between raw and validated EventLogging overall message rates on graphite1001 is CRITICAL 20.00% of data above the critical threshold [30.0] [14:15:28] RECOVERY - Difference between raw and validated EventLogging overall message rates on graphite1001 is OK Less than 15.00% above the threshold [20.0] [14:25:09] PROBLEM - Difference between raw and validated EventLogging overall message rates on graphite1001 is CRITICAL 20.00% of data above the critical threshold [30.0] [14:27:00] RECOVERY - Difference between raw and validated EventLogging overall message rates on graphite1001 is OK Less than 15.00% above the threshold [20.0] [14:49:29] PROBLEM - Difference between raw and validated EventLogging overall message rates on graphite1001 is CRITICAL 20.00% of data above the critical threshold [30.0] [14:51:19] RECOVERY - Difference between raw and validated EventLogging overall message rates on graphite1001 is OK Less than 15.00% above the threshold [20.0] [15:18:44] Quarry: Quarry shows old username after user was renamed - https://phabricator.wikimedia.org/T73064#1427389 (yuvipanda) It's probably a similar issue - we just cache the name OAuth gives us in the db and do not change it every login. We perhaps should... [15:47:28] PROBLEM - Difference between raw and validated EventLogging overall message rates on graphite1001 is CRITICAL 20.00% of data above the critical threshold [30.0] [15:49:19] RECOVERY - Difference between raw and validated EventLogging overall message rates on graphite1001 is OK Less than 15.00% above the threshold [20.0] [16:36:09] PROBLEM - Difference between raw and validated EventLogging overall message rates on graphite1001 is CRITICAL 26.67% of data above the critical threshold [30.0] [16:38:08] RECOVERY - Difference between raw and validated EventLogging overall message rates on graphite1001 is OK Less than 15.00% above the threshold [20.0] [18:02:08] PROBLEM - Difference between raw and validated EventLogging overall message rates on graphite1001 is CRITICAL 26.67% of data above the critical threshold [30.0] [18:03:59] RECOVERY - Difference between raw and validated EventLogging overall message rates on graphite1001 is OK Less than 15.00% above the threshold [20.0] [18:29:59] PROBLEM - Difference between raw and validated EventLogging overall message rates on graphite1001 is CRITICAL 20.00% of data above the critical threshold [30.0] [18:31:58] RECOVERY - Difference between raw and validated EventLogging overall message rates on graphite1001 is OK Less than 15.00% above the threshold [20.0] [19:09:18] PROBLEM - Difference between raw and validated EventLogging overall message rates on graphite1001 is CRITICAL 20.00% of data above the critical threshold [30.0] [19:11:08] RECOVERY - Difference between raw and validated EventLogging overall message rates on graphite1001 is OK Less than 15.00% above the threshold [20.0] [20:54:49] PROBLEM - Difference between raw and validated EventLogging overall message rates on graphite1001 is CRITICAL 20.00% of data above the critical threshold [30.0] [20:58:29] RECOVERY - Difference between raw and validated EventLogging overall message rates on graphite1001 is OK Less than 15.00% above the threshold [20.0]