I just released a series of new versions. mwtitle 0.2.6, parsoid 0.10.0, wikipedia_prosesize 0.3.0, mwapi 0.7.0, mwapi_responses 0.5.0, mwbot 0.7.0. Enjoy new features!

I am at school this and next weeks, sorry, so I will look into this next Saturday. It would be appreciated if someone else could release it. cc @Legoktm @mirror-kt

https://www.mediawiki.org/w/index.php?title=Mwbot-rs&diff=prev&oldid=7608909

Hi @dcaro, wmgmc_monitoring is okay. Thanks!

I tried to fix it, manually triggered a build for mwbot-rs and mwseaql and it seems that coverage report now works.

I temporarily ignored that test because it is constantly failing: https://gitlab.wikimedia.org/repos/mwbot-rs/mwbot/-/commit/377a605775799f21e2850ec6dbe29f1486a61b7a

The token store also needs to be flushed once api_url is updated.

@taavi thank you! I have updated the task description to a group request.

cargo binstall toolforge, probably. The crate is published on crates.io as toolforge instead of toolforge-tunnel.

Thank all of you for looking into this (:

not completely. after sending the request for more times, the ETag is continuously missing but hit-local seldomly become hit-front (also without etag), however, it will become hit-local again shortly (basically in next request).

What's the difference between hit-local and hit-front?

( Just to record, in my tests, repeating querying one URL made its ETag disappear (:

Have you forked the repository? I couldn't see your fork repository on gitlab.

btw it seems that the GitLab approval request queue is now suspended and requests are not being handled for unknown reasons (:

Making it not dismissable sounds good to me (:

@Nischay3333 https://phabricator.wikimedia.org/maniphest/task/edit/form/117/

Hi. If your gitlab account is already activated, you could first click the fork button and push changes to your fork, then make a merge request to send your code for review. If not, you should follow the banner on gitlab.wikimedia.org to activate it.

You can claim by youself, by clicking the Edit Task on the right of this page, add yourself to "Assignee" and save.

Hi! Thanks for your interest in mwbot-rs.
First of all, to let others know that you are working on this task, you should claim this task, by clicking "Edit Task" at the right of this page, and add yourself to "Assignee".
Then you need to clone the repository (if you does not have a WMF GitLab account, you can clone with HTTP before your account is activated) and make code changes.
The general idea of ​this task has been clearly explained in the description (if you still have other questions, you can ask here or just do as what you think is right).
To submit your code, you will need to request for an account on https://gitlab.wikimedia.org/ first, then make a merge request to https://gitlab.wikimedia.org/repos/mwbot-rs/mwbot .

For your GitLab account, according to the GitLab banner, you may need to fill out [ https://phabricator.wikimedia.org/maniphest/task/edit/form/117/ | this form ] on Phabricator to activate your account.

You should fork the repository and then clone your fork. You may be added a a member of the mwbot-rs org so you can directly clone and push to the mwbot-rs/mwbot repository.

@Priyanshu_Chahal Thanks for your contribution to the mwbot-rs project! Please submit your MR to https://gitlab.wikimedia.org/repos/mwbot-rs/mwbot , where most development of mwbot-rs happens. The old mirror on gitlab.com is outdated.

@Priyanshu_Chahal Hi! You may implement your code in the mwbot crate: https://gitlab.wikimedia.org/repos/mwbot-rs/mwbot/-/tree/main/mwbot.

As in T380675, I created a new rc release for mwbot, which should include the fix.

This is actually fixed by d6a97188f526 ("mwbot: Fix revisions generator"). Please verify if this issue still exists in the latest code.

The example block mentioned above has ID 3260612.
I did a query on Toolforge replica DBs and it seems that the block is for a user but not a IP address/range.