[02:05:05] Submitting changes to all wikis is lagging/timing out for me, with occasional 503 responses [12:04:42] question for people who know about MediaWiki scap deployments: is it currently possible to deploy a config change & a MediaWiki code change (on a wmf/ branch) to production at the same time? [12:06:51] A_smart_kitten: yes [12:08:39] taavi: ahh, thank you! (in case you're curious, the context is https://gerrit.wikimedia.org/r/956060, & me wondering whether it'd be technically possible for it to be deployed at the same time as https://gerrit.wikimedia.org/r/c/mediawiki/core/+/956018 (assuming that patch is approved)) [13:24:15] Hello, [13:24:16] I have an issue with MediaWiki: [13:24:16] Version MediaWiki 1.38.1 [13:24:17] Using Google maps [13:24:17] {{#display_point: [13:24:18]   58.91, 91.20 ~ ~ ~ ~ ~ [[Position1]]; [13:24:18]   58.57, 18.20 ~ ~ ~ ~ ~ [[Position2]] [13:24:19]  |height=500px [13:24:19]  |icon=custom_icon.png [13:24:20] }} [13:24:20] In Wiki page it worked to show points with marker hasing custom_icon and beside that a lable for each point. Now, just the lable seen in the map and marker icon just for the last point. [13:24:21] Moreover, in my browser I have this warning message: [13:24:21] As of February 21st, 2024, google.maps.Marker is deprecated. Please use google.maps.marker.AdvancedMarkerElement instead. At this time, google.maps.Marker is not scheduled to be discontinued, but google.maps.marker.AdvancedMarkerElement is recommended over google.maps.Marker. While google.maps.Marker will continue to receive bug fixes for any major [13:24:22] regressions, existing bugs in google.maps.Marker will not be addressed. At least 12 months notice will be given before support is discontinued. Please see https://developers.google.com/maps/deprecations for additional details and https://developers.google.com/maps/documentation/javascript/advanced-markers/migration for the migration guide. [13:24:22] Please have you any idea about this issue? [13:25:06] This is the wrong channel to be asking about general MediaWiki questions. You're also using a long unsupported version of MediaWiki, so chances are you're not using an up to date version of the relevant extensions either [13:31:28] [[Tech]]; ~2025-39341-62; /* MediaWiki Display Points */ new section; https://meta.wikimedia.org/w/index.php?diff=29769183&oldid=29768038&rcid=37749430 [13:32:32] Alaa: Posting on that Tech page ^ isn't the right place either [13:34:37] Ok, thank youvery much for your answer! Where I can ask then? [13:36:35] https://www.mediawiki.org/wiki/Extension:Maps probably is a good starting point, but like I say, you're using an ancient version of MediaWiki (which should be upgraded), and therefore you're probably also using an ancient version of the Maps extension... and a newer version probably already has this issue fixed [13:38:12] Ok, thanks! [13:41:06] A_smart_kitten: while it’s technically possible, I would say it’s discouraged to have changes depend on each other like that [13:41:31] I see that ability as an optimization, useful for cases where people have added nine changes to a single window *looks disapprovingly at the upcoming window* [13:41:54] but changes should still be organized so they can be deployed and reverted separately as much as possible [13:42:25] looking at this change, IIUC the config change could Depend(s)-On the MediaWiki change? [13:42:47] or would deploying the MediaWiki change without the config change also cause unexpected changes in the effective config? [13:43:30] Lucas_WMDE: yeah, in the case i'm looking at (that was the basis for my question), the MW change on its own could cause changes in effective config. [13:44:10] so to maintain the status quo at all times, AFAICS there'd either have to be two config changes (one deployed prior to the MW change & one deployed after it), or they'd both have to be deployed together [13:44:51] (re this window... sorry!! i can reschedule mine if you want. though the SVG patch is a no-op and can be bundled with other low-risk changes imo) [13:46:09] s/could cause changes/would cause changes/ [14:25:54] hi