I'm a Steward and Technical Contributor for the Miraheze project and float around other parts of the wider MediaWiki ecosystem, and a techy sometimes Wikimedian.
See my Miraheze Meta user page.
I'm a Steward and Technical Contributor for the Miraheze project and float around other parts of the wider MediaWiki ecosystem, and a techy sometimes Wikimedian.
See my Miraheze Meta user page.
Getting both more information and more confused. I can't for the life of me find any info on what tags/platforms the WM containers support on docker-registry.wm.o, but the other images that complain seem to have arm builds in different layers. Trying to poke with different DOCKER_DEFAULT_PLATFORMs is driving me slightly insane so I may revisit this later. If there's a way to manually override the image for a specific container in mwcli, that would probably help a lot. I am not very experienced in this area of dev so it's also possible I'm getting in too deep under my head and all crossed, in which case feel free to trout me.
https://hub.docker.com/layers/defreitas/dns-proxy-server/5.9.0-aarch64/images/sha256-acf17e8354cfcc6e99b66c740a3c5a6275e9ec29c9047460550b5bd69445463c
https://hub.docker.com/layers/library/golang/1.23-alpine3.22/images/sha256-56e44a486dc12270a471259239c0005ae492be2f078c4f54567c0e3159e23e4b
Should have checked the actual Docker Desktop menu earlier, since it does probably explain both why Windows works and why it works bad. The three grumpy containers have warnings next to them flagging that they're AMD, and seemingly implying they're being run by emulation (though I've found painfully little information on how this works). I'm not sure yet why running Docker on WSL directly apparently didn't try to or failed to emulate it, but looking into it. Given that using emulation hits with a 10x slowdown though, I think the best way to resolve this would be to try and update the upstream Wikimedia and dns containers to be built with an ARM supporting version, which, shouldn't be too hard, right(???)
defreitas/dns-proxy-server already has a 'snapshot' version targeted for linux/arm64, as for Wikimedia, I don't know how or who maintains their docker registry so I don't really know where to start.
The volumes bug was easy enough to debug, just needed to manually mw dev env set it. Running the Windows binary gives the following.
PS C:\Users\User\Downloads> .\mw_202608-arm_windows_amd64.exe dev mediawiki create -v [+] up 62/63 [+] up 63/64. Pulled 36.0s [+] up 63/64. Pulled 36.0s [+] up 66/67. Pulled 36.0s ✔ Image d... Pulled 36.0s [+] up 66/67. Pulled 16.1s ✔ Image d... Pulled 36.0s [+] up 67/68. Pulled 16.1s ✔ Image d... Pulled 36.0s ✔ Image d... Pulled 16.1s [I removed a lot of these to save space, nothing interesting in here] [+] up 68/68. Pulled 19.5s ✔ Image d... Pulled 36.0s ✔ Image d... Pulled 16.1s ✔ Image j... Pulled 19.5s ✔ Image g... Pulled 33.5s ✔ Image d... Pulled 39.4s ✔ Network... Created 0.1s ✔ Volume ... Created 0.0s ✔ Volume ... Created 0.1s ✔ Volume ... Created 0.0s ✔ Contain... Started 2.3s ! dps The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested 0.0s✔ Contain... Started 8.5s ✔ Contain... Started 1.3s ✔ Contain... Started 7.2s ✔ Contain... Started 8.5s ! mediawi... The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested 0.0s ✔ Contain... Started 9.1s ! mediawiki The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested 0.0s PS C:\Users\User\Downloads>
Directly after installing the mw_202608-arm_linux_arm64 binary:
pixldev@LAPTOP-AR6JANU0:~$ mw dev mediawiki create [+] up 6/7 ✔ Network mwcli-... Created 0.1s ✔ Volume mwcli-m... Created 0.0s ✔ Volume mwcli-m... Created 0.0s ✔ Volume mwcli-m... Created 0.0s ✔ Container mwcl... Created 0.2s ⠋ Container mwcl... Creating 0.0s ✘ service:dashbo... Error response from daemon: image with reference golang:1.23-alpine was found but does not provide the specified platform (linux/amd64) 0.0s Error response from daemon: image with reference golang:1.23-alpine was found but does not provide the specified platform (linux/amd64) ERROR exit status 1
Every bit of extra arm info and experience will likely help!
Alright! Let me know if there's any other tests you'd like me to run (for this task or any others, I'm on the MW discord if it's a matter without a Phab task) and I'll send over the results if able.
Not sure if this helps at all, but I tried specifically running the creation commands with the default platform variable shoved in, and it seemed to be picked up but still causes complaints.
pixldev@LAPTOP-AR6JANU0:~$ DOCKER_DEFAULT_PLATFORM=linux/amd64 mw dev mediawiki create [+] up 6/8 ✔ Volume mwcli-m... Created 0.0s ✔ Volume mwcli-m... Created 0.1s ✔ Volume mwcli-m... Created 0.0s ✔ Network mwcli-... Created 0.1s ✔ Container mwcl... Created 0.2s ⠋ Container mwcl... Creating 0.0s ✘ service:dashbo... Error response from daemon: image with reference golang:1.23-alpine was found but does not provide the specified platform (linux/amd64) 0.0s ⠋ Container mwcl... Creating 0.0s Error response from daemon: image with reference golang:1.23-alpine was found but does not provide the specified platform (linux/amd64) ERROR exit status 1 pixldev@LAPTOP-AR6JANU0:~$ mw dev destroy [+] down 5/5 ✔ Container mwcli-mwdd-default-dps-1 Removed 0.0s ✔ Volume mwcli-mwdd-default_mediawiki-data Removed 0.0s ✔ Network mwcli-mwdd-default_dps Removed 0.1s ✔ Volume mwcli-mwdd-default_mediawiki-logs Removed 0.0s ✔ Volume mwcli-mwdd-default_mediawiki-images Removed 0.0s pixldev@LAPTOP-AR6JANU0:~$ DOCKER_DEFAULT_PLATFORM=linux/arm64 mw dev mediawiki create [+] up 5/7 ✔ Network... Created 0.0s ✔ Volume ... Created 0.0s ✔ Volume ... Created 0.0s ✔ Volume ... Created 0.0s ⠋ Contain... Creating 0.0s ✘ service... Error response from daemon: image with reference defreitas/dns-proxy-server:5.9.0 was found but does not provide the specified platform (linux/arm64) 0.0s ⠋ Contain... Creating 0.0s Error response from daemon: image with reference defreitas/dns-proxy-server:5.9.0 was found but does not provide the specified platform (linux/arm64) ERROR exit status 1
The linked artifact didn't seem to compile to arm, since I got an exec file format error when trying to run it (same issue as when I was directly following the install instructions instead of downloading the specific linux arm build.
Also, this is seemingly an issue for another task but I'll just mention that using mw update --version=<url> gave a ERROR could not move new binary to location: open /usr/local/bin/mw: text file busy. I would suspect that the program doesn't like to delete itself while it's still running.
Marking as assigned to David since he was the one who added the floating IP (title of the task)
(Just as an extra note, mailcow’s default logo branding is still present on dark mode, only light mode is using the Wikimedia logo. Not relevant to the task itself but I don’t believe there’s a more specific task on this)
If using the same config, we would need to disallow global and local groups having the same name
This probably best avoided, quickly looking at Wikimedia Meta, this would at the least require the steward global or local group to be renamed, which may cause more headaches for updating things that rely on the group name (don't have an example on hand but I would not be shocked if some existing bots or tools check if a user is a steward by group name. Off Wikimedia, the Miraheze project also has at least 4 groups that have a local and global group of the same name. Making a slightly modifed version of the existing config seems to be the least bothersome option overall.
At least sometimes, no wiki accounts mentioned there would be created
Seems in both your example and mine, Alice, Bob and Mallory are created indeed, but I don’t think any of them use the password(haven’t thoroughly tested)
Seems to be fine -some 5 years later-.
In T383466#10450797, @MBH wrote:As far as I understand,
- an admin enters "Москва" into text field in the blocking interface. Block doesn't work.
- an admin enters "москва" into text field in the blocking interface. Block works.
Gave this a try on another mediawiki instance, failed to reproduce. See https://publictestwiki.com/wiki/Special:Log?logid=38189. Maybe an issue on the alpha version of MW that Wikimedia is on?
In T383466#10450473, @MBH wrote:Cyrillic. Capital-first-letter is enabled, I think, in all wikipedias (and definitely enabled in Russian).
Is this using the standard Latin alphabet or using uppercase in the Russian alphabet? Also, does ruwiki have the setting to always capitalize page names on? Capital titles is the default so partial blocks not working on capitalized doesn't make sense.
In T345477#10305980, @SomeRandomDeveloper wrote:Should this be a magic word? Another thing to consider would be to show these stats on Special:Statistics, like Semantic MediaWiki does.
@Pppery if we move the m: messages to a Wikimedia specific collection, what would we make the default message. Would we have a link at all?
In T383362#10446516, @Tgr wrote:Should be straightforward technically via the LinkerMakeExternalLink hook, but yes it would raise all kinds of SEO and usability and tool B/C issues, and on Wikimedia sites it would increase the amount of user tracking (currently we don't learn about a user clicking a link, I think it would be hard to avoid that data getting at least into the webrequest table).
In T383362#10446414, @Izno wrote:I can only assume there was another event that caused this task since this is the second similar item showing up in my inbox today, please consider connecting that if it's not already connected.
Yeeeaaah, I’m going to get a gander and point at… this
In T381138#10446364, @bd808 wrote:Tool was archived by its prior maintainer.
In T378901#10289683, @Himacharanbatchu wrote:Thanks @taavi for the nice observations you made, I'll fix this :)
In T381138#10369300, @JJMC89 wrote:FYI, there is nothing useful remaining in the tool's directory - any files to run the tool were removed prior to disabling. Other than the URL, there would be no difference to creating a new tool. (Anything that links to it can be updated.)
Hm, it is possible/worth it/has precedent to set a domain redirect to wherever the new version of the tool is hosted to minimize confusion?
(my 2c) I agree this should be changed for clarity, but given that the only people who would encounter this should be users who are experienced in its functions and read up on how it works, having a confirmation for changing the publicity of a Filter probably isn't needed.
Reported in https://issue-tracker.miraheze.org/T12766
I don't have the ability to do so, but can someone move this to the deployment requests column of Automoderator, please?
Fix merged, should work now but I'm not familiar with the CI system so if someone who knows how to use it and verify the issue is solved, feel free to close this!
Got a seemingly working one line fix, I’m going to test it a bit more and reformat, then see about merging it(great now I have to learn how to use gerrit)
(Miraheze Volunteer, Non-SRE) if this relys on the Job Queue it makes sense it's not functioning, Miraheze is recently moved it's jobrunner to Kafka from Redis and it's causing a few issue we are still working out(ie delayed notification) I'll see if there's anything we can do if we have time. Thanks Ciencia for pointing that out