[05:59:26] looks like the PHP bug tracker is down [05:59:40] or mostly down and barely usable [05:59:57] am I just trying at a bad time, or is that the general state of affairs? [06:08:04] tgr: I'm guessing something bad is happening to them. bugs.php.net is usually ok for me [06:09:14] it does seem to be messed up right now though [06:09:53] <_joe_> so, I know php core funding is in a dire situation right now [06:11:26] the doc and pecl sites are ok, just bugs down [07:12:13] yeah, works fine now [07:24:29] <_joe_> any idea who owns php.net now? [11:57:57] _joe_ not sure about who owns it, but I am managing a contract to make it possible to put it under https [11:58:39] <_joe_> they probably can't use letsencrypt indeed [11:59:21] my understanding is the issue is it is still hosted like bandwidth is really expensive and the work is to consolidate things [12:24:17] <_joe_> https://externals.io/message/104533 [12:24:58] yes that is the work we are supporting :) [18:10:51] SMalyshev, tgr found https://phabricator.wikimedia.org/T215000#4993172 for which he filed https://bugs.php.net/bug.php?id=77686 ... we may (have to) find ways to work around for now, but do you know the likelihood of this being fixed quickly and backported to 7.2? [21:51:53] subbu: not sure, that probably needs to be checked with the maintainer (which may or may not be maintaining it anymore...). It looks like some deep issue that may also depend on libxml2 (DOM ext relies on it). I wonder if libxml2 has the latest version or whether it has issues like this [21:52:28] subbu: I can take a look into it a bit later but I don't know that code particularly well so not sure whether I'd be able to help... [21:53:44] yes, it is libxml2 .. we've been working around a bunch of gaps in the DOM functionality so we can actually use php dom in our parsoid port without having to port a JS dom library to PHP before we can actually finish our parsoid port. [21:53:51] thanks about taking a look at it. [21:54:40] at some point, i think it might make sense to have an updated DOM library .. but we don't want to add that to the critical path. [21:55:23] so, anything you can find out about maintenance of libxml2 / phpdom and plans would help with that later decision. [22:11:11] tgr: is the repro case for https://bugs.php.net/bug.php?id=77686 missing a line? [22:12:04] you don't remove the div from the doc [22:12:47] yeah, the 3v4l example has $body->removeChild($div); [22:16:23] * bd808 added that in a note on the bug [22:28:28] https://mail.gnome.org/archives/xml/2003-August/msg00236.html [22:37:35] oops, thanks [22:41:19] apparently no way to edit the text of bug reports though [22:45:51] removeChild unlinks the node but doesn't destroy it, and for some reason libxml does not update the id table when a node is unlinked, only when it is destroyed [22:48:48] yup [22:49:06] if you unset($div), getElementById doesn't find it [22:49:42] https://3v4l.org/QUvhG [23:10:38] bye!