Re: [Wikitech-l] [Engineering] Phabricator spam - account approval requirement enabled
> Yes, though careful because CommunityTechBot shows up as a subscriber to
lots of tasks now which are getting comments from other people, so it
appears on the Cc list at the bottom of each email notification.
Oh, oops :/ I think I can automate removing the bot as a subscriber? Will
look into that later.
~Leon
On Mon, Jul 2, 2018 at 2:08 PM Alex Monk wrote:
> Yes, though careful because CommunityTechBot shows up as a subscriber to
> lots of tasks now which are getting comments from other people, so it
> appears on the Cc list at the bottom of each email notification.
>
> On 2 July 2018 at 19:06, Ed Sanders wrote:
>
>> +100
>>
>> Also a tip for those of you wanting to clear up the resulting email spam:
>> you can temporarily turn off "conversation mode" in Gmail's settings, then
>> search for messages from CommunityTechBot or the spammer, and delete all
>> these emails without having to delete the threads they belong too.
>>
>> On Mon, 2 Jul 2018 at 18:18, Joel Aufrecht
>> wrote:
>>
>>> Thank you Leon for this heroic effort, and thanks to everyone who helped
>>> in this cleanup.
>>>
>>> On Mon, Jul 2, 2018, 9:58 AM Leon Ziemba
>>> wrote:
>>>
The bot has now completed it's run. If you see any outstanding tasks
that need to be repaired, please give me the task IDs.
The bot ran for roughly 36 hours, repairing at least 4,000 tasks
(perhaps many more).
There were some issues with the bot that may still affect your tasks:
* The triage level was not restored, or was put in "Needs triage". This
was fixed around 16:00 UTC on July 1. Hundreds of tasks were affected.
* For most of the bot's run, it was subject to a newly imposed rate
limiting. If the rate limit was hit in the middle of repairing a task, the
bot may not have fixed everything. Many tasks were affected. This issue was
fixed around 15:00 UTC on July 1.
* For some tasks, the vandal removed tags as well adding some. The bot
did not properly restore the removed tags until around 12:00 UTC on July 2.
The number of tasks affected by this is estimated to be low.
* Some tasks have "custom fields" that were vandalized, which the bot
did not restore. An example is the "due date" on
https://phabricator.wikimedia.org/T193593. The number of tasks
affected by this should be very low.
If you notice any tasks where the bot didn't fix everything, and you
don't want to fix it yourself, just give me the task IDs and I can re-run
the bot on those.
Thanks to Andre, Mukunda, and everyone else to helped with this effort.
~Leon
On Sun, Jul 1, 2018 at 8:49 PM Mukunda Modell
wrote:
> Hi Leon. I can't thank you enough for your efforts to help clean
> things up in Phabricator. I can, however, help make the bot more
> effective. See below for responses inline.
>
> On Sun, Jul 1, 2018 at 10:47 AM Leon Ziemba
> wrote:
>
>> An update... the bot went to sleep as instructed a few hours after I
>> went to sleep. Bot is now back up and running, with some ~4,500 tasks
>> still
>> to fix.
>>
>> A few problems:
>> * The new "rate limiting" of the API is rather rigorous. Release
>> engineering tried to whitelist the bot but we had no luck. So, it will
>> take
>> some time to go through everything.
>>
>
> I'm still looking into why the bot hits the rate limit. I'm sure I can
> come up with a way to get it whitelisted.
>
>
>> * If the bot hits the rate limit while editing a task, all other
>> changes it was going to make to that task didn't happen. Hence you may
>> see
>> only some corrections on some tasks.
>> * The priority level is now being set to "Needs triage". This is
>> because the Conduit API gives me numbers for the priority level, and the
>> edit API wants a string (?!?). I don't know what numbers are for what
>> priorities, so "Needs triage" it is. Older versions of the script left
>> the
>> priority level unchanged, so either way you may wish to review the
>> priorities of your tasks. If you know what the priority number to string
>> mapping is, please tell me :)
>>
>>
> If you would like to alter the bot to restore the correct priority,
> this should help; The priority levels are configured as follows:
>
> {
> "10": {
> "color": "sky",
> "keywords": [
> "lowest"
> ],
> "name": "Lowest",
> "short": "Lowest"
> },
> "25": {
> "color": "yellow",
> "keywords": [
> "low"
> ],
> "name": "Low",
> "short": "Low"
> },
> "50": {
> "color": "orange",
> "keywords": [
> "normal"
> ],
> "name": "Normal",
> "short": "Normal"
> },
> "80": {
> "color": "red",
>
[Wikitech-l] Additional European-appropriate MediaWiki train window starting week of July 9th (also SWAT change)
Hello, The Release Engineering team will be expanding the set of people responsible for the weekly MediaWiki train deployments[0] to include people working normal European hours. Unfortunately, the current MW train deployment window is too late in the day for them. To address this we are adding a European-focused timeslot for the MW train (and moving the current "EU SWAT window" 2 hours earlier to accommodate). The first planned use of the new window will be next week, the week of July 9th. For the avoidance of doubt: the normal MW train windows will not go away, these EU-timezone ones are in addition to them and only used during weeks that the train is conducted by someone in Europe. But, the EU SWAT window will indeed be permanently moved for simplicity (IOW: not dependent upon who's doing the train). == European train window and changes == This would affect Tuesday, Wednesday, and Thursday * 1300-1400 CEST (1100-1200 UTC) - EU SWAT window (2 hours earlier) * 1400-1500 CEST (1200-1300 UTC) - Break * 1500-1700 CEST (1300-1500 UTC) - EU Train window * 1700-1800 CEST (1500-1600 UTC) - Break * 1800-1900 CEST (1600-1700 UTC) - PuppetSWAT (Tue/Thu only, no change) Also, at the same time we'll be moving the Wednesday morning (SF time) SWAT window on hour earlier to 9am Pacific. This is to alleviate a contention with the weekly Scrum of Scrums meeting. Best, Greg [0] https://www.mediawiki.org/wiki/MediaWiki_1.32/Roadmap -- | Greg GrossmeierGPG: B2FA 27B1 F7EB D327 6B8E | | Release Team ManagerA18D 1138 8E47 FAC8 1C7D | signature.asc Description: PGP signature ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] [Engineering] Phabricator spam - account approval requirement enabled
Yes, though careful because CommunityTechBot shows up as a subscriber to
lots of tasks now which are getting comments from other people, so it
appears on the Cc list at the bottom of each email notification.
On 2 July 2018 at 19:06, Ed Sanders wrote:
> +100
>
> Also a tip for those of you wanting to clear up the resulting email spam:
> you can temporarily turn off "conversation mode" in Gmail's settings, then
> search for messages from CommunityTechBot or the spammer, and delete all
> these emails without having to delete the threads they belong too.
>
> On Mon, 2 Jul 2018 at 18:18, Joel Aufrecht
> wrote:
>
>> Thank you Leon for this heroic effort, and thanks to everyone who helped
>> in this cleanup.
>>
>> On Mon, Jul 2, 2018, 9:58 AM Leon Ziemba
>> wrote:
>>
>>> The bot has now completed it's run. If you see any outstanding tasks
>>> that need to be repaired, please give me the task IDs.
>>>
>>> The bot ran for roughly 36 hours, repairing at least 4,000 tasks
>>> (perhaps many more).
>>>
>>> There were some issues with the bot that may still affect your tasks:
>>> * The triage level was not restored, or was put in "Needs triage". This
>>> was fixed around 16:00 UTC on July 1. Hundreds of tasks were affected.
>>> * For most of the bot's run, it was subject to a newly imposed rate
>>> limiting. If the rate limit was hit in the middle of repairing a task, the
>>> bot may not have fixed everything. Many tasks were affected. This issue was
>>> fixed around 15:00 UTC on July 1.
>>> * For some tasks, the vandal removed tags as well adding some. The bot
>>> did not properly restore the removed tags until around 12:00 UTC on July 2.
>>> The number of tasks affected by this is estimated to be low.
>>> * Some tasks have "custom fields" that were vandalized, which the bot
>>> did not restore. An example is the "due date" on
>>> https://phabricator.wikimedia.org/T193593. The number of tasks affected
>>> by this should be very low.
>>>
>>> If you notice any tasks where the bot didn't fix everything, and you
>>> don't want to fix it yourself, just give me the task IDs and I can re-run
>>> the bot on those.
>>>
>>> Thanks to Andre, Mukunda, and everyone else to helped with this effort.
>>>
>>> ~Leon
>>>
>>> On Sun, Jul 1, 2018 at 8:49 PM Mukunda Modell
>>> wrote:
>>>
Hi Leon. I can't thank you enough for your efforts to help clean things
up in Phabricator. I can, however, help make the bot more effective. See
below for responses inline.
On Sun, Jul 1, 2018 at 10:47 AM Leon Ziemba
wrote:
> An update... the bot went to sleep as instructed a few hours after I
> went to sleep. Bot is now back up and running, with some ~4,500 tasks
> still
> to fix.
>
> A few problems:
> * The new "rate limiting" of the API is rather rigorous. Release
> engineering tried to whitelist the bot but we had no luck. So, it will
> take
> some time to go through everything.
>
I'm still looking into why the bot hits the rate limit. I'm sure I can
come up with a way to get it whitelisted.
> * If the bot hits the rate limit while editing a task, all other
> changes it was going to make to that task didn't happen. Hence you may see
> only some corrections on some tasks.
> * The priority level is now being set to "Needs triage". This is
> because the Conduit API gives me numbers for the priority level, and the
> edit API wants a string (?!?). I don't know what numbers are for what
> priorities, so "Needs triage" it is. Older versions of the script left the
> priority level unchanged, so either way you may wish to review the
> priorities of your tasks. If you know what the priority number to string
> mapping is, please tell me :)
>
>
If you would like to alter the bot to restore the correct priority,
this should help; The priority levels are configured as follows:
{
"10": {
"color": "sky",
"keywords": [
"lowest"
],
"name": "Lowest",
"short": "Lowest"
},
"25": {
"color": "yellow",
"keywords": [
"low"
],
"name": "Low",
"short": "Low"
},
"50": {
"color": "orange",
"keywords": [
"normal"
],
"name": "Normal",
"short": "Normal"
},
"80": {
"color": "red",
"keywords": [
"high"
],
"name": "High",
"short": "High"
},
"90": {
"color": "violet",
"keywords": [
"triage"
],
"name": "Needs Triage",
"short": "Triage"
},
"100": {
"color": "pink",
"keywords": [
"unbreak"
],
"name": "Unbreak Now!",
"short": "Unbreak!"
}
}
Cheers,
>
> ~Leon
>
>
Re: [Wikitech-l] [Engineering] Phabricator spam - account approval requirement enabled
+100
Also a tip for those of you wanting to clear up the resulting email spam:
you can temporarily turn off "conversation mode" in Gmail's settings, then
search for messages from CommunityTechBot or the spammer, and delete all
these emails without having to delete the threads they belong too.
On Mon, 2 Jul 2018 at 18:18, Joel Aufrecht wrote:
> Thank you Leon for this heroic effort, and thanks to everyone who helped
> in this cleanup.
>
> On Mon, Jul 2, 2018, 9:58 AM Leon Ziemba
> wrote:
>
>> The bot has now completed it's run. If you see any outstanding tasks that
>> need to be repaired, please give me the task IDs.
>>
>> The bot ran for roughly 36 hours, repairing at least 4,000 tasks (perhaps
>> many more).
>>
>> There were some issues with the bot that may still affect your tasks:
>> * The triage level was not restored, or was put in "Needs triage". This
>> was fixed around 16:00 UTC on July 1. Hundreds of tasks were affected.
>> * For most of the bot's run, it was subject to a newly imposed rate
>> limiting. If the rate limit was hit in the middle of repairing a task, the
>> bot may not have fixed everything. Many tasks were affected. This issue was
>> fixed around 15:00 UTC on July 1.
>> * For some tasks, the vandal removed tags as well adding some. The bot
>> did not properly restore the removed tags until around 12:00 UTC on July 2.
>> The number of tasks affected by this is estimated to be low.
>> * Some tasks have "custom fields" that were vandalized, which the bot did
>> not restore. An example is the "due date" on
>> https://phabricator.wikimedia.org/T193593. The number of tasks affected
>> by this should be very low.
>>
>> If you notice any tasks where the bot didn't fix everything, and you
>> don't want to fix it yourself, just give me the task IDs and I can re-run
>> the bot on those.
>>
>> Thanks to Andre, Mukunda, and everyone else to helped with this effort.
>>
>> ~Leon
>>
>> On Sun, Jul 1, 2018 at 8:49 PM Mukunda Modell
>> wrote:
>>
>>> Hi Leon. I can't thank you enough for your efforts to help clean things
>>> up in Phabricator. I can, however, help make the bot more effective. See
>>> below for responses inline.
>>>
>>> On Sun, Jul 1, 2018 at 10:47 AM Leon Ziemba
>>> wrote:
>>>
An update... the bot went to sleep as instructed a few hours after I
went to sleep. Bot is now back up and running, with some ~4,500 tasks still
to fix.
A few problems:
* The new "rate limiting" of the API is rather rigorous. Release
engineering tried to whitelist the bot but we had no luck. So, it will take
some time to go through everything.
>>>
>>> I'm still looking into why the bot hits the rate limit. I'm sure I can
>>> come up with a way to get it whitelisted.
>>>
>>>
* If the bot hits the rate limit while editing a task, all other
changes it was going to make to that task didn't happen. Hence you may see
only some corrections on some tasks.
* The priority level is now being set to "Needs triage". This is
because the Conduit API gives me numbers for the priority level, and the
edit API wants a string (?!?). I don't know what numbers are for what
priorities, so "Needs triage" it is. Older versions of the script left the
priority level unchanged, so either way you may wish to review the
priorities of your tasks. If you know what the priority number to string
mapping is, please tell me :)
>>> If you would like to alter the bot to restore the correct priority, this
>>> should help; The priority levels are configured as follows:
>>>
>>> {
>>> "10": {
>>> "color": "sky",
>>> "keywords": [
>>> "lowest"
>>> ],
>>> "name": "Lowest",
>>> "short": "Lowest"
>>> },
>>> "25": {
>>> "color": "yellow",
>>> "keywords": [
>>> "low"
>>> ],
>>> "name": "Low",
>>> "short": "Low"
>>> },
>>> "50": {
>>> "color": "orange",
>>> "keywords": [
>>> "normal"
>>> ],
>>> "name": "Normal",
>>> "short": "Normal"
>>> },
>>> "80": {
>>> "color": "red",
>>> "keywords": [
>>> "high"
>>> ],
>>> "name": "High",
>>> "short": "High"
>>> },
>>> "90": {
>>> "color": "violet",
>>> "keywords": [
>>> "triage"
>>> ],
>>> "name": "Needs Triage",
>>> "short": "Triage"
>>> },
>>> "100": {
>>> "color": "pink",
>>> "keywords": [
>>> "unbreak"
>>> ],
>>> "name": "Unbreak Now!",
>>> "short": "Unbreak!"
>>> }
>>> }
>>>
>>>
>>>
>>> Cheers,
~Leon
On Sun, Jul 1, 2018 at 5:32 AM Max Semenik
wrote:
> We've got ourselves da MVP!
>
> On Sun, Jul 1, 2018 at 12:51 AM, Leon Ziemba <
> musikani...@wikimedia.org>
> wrote:
>
> > I wrote a rollback script, currently running as CommunityTechBot
> >
Re: [Wikitech-l] [Engineering] Phabricator spam - account approval requirement enabled
Thank you Leon for this heroic effort, and thanks to everyone who helped in
this cleanup.
On Mon, Jul 2, 2018, 9:58 AM Leon Ziemba wrote:
> The bot has now completed it's run. If you see any outstanding tasks that
> need to be repaired, please give me the task IDs.
>
> The bot ran for roughly 36 hours, repairing at least 4,000 tasks (perhaps
> many more).
>
> There were some issues with the bot that may still affect your tasks:
> * The triage level was not restored, or was put in "Needs triage". This
> was fixed around 16:00 UTC on July 1. Hundreds of tasks were affected.
> * For most of the bot's run, it was subject to a newly imposed rate
> limiting. If the rate limit was hit in the middle of repairing a task, the
> bot may not have fixed everything. Many tasks were affected. This issue was
> fixed around 15:00 UTC on July 1.
> * For some tasks, the vandal removed tags as well adding some. The bot did
> not properly restore the removed tags until around 12:00 UTC on July 2. The
> number of tasks affected by this is estimated to be low.
> * Some tasks have "custom fields" that were vandalized, which the bot did
> not restore. An example is the "due date" on
> https://phabricator.wikimedia.org/T193593. The number of tasks affected
> by this should be very low.
>
> If you notice any tasks where the bot didn't fix everything, and you don't
> want to fix it yourself, just give me the task IDs and I can re-run the bot
> on those.
>
> Thanks to Andre, Mukunda, and everyone else to helped with this effort.
>
> ~Leon
>
> On Sun, Jul 1, 2018 at 8:49 PM Mukunda Modell
> wrote:
>
>> Hi Leon. I can't thank you enough for your efforts to help clean things
>> up in Phabricator. I can, however, help make the bot more effective. See
>> below for responses inline.
>>
>> On Sun, Jul 1, 2018 at 10:47 AM Leon Ziemba
>> wrote:
>>
>>> An update... the bot went to sleep as instructed a few hours after I
>>> went to sleep. Bot is now back up and running, with some ~4,500 tasks still
>>> to fix.
>>>
>>> A few problems:
>>> * The new "rate limiting" of the API is rather rigorous. Release
>>> engineering tried to whitelist the bot but we had no luck. So, it will take
>>> some time to go through everything.
>>>
>>
>> I'm still looking into why the bot hits the rate limit. I'm sure I can
>> come up with a way to get it whitelisted.
>>
>>
>>> * If the bot hits the rate limit while editing a task, all other changes
>>> it was going to make to that task didn't happen. Hence you may see only
>>> some corrections on some tasks.
>>> * The priority level is now being set to "Needs triage". This is because
>>> the Conduit API gives me numbers for the priority level, and the edit API
>>> wants a string (?!?). I don't know what numbers are for what priorities, so
>>> "Needs triage" it is. Older versions of the script left the priority level
>>> unchanged, so either way you may wish to review the priorities of your
>>> tasks. If you know what the priority number to string mapping is, please
>>> tell me :)
>>>
>>>
>> If you would like to alter the bot to restore the correct priority, this
>> should help; The priority levels are configured as follows:
>>
>> {
>> "10": {
>> "color": "sky",
>> "keywords": [
>> "lowest"
>> ],
>> "name": "Lowest",
>> "short": "Lowest"
>> },
>> "25": {
>> "color": "yellow",
>> "keywords": [
>> "low"
>> ],
>> "name": "Low",
>> "short": "Low"
>> },
>> "50": {
>> "color": "orange",
>> "keywords": [
>> "normal"
>> ],
>> "name": "Normal",
>> "short": "Normal"
>> },
>> "80": {
>> "color": "red",
>> "keywords": [
>> "high"
>> ],
>> "name": "High",
>> "short": "High"
>> },
>> "90": {
>> "color": "violet",
>> "keywords": [
>> "triage"
>> ],
>> "name": "Needs Triage",
>> "short": "Triage"
>> },
>> "100": {
>> "color": "pink",
>> "keywords": [
>> "unbreak"
>> ],
>> "name": "Unbreak Now!",
>> "short": "Unbreak!"
>> }
>> }
>>
>>
>>
>> Cheers,
>>>
>>> ~Leon
>>>
>>> On Sun, Jul 1, 2018 at 5:32 AM Max Semenik
>>> wrote:
>>>
We've got ourselves da MVP!
On Sun, Jul 1, 2018 at 12:51 AM, Leon Ziemba >>> >
wrote:
> I wrote a rollback script, currently running as CommunityTechBot
>
Re: [Wikitech-l] [Engineering] Phabricator spam - account approval requirement enabled
The bot has now completed it's run. If you see any outstanding tasks that
need to be repaired, please give me the task IDs.
The bot ran for roughly 36 hours, repairing at least 4,000 tasks (perhaps
many more).
There were some issues with the bot that may still affect your tasks:
* The triage level was not restored, or was put in "Needs triage". This was
fixed around 16:00 UTC on July 1. Hundreds of tasks were affected.
* For most of the bot's run, it was subject to a newly imposed rate
limiting. If the rate limit was hit in the middle of repairing a task, the
bot may not have fixed everything. Many tasks were affected. This issue was
fixed around 15:00 UTC on July 1.
* For some tasks, the vandal removed tags as well adding some. The bot did
not properly restore the removed tags until around 12:00 UTC on July 2. The
number of tasks affected by this is estimated to be low.
* Some tasks have "custom fields" that were vandalized, which the bot did
not restore. An example is the "due date" on
https://phabricator.wikimedia.org/T193593. The number of tasks affected by
this should be very low.
If you notice any tasks where the bot didn't fix everything, and you don't
want to fix it yourself, just give me the task IDs and I can re-run the bot
on those.
Thanks to Andre, Mukunda, and everyone else to helped with this effort.
~Leon
On Sun, Jul 1, 2018 at 8:49 PM Mukunda Modell wrote:
> Hi Leon. I can't thank you enough for your efforts to help clean things up
> in Phabricator. I can, however, help make the bot more effective. See
> below for responses inline.
>
> On Sun, Jul 1, 2018 at 10:47 AM Leon Ziemba
> wrote:
>
>> An update... the bot went to sleep as instructed a few hours after I went
>> to sleep. Bot is now back up and running, with some ~4,500 tasks still to
>> fix.
>>
>> A few problems:
>> * The new "rate limiting" of the API is rather rigorous. Release
>> engineering tried to whitelist the bot but we had no luck. So, it will take
>> some time to go through everything.
>>
>
> I'm still looking into why the bot hits the rate limit. I'm sure I can
> come up with a way to get it whitelisted.
>
>
>> * If the bot hits the rate limit while editing a task, all other changes
>> it was going to make to that task didn't happen. Hence you may see only
>> some corrections on some tasks.
>> * The priority level is now being set to "Needs triage". This is because
>> the Conduit API gives me numbers for the priority level, and the edit API
>> wants a string (?!?). I don't know what numbers are for what priorities, so
>> "Needs triage" it is. Older versions of the script left the priority level
>> unchanged, so either way you may wish to review the priorities of your
>> tasks. If you know what the priority number to string mapping is, please
>> tell me :)
>>
>>
> If you would like to alter the bot to restore the correct priority, this
> should help; The priority levels are configured as follows:
>
> {
> "10": {
> "color": "sky",
> "keywords": [
> "lowest"
> ],
> "name": "Lowest",
> "short": "Lowest"
> },
> "25": {
> "color": "yellow",
> "keywords": [
> "low"
> ],
> "name": "Low",
> "short": "Low"
> },
> "50": {
> "color": "orange",
> "keywords": [
> "normal"
> ],
> "name": "Normal",
> "short": "Normal"
> },
> "80": {
> "color": "red",
> "keywords": [
> "high"
> ],
> "name": "High",
> "short": "High"
> },
> "90": {
> "color": "violet",
> "keywords": [
> "triage"
> ],
> "name": "Needs Triage",
> "short": "Triage"
> },
> "100": {
> "color": "pink",
> "keywords": [
> "unbreak"
> ],
> "name": "Unbreak Now!",
> "short": "Unbreak!"
> }
> }
>
>
>
> Cheers,
>>
>> ~Leon
>>
>> On Sun, Jul 1, 2018 at 5:32 AM Max Semenik wrote:
>>
>>> We've got ourselves da MVP!
>>>
>>> On Sun, Jul 1, 2018 at 12:51 AM, Leon Ziemba
>>> wrote:
>>>
>>> > I wrote a rollback script, currently running as CommunityTechBot
>>> >
