Jira Lock Down Upgraded?

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

Jira Lock Down Upgraded?

Xiao Chen
Hello,

I'm not sure if common-dev is the right contact list, please redirect me if
not.

It seems the jira lock down is somehow being more strict?
I was able to comment on an HDFS jira
<https://issues.apache.org/jira/browse/HDFS-4210?focusedCommentId=15282111&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15282111>
at around 14:45 PDT today, but now I cannot.

The banner still says:

Jira is in Temporary Lockdown mode as a spam countermeasure. Only logged-in
users with active roles (committer, contributor, PMC, etc.) will be able to
create issues or comments during this time. Lockdown period from 11 May
2300 UTC to estimated 12 May 2300 UTC.


But with a quick check with Yongjun and Yufei, contributors are locked down
as well.

Thanks,
-Xiao
Reply | Threaded
Open this post in threaded view
|

Re: Jira Lock Down Upgraded?

Andrew Wang
Try asking on infra.chat (Apache INFRA's hipchat). I was in that room
earlier today, and they were working on the ongoing JIRA spam.

On Thu, May 12, 2016 at 3:03 PM, Xiao Chen <[hidden email]> wrote:

> Hello,
>
> I'm not sure if common-dev is the right contact list, please redirect me if
> not.
>
> It seems the jira lock down is somehow being more strict?
> I was able to comment on an HDFS jira
> <
> https://issues.apache.org/jira/browse/HDFS-4210?focusedCommentId=15282111&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15282111
> >
> at around 14:45 PDT today, but now I cannot.
>
> The banner still says:
>
> Jira is in Temporary Lockdown mode as a spam countermeasure. Only logged-in
> users with active roles (committer, contributor, PMC, etc.) will be able to
> create issues or comments during this time. Lockdown period from 11 May
> 2300 UTC to estimated 12 May 2300 UTC.
>
>
> But with a quick check with Yongjun and Yufei, contributors are locked down
> as well.
>
> Thanks,
> -Xiao
>
Reply | Threaded
Open this post in threaded view
|

Re: Jira Lock Down Upgraded?

Ted Yu-3
Looks like side effects of this lock down are:

1. person (non-admin) who logged JIRA cannot comment on the JIRA
2. result of QA run cannot be posted onto JIRA (at least for hbase tests)

:-(

On Thu, May 12, 2016 at 3:10 PM, Andrew Wang <[hidden email]>
wrote:

> Try asking on infra.chat (Apache INFRA's hipchat). I was in that room
> earlier today, and they were working on the ongoing JIRA spam.
>
> On Thu, May 12, 2016 at 3:03 PM, Xiao Chen <[hidden email]> wrote:
>
> > Hello,
> >
> > I'm not sure if common-dev is the right contact list, please redirect me
> if
> > not.
> >
> > It seems the jira lock down is somehow being more strict?
> > I was able to comment on an HDFS jira
> > <
> >
> https://issues.apache.org/jira/browse/HDFS-4210?focusedCommentId=15282111&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15282111
> > >
> > at around 14:45 PDT today, but now I cannot.
> >
> > The banner still says:
> >
> > Jira is in Temporary Lockdown mode as a spam countermeasure. Only
> logged-in
> > users with active roles (committer, contributor, PMC, etc.) will be able
> to
> > create issues or comments during this time. Lockdown period from 11 May
> > 2300 UTC to estimated 12 May 2300 UTC.
> >
> >
> > But with a quick check with Yongjun and Yufei, contributors are locked
> down
> > as well.
> >
> > Thanks,
> > -Xiao
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: Jira Lock Down Upgraded?

Xiao Chen
FYI - I pinged infra but the answer is only people with
PMC/committer/contributor *Roles* on jira can comment. Hadoop's contributor
list seems to be reached it's limit, so cannot be added.

Hopefully we can restore after said May 12 2300 UTC.

Maybe we should increase the contributor limit or add some kind of
whitelist, so this spam counter measurement doesn't do too much collateral
damage on regular work....

-Xiao

On Thu, May 12, 2016 at 7:46 PM, Ted Yu <[hidden email]> wrote:

> Looks like side effects of this lock down are:
>
> 1. person (non-admin) who logged JIRA cannot comment on the JIRA
> 2. result of QA run cannot be posted onto JIRA (at least for hbase tests)
>
> :-(
>
> On Thu, May 12, 2016 at 3:10 PM, Andrew Wang <[hidden email]>
> wrote:
>
>> Try asking on infra.chat (Apache INFRA's hipchat). I was in that room
>> earlier today, and they were working on the ongoing JIRA spam.
>>
>> On Thu, May 12, 2016 at 3:03 PM, Xiao Chen <[hidden email]> wrote:
>>
>> > Hello,
>> >
>> > I'm not sure if common-dev is the right contact list, please redirect
>> me if
>> > not.
>> >
>> > It seems the jira lock down is somehow being more strict?
>> > I was able to comment on an HDFS jira
>> > <
>> >
>> https://issues.apache.org/jira/browse/HDFS-4210?focusedCommentId=15282111&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15282111
>> > >
>> > at around 14:45 PDT today, but now I cannot.
>> >
>> > The banner still says:
>> >
>> > Jira is in Temporary Lockdown mode as a spam countermeasure. Only
>> logged-in
>> > users with active roles (committer, contributor, PMC, etc.) will be
>> able to
>> > create issues or comments during this time. Lockdown period from 11 May
>> > 2300 UTC to estimated 12 May 2300 UTC.
>> >
>> >
>> > But with a quick check with Yongjun and Yufei, contributors are locked
>> down
>> > as well.
>> >
>> > Thanks,
>> > -Xiao
>> >
>>
>
>
Reply | Threaded
Open this post in threaded view
|

Re: Jira Lock Down Upgraded?

Steve Loughran-3

> On 13 May 2016, at 06:56, Xiao Chen <[hidden email]> wrote:
>
> FYI - I pinged infra but the answer is only people with
> PMC/committer/contributor *Roles* on jira can comment. Hadoop's contributor
> list seems to be reached it's limit, so cannot be added.


you can add new contributors (I did this yesterday to assign credit to someone). Process is

-work out their username by going to the user page, look at the URL, copy the name bit
-go to the admin page where the list of contributors is.
-paste in the name

What is breaking is the ability to type a name in letter-by-letter and expect JIRA to do an incremental scan. That is overloading


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Jira Lock Down Upgraded?

Bokor Andras
I was added as contributor but I am still not able to comment. So it seems the contributors are locked down too as Xiao metioned earlier.
Steve Loughran <[hidden email]> írta:

>
>> On 13 May 2016, at 06:56, Xiao Chen <[hidden email]> wrote:
>>
>> FYI - I pinged infra but the answer is only people with
>> PMC/committer/contributor *Roles* on jira can comment. Hadoop&#39;s contributor
>> list seems to be reached it&#39;s limit, so cannot be added.
>
>
>you can add new contributors (I did this yesterday to assign credit to someone). Process is
>
>-work out their username by going to the user page, look at the URL, copy the name bit
>-go to the admin page where the list of contributors is.
>-paste in the name
>
>What is breaking is the ability to type a name in letter-by-letter and expect JIRA to do an incremental scan. That is overloading
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [hidden email]
>For additional commands, e-mail: [hidden email]
>