In P49617#201236, @TheresNoTime wrote:

Disabling Use Rosetta for x86/amd64 emulation on Apple Silicon resolved the issue

In T126540#4140551, @gerritbot wrote:

Change 328602 had a related patch set uploaded (by Zhuyifei1999; owner: XXN):
[analytics/quarry/web@master] More options for the number of shown rows of resultset.

https://gerrit.wikimedia.org/r/328602

Hey there. Is this functionality still needed?
Also, could someone clarify whether the pull requests should be made to this Github repository or to Gerrit?

@Mrjohncummings, I've run a little batch test today with 5 icons I downloaded from Thenounproject.com some minutes earlier. All the uploads went fine. Still seeing some minor white space but overall the SVG look decent to me: https://commons.wikimedia.org/wiki/Special:ListFiles?limit=20&user=African+Hope

In T189368#6372898, @Mrjohncummings wrote:

Cool, I wonder if this has already been worked out by someone or if there is a bot for it, I assume there are a lot of SVGs uploaded to commons with weird white spaces

Thanks @Tpt, for taking the time to explain this. I created a couple of pages in the Index namespace. However, Special:IndexPages still doesn't return any result, while a general search indicates that there are actually pages in the Index namespace. Should the pages contain special tags or do I need additional settings?

Hello @Tpt, I'd appreciate some guidance to reproduce the screenshot above. I managed to install the ProofRead Page extension as per this guide (https://www.mediawiki.org/wiki/Extension:Proofread_Page) but I can't quite figure out how to obtain the same step as in the description.

In T189368#6344144, @Mrjohncummings wrote:

One note to add about the upload, it would be helpful if the borders around the icons could be consistent so they could be used together, the credit that is included in the file means the border spacing at the bottom at least will be a bit weird if not fixed

In T189368#6344141, @Mrjohncummings wrote:

@samuelguebo this is really great, please let me know where I can help as a non technical person, happy to be a tester

Hey @ashley, thanks for spending some time describing the issue in more detail.
Here's the screenshot I have. From what I can see, the upload frames seem to be partially cut. The upload buttons and other parts of the form do not appear.

@apaskulin, anytime. Glad I could help.

@apaskulin, thanks for elaborating on that. I've added a short sub-section. Let me know if that needs to be expanded or adjusted: https://www.mediawiki.org/wiki/Special:Diff/3997458

Hey @SamanthaNguyen, could you please indicate the steps to reproduce the error? What's the namespace for accessing PictureGame?

Hey @apaskulin. Am I right that what you're requesting is that the documentation be updated, mentioning that that wikidata.org is not fully supported by the REST API? If so, do you mind indicating which documentation you're talking about? Is it a page on mediawiki.org or on wikidata.org?

Quick update: I managed to have a proof-of-concept version that worked locally. I'm in the process of deploying it to ToolForge (https://thenoun-uploader.toolforge.org/).

In T254046#6178319, @RhinosF1 wrote:

We'll need to do a short downtime for this as I'll be touching the database.

Hopefully should take no longer than 30 mins.

kubectl scale --replicas=0 $(deployment.apps/sopel.bot)
kubectl delete pods sopel.bot-<hash>

will stop the bot

kubectl scale --replicas=1 $(deployment.apps/sopel.bot)

will reboot us

I plan to do this on Monday 1st June at 10:00 am UTC+1. Once we restart, there should be NO user impact as we're only touching things that are not needed.

I will announce this tomorrow morning.

In T189368#6144873, @BamLifa wrote:

@samuelguebo: Hi! Thank you so much for the effort to build this tool. However, I tried to check your repo and noticed that there's no test and the current code is not at all ES6+. Would you accept any help?

Thanks.

In T189368#6143046, @Aklapper wrote:

@samuelguebo: Hi! This task has been assigned to you a while ago. Could you maybe share an update? Do you still plan to work on this task, or do you need any help?

If this task has been resolved in the meantime: Please update the task status (via Add Action... → Change Status in the dropdown menu).
If this task is not resolved and only if you do not plan to work on this task anymore: Please consider removing yourself as assignee (via Add Action... → Assign / Claim in the dropdown menu): That would allow others to work on this (in theory), as others won't think that someone is already working on this. Thanks! :)

{{Done}}

Already split into other independent tasks.

Hey @D3r1ck01 and @MarcoAurelio, I think this ticket can be closed, otherwise it may be misleading. What do you think?

I think 100% is the target. Short term goals should be to cover app.py and utils.py at 100% and then move on to the others. Plus, I suppose tests are low-hanging fruits and a good idea could be to keep few of those tests available for newcomers or starters.

Hey, @Aklapper, unless @D3r1ck01 has a different view, I am totally okay with those stats being shared here. Plus, we were hoping to discuss those stats in our public meeting once they would be available.

Hey @Stibba,
You have it all right. For now testGetContributors isn't performing what it's intended, it only test getStatsFromDb. You should alter the method, add what's missing, so that it tests getContributors.

+2. I strongly support this idea. @D3r1ck01 is a community member with a keen interest and dedication in helping other contributors, not to mention is relevant work.

Imported to GCI as https://codein.withgoogle.com/dashboard/tasks/5161263047901184/