[15:15:11] why would API say "'empty-file', 'The file you submitted was empty.'" on a PNG upload? the only change that happened during the period from when it last worked to when it stopped working was OS upgrade… weird :| [15:15:59] (regular file upload page works fine) [16:00:07] Hello, all! I was wondering if anyone has had experience with docker-compose and end-to-end testing in MediaWiki extensions. I'd like to add additional services to docker-compose within CI, but I don't see a way to do that within my extension repo. [16:41:47] oh wow it gets SIGILL [17:08:20] hmm phabricator no longer lets me log in with my wikitech account huh [18:06:56] what is the difference between regular file upload page and the API? [18:07:05] in terms of mediawiki back-end [18:07:18] I want to understand why it crashes with SIGILL [18:10:30] This means your php is buggy. No PHP code should ever cause a SIGILL. That means that's a bug on the PHP engine, not on the php code [18:11:56] Vulpix: I know but I want to know which part of PHP [18:12:13] maybe it is something about JSON [18:12:39] this started happening after I upgraded the OS and rebuilt PHP [18:13:37] Sure, there's no JSON in Special:Upload. Anyway, unless you're a PHP developer that wants to track the bug on PHP, I'd simply get a different PHP version (maybe a different minor version) [18:15:14] I am already considering this :\ [18:15:22] going back to 7.3 temporarily [18:16:34] tried disabling opcache and building with -O0 but it did not help, the moment I use the API to upload a file I get a SIGILL haha [18:42:11] SIGILL is a gcc -march mismatch where extra instructions are included that the processor cannot handle. this can be in PHP or in an extension or some other lib that is called by either [18:43:16] Remilia: ^^ [18:44:46] grknight: this is not gcc [18:45:10] built php 7.3, works fine :\ [18:45:35] sure it is.. when you "build php" gcc does the work [18:45:50] I am 100% sure it does not [18:46:47] I'm just explaining where SIGILL comes from. compilers like gcc or clang [18:47:17] sadly, I know where SIGILL is born, I just want to know where in php it happens \o/ [18:47:38] I even tried building php with DEBUG but that breaks half the extensions [18:48:54] the built php is just done incorrectly via a bad option to gcc or clang [18:50:22] Why don't you install the php that comes from your distro? [18:51:16] Vulpix: it is the PHP that comes with my distro [18:51:28] /usr/ports/lang/php74 [18:53:04] But why are you building it from sources instead of using the distributed binaries? [18:53:27] that's BSD ports which are built [18:55:56] Vulpix: 1) I need specific build options, 2) combining several package repositories is a major pain so it is easier to have one [18:56:37] though I can probably do a jail experiment to see [21:38:01] I want to confirm something here. When using apache2 sitting behind varnish, I would use $wgCdnServers for the (static) varnish IPs, and then I should use $wgCdnServersNoPurge for the non-static IPs of the apache2 servers (which are auto-scaled)? [21:55:09] jfolv: Yes. $wgCdnServers are IPs to send purges when pages are changed. $wgCdnServersNoPurge are not for sending purges, but to not use those IPs when attributing non-registered users edits (instead, MW will use one of the X-Forwarded-For IPs that doesn't match any of them) [22:08:14] Vulpix: Gotcha, thanks for the easy to understand response!