[10:04:09] Hi guys, on my wiki people want to upload some large files up to 8000x5000. How do I know if it's safe to set $wgMaxImageArea = 6.4e7; ? [10:39:37] Torsten552: Just do it. If your server can't handle the amount of memory needed to create a thumnail of it, imagemagick should just crash. https://www.mediawiki.org/wiki/Manual:$wgMaxShellMemory is another setting that will prevent consuming too much memory [11:08:19] Vulpix so should I then set it to $wgMaxImageArea = 6.4e7; and $wgMaxShellMemory = 307200; [11:09:01] Try to not set $wgMaxShellMemory to more than your available memory :) [11:09:02] and if there is not enough free memory, it simply doesn't create the thumbnail? [11:09:25] total memory or free memory? [11:09:26] Imagemagick will crash. But yes, that's the consequence [11:09:34] Free memory [11:10:00] what happens if it's to high? [11:11:14] Note that you'll see an error instead of the thumbnail, but that's the same consequence if the image is larger than $wgMaxImageArea. The difference would be that MediaWiki will try to thumbnail it again and again when requested to do so, instead of refusing to thumbnail it at all [11:12:12] ok, thank you Vulpix [11:12:57] If you set the memory limit higher than your available memory, the imagemagick process will crash anyway, but chances are that there's another competing process trying to allocate more memory at the same time and this one would also crash [11:13:22] ok [11:13:24] This could crash a critical process like your webserver or who knows what [11:13:49] understood [11:14:07] think I should be on the safe side, free memory is 5gb [11:15:32] I think you can let it create the thumbnail and, if it succeeded, then reduce $wgMaxImageArea, and the generated thumbnail will still be used [11:16:07] Or even manually create the thumbnail with a program on your computer and copy it at the location where it should go [11:43:46] I just tried to install semantic mediawiki on top of a freshly installed mediawiki [11:44:22] ) Deprecated: Use of ResourceLoaderTestModules hook (used in onResourceLoaderTestModules) was deprecated in MediaWiki 1.33. [Called from MediaWiki\HookContainer\HookContainer::run in /var/www/html/w/includes/HookContainer/HookContainer.php at line 140] in /var/www/html/w/includes/debug/MWDebug.php on line 376 [11:44:32] how can i get rid of that ? [11:45:32] Adjust the error_reporting setting of php to remove deprecated warnings [11:45:59] thankyou Vulpix ! [11:46:01] how ? [11:47:21] https://www.php.net/manual/errorfunc.configuration.php#ini.error-reporting [11:47:48] Although those may come from https://www.mediawiki.org/wiki/Manual:$wgDevelopmentWarnings too (not sure how you get that variable set to "true") [11:47:54] thanks but which file should I modify ...index.php ? [11:49:14] https://www.mediawiki.org/wiki/Manual:LocalSettings.php [11:49:59] thankyou [11:54:03] Vulpix: logoktm: i think i found the problem with VisualEditor's autoconfiguration. it will not work in a containerized/docker setup in which the container network and the outside network aren't absolutely identical. so the server name has to be localhost:8181 on the outside network so that frontend things work, but localhost in the container network. [11:54:17] this is the failing request from the detailed log: [11:54:32] [http] GET: http://localhost:8181/w/rest.php/localhost/v3/page/html/Main_Page/144730?redirect=false&stash=true [11:54:34] [http] Error fetching URL "http://localhost:8181/w/rest.php/localhost/v3/page/html/Main_Page/144730?redirect=false&stash=true": (curl error: 7) Couldn't connect to server [11:55:06] testing from the outside, the URL works. from the inside of the containerm it fails. [11:55:47] it is a pattern i have seen in some places in Mediawiki/Wikibase that all URLs and host names are assumed to be globally accessible. [11:56:45] for instance https://phabricator.wikimedia.org/T264009 [12:01:21] You need a setting to tell MediaWiki which host (and port) to use for internal connections to itself, different from external connections. I don't know if such setting exists... [12:01:35] it doesn't unfortunately [12:01:50] had this issue in multiple instances :) [12:07:16] This reminds me when job runner was changed to make an HTTP connection to itself, and this setting defaulted to true: T142751 [12:07:16] T142751: Turn $wgRunJobsAsync off by default - https://phabricator.wikimedia.org/T142751 [12:07:41] Looks like "we" haven't learned from past errors :) [12:07:59] https://phabricator.wikimedia.org/T263928#6776976 [12:08:16] And that's why a connection to itself is a Bad Idea™ [12:09:48] If I add the line $wgDevelopmentWarnings = false to LocalSettings.php then the application does not even start [12:10:22] Vulpix: at least it has to be executed with caution :) [12:10:22] I have a docker running on my desktop and then conencting to port 8080 for testing purposes before moving all on a server [12:11:23] luca16: Did you miss the ";" at the end of the line? That's PHP, you must follow PHP syntax [12:12:25] @Vulipx thankyou, I did too much swift recently ... [12:12:29]  Deprecated: Use of ResourceLoaderTestModules hook (used in onResourceLoaderTestModules) was deprecated in MediaWiki 1.33. [Called from MediaWiki\HookContainer\HookContainer::run in /var/www/html/w/includes/HookContainer/HookContainer.php at line 140] in /var/www/html/w/includes/debug/MWDebug.php on line 376 [12:12:34] I still get that error message now [12:17:03] I have no idea, then. Documentation is outdated, or there's a bug [12:52:59] I confirm, deactivating the enableSemantics( 'localhost' ); line the errors go away (however of course no semantics is in place) [12:57:11] is your semantic mediawiki up to date? [12:57:25] The documentation says that for running in localhost one should simply use enableSemantics() I did so and now I get [12:57:25] Deprecated: Use of ResourceLoaderTestModules hook (used in onResourceLoaderTestModules) was deprecated in MediaWiki 1.33. [Called from MediaWiki\HookContainer\HookContainer::run in /var/www/html/w/includes/HookContainer/HookContainer.php at line 140] in /var/www/html/w/includes/debug/MWDebug.php on line 376 [12:57:44] @Majavah yes I did everything fresh this morning [13:22:50] In the past I was using SMW quite heavily and it was an excellent tool. I also contributed some extensions to it ... [13:23:12] pitty that its deployability did not improve ... [13:23:56] I was hopeing with the docker approach things would go smoothier ... [16:38:52] Majavah: Vulpix: (I know luca16 left) For future reference, it seems there perhaps was not an actual problem. Deprecation warnings are normal. If you are not yourself a SMW developer, then you can ignore them by turning off 'error_reporting' PHP setting in LocalSettings.php or php.ini. [16:39:05] or turn off 'display_errors' PHP setting. [16:39:58] There is also $wgDevelopmentWarnings which might be on by accident. [16:41:07] Ah, missed the first part. Y'all know that of course. [16:41:08] :)