[11:45:06] rate limit [11:48:38] hello! for the first time in a course with students, I had a rate limit message for students. They are only 20 and they were doing 1-2 edits per person in around half an hour. What could we do if this happens again? Thanks [11:53:11] Just saw this oh well, DM him already hello was to draw his attention. (re @malyacko: https://nohello.net/ :)) [12:25:45] His, and >700 people who got a notification of a new message in this group :) (re @gbemiesho: Just saw this oh well, DM him already hello was to draw his attention.) [12:26:20] Oh okay [12:44:38] Depends on the exact error message. Could be https://meta.m.wikimedia.org/wiki/Mass_account_creation#Requesting_temporary_lift_of_IP_cap (re @Galder: hello! for the first time in a course with students, I had a rate limit message for students. They are only 20 and they were doi...) [17:16:56] I'm trying to send a patch to the labs/tools/Isa repository on Gerrit. I make lots of patches, and I usually don't have issues, but I can't submit this one. Here's what happens: [17:17:49] To ssh://gerrit.wikimedia.org:29418/labs/tools/Isa.git ! [remote rejected] HEAD -> refs/for/master%topic=T357422 (branch master not found) error: failed to push some refs to 'ssh://gerrit.wikimedia.org:29418/labs/tools/Isa.git' [17:18:20] Perhaps it's because I usually push to "master", but in this repo it's called "main", but I don't know how to change it. [17:21:56] What are you using to submit your patch? Git command line? [17:22:19] git review [17:30:17] "git review main" should work for a one off commit, but, it sounds like defaultbranch needs setting in .gitreview for repos adopting "main" for now, I guess? [17:32:54] The .gitreview for Isa has "track=1" which I thought was the gerrit magic to push back to the same branch the patch was created on locally. I'm not exactly sure what happens there when you are editing on a "working" branch to set the topic or collect related changes. [17:43:41] I'll defer - I don't submit anywhere near enough code to talk from experience. (re @wmtelegram_bot: The .gitreview for Isa has "track=1" which I thought was the gerrit magic to push back to the same branch the patch was ...) [18:11:52] I am indeed using a branch with a different name, as I usually do. But "master" doesn't appear anywhere, except maybe in some of my default git-review settings. But that's not a problem with other repositories that don't use "master" as the default branch name, such as puppet. [18:36:06] Ah, yes, puppet has a defaultbranch set. https://gerrit.wikimedia.org/r/plugins/gitiles/operations/puppet/+/refs/heads/production/.gitreview [18:58:07] Aha! And Isa doesn't have it? [19:08:32] Looks like this solves the problem [19:11:28] There may well be some tracking stuff that helps in this/other repos as well - from what I can tell (from limited git/python in the src and wikitech-l) the track=1 might help sometimes, but, there are instances like detached head or untracked local branches(?) where it doesn't do anything though. [20:58:59] Hi everyone! Language Community Meeting will be held next Wednesday, *February 21st*, from *12:00 to 13:00 (UTC)*. Would you like to share any updates related to language-specific projects you have been working on at this meeting? Or perhaps you'd like to help resolve technical or non-technical challenges in other language projects? Feel free to add items to the agenda document. [20:58:59] [20:59:01] This meeting is for individuals involved in creating content or managing technical aspects across different language communities. This will be a participant-driven meeting, where we collectively discuss specific technical issues related to language wikis and work together to find possible solutions. This could involve anything from fixing a broken template on the Kurdish wiki to [20:59:02] brainstorming ideas for growing content on the Tulu Wiktionary, currently in the Wikimedia Incubator, or celebrating the creation of Fon Wikipedia, to using MinT for content translation. [20:59:04] [20:59:05] @MaryMunyoki and @jhsoby will be facilitating this meeting. [23:00:29] Do you want to share the results of that research somewhere on the relevant talk page? Would be nice to coordinate on where non-scholarship people are staying. (re @siebrand: I have not gotten email. I didn’t request a scholarship. I’ve researched stay options yesterday, or more accurately, Maarten res...) [23:02:32] Telegram moderation is a dumpster fire. If you are getting any kind of error message that's already one of the better outcomes. Often it just pretends the message is sent but doesn't send it. (re @wmtelegram_bot: When Telegram gives that "Sorry, you are currently restricted from posting in this group" it should also include a "Lear...) [23:04:21] As Sam says the wishathon is for the wishlist specifically, but aside from that, the task looks hackathon-sized. (re @Susannaanas: Hiya! I just came up with a wish and I would like to know what it would take to work on it in a wishathon. (expertisewise, how t...) [23:06:48] Nothing concrete yet (re @gtisza: Do you want to share the results of that research somewhere on the relevant talk page? Would be nice to coordinate on where non-...)