[15:06:04] yeah, the only part we use and kinda need really is by requestID/URL-ish [15:06:33] a page view often triggers 5 or 6 different reqs which makes it a bit hard/tedious to figure out which is which. [15:07:39] the current flow is WikimediaDebug -> Find -> https://performance.wikimedia.org/xhgui/?url=3687efbd-ccda-4859-8dbe-0ab4e65a98b1 -> Click the one/only result. [15:14:52] Ah, yeah, none of the search methods are implemented [15:14:53] https://github.com/perftools/xhgui/blob/f9cc1970a8cbcd9d522ddddb1c23ec029ca5cfdb/src/Xhgui/Searcher/Pdo.php [15:15:02] not just some, unless one counts "show all" as a search. [15:15:32] https://github.com/perftools/xhgui/blob/1e8b3d493176dc17c9148ca2816a219f10307056/src/Xhgui/Controller/Run.php#L34-L48 [15:15:57] The method for the search we use is getAll/$options['conditions'] [15:16:00] * Krinkle files a ticket [15:21:28] https://github.com/perftools/xhgui/issues/303 [17:18:06] Krinkle: if you are there , one question, do we have any code on mediawiki, on visual editor or similar that asses "inactivity', as in, 'nothing has happen in the UI for this amount of time' [17:20:44] nuria: No, not that I'm aware of. We don't have a "You're inactive for 5min, click here or you'll be logged out." kind of things as far as I know. We do have some cache TTLs and session expiries e.g. around saving edit process there are some optimisations that assume the user will not likely save if they'be been inactive in the editor for 2+ min. [17:20:58] but those are pretty weak assumptions and only optimisations, not visible to the user and not stored anywhere [17:21:11] as I' [17:21:20] as I'm writing this, I get loggedd out of my bank for the same reason :P [17:21:37] Krinkle: can you point me to the js that does that inference of 'you have been inactive for this amount of time'? [17:22:26] https://github.com/wikimedia/mediawiki/blob/1.34.2/resources/src/mediawiki.action/mediawiki.action.edit.stash.js [17:22:39] basically just onkeyup + onfocus/onblur for the