[02:12:56] https://www.php.net/manual/en/function.ignore-user-abort.php [02:13:05] ignore_user_abort(?bool $enable = null): int [02:13:07] > Returns the previous setting, as an integer. [02:13:09] thanks PHP [02:42:01] * Krinkle was just wondering the same [16:48:32] zabe: shall we start removing the ResultWrapper deprecated functions (Database ones) [16:51:22] Amir1: +1 from my side [16:53:02] zabe: awesome, patches coming :D [16:53:25] I wonder what else is game to be removed now... [16:53:37] Amir1: am I right in thinking no script to update templatelinks exists [16:53:52] is setting READ OLD | WRITE BOTH probably sensible then [16:54:20] RhinosF1: the patch for it is ready, https://gerrit.wikimedia.org/r/c/mediawiki/core/+/769705 [16:54:30] I can backport it but I honestly don't have rush on it [16:54:56] Reedy: probably can bump a release in update.php meaning removing a bunch of sql files, etc. [16:55:17] Mmm [16:55:20] 1.39 is an LTS... [16:55:31] Amir1: you've got the schema change and config variable for it in 1.38 [16:55:43] seems strange to have everything but old data [16:55:47] migration [16:57:27] Amir1, huh, same thought apparently: https://gerrit.wikimedia.org/r/c/mediawiki/core/+/770972/ [17:03:17] zabe: https://gerrit.wikimedia.org/r/c/mediawiki/core/+/742547 is similar [17:08:05] zabe: https://gerrit.wikimedia.org/r/c/mediawiki/core/+/770975 [17:08:50] RhinosF1: I don't mind either way, it's hard to make decision about third parties as I feel it's out of my scope [17:09:10] Amir1: i'm a third party and it'll keep me sane [22:14:17] I thought about it, still not convinced we should do it, specially because turning it on will add a lot of duplicate data that won't be read. Once we have the code that reads from the new system and the code to drop the old system, we can enable it for third parties, otherwise they will have duplicate data (which won't get any reads) for at least a release