Fri, Nov 8
Sep 24 2019
Aug 22 2019
what kind of impact the solving of the issue will generate and why?
who/what is suffering from it ?
- on boarding young developers increase in cost too as they need to get to learn and work with semi-outdated and limitef APIs and standardbof JS.
what the current problem(s) are ?
we cannot use es5/6 features that are not supported by browsers yet and cannot be polyfilled in runtime (like URI api. ref: T117651: Align mediawiki.Uri more with the native URL constructor and <the one with browser.URI>)
Aug 21 2019
@WMDE-leszek that's great! I remember seeing it differently locally when I tested adding the id back a while back, or maybe I just assumed it will land on the a tag from the code (that seems to do some magic there). Either way, I should've waited and checked on beta :)
@Ladsgroup yeah probably.. There might still some that might break because the id now is on the a tag and not a wrapper element like it used to be.
Jun 28 2019
yeah we need some column for such cases.
Jun 6 2019
May 25 2019
Thanks @waldyrious very much for your contribution on the spot!
Apr 13 2019
Moved back to be briefly discussed, estimated and broken down.
Wow in minutes .. it took a query on wb_terms >5 minutes to get 50 results only. Same on Query Service. How did you find those?
Apr 11 2019
oh yeah sure that won't be running in production like that .. I just was wondering if there are any extra optimization here that I could've missed re using indexes or using the sub-queries.
Mar 26 2019
Feb 20 2019
yes I did. I should add that the only teats failing for me now are WikibaseLexeme ones, specifically mwbot logins. There is an invalid edit token (+\\ feels truncated or smth) being stored and reused by the test sometimes, causing Invalid CSRF Token error.