You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@bloodhound.apache.org by Apache Bloodhound <de...@bloodhound.apache.org> on 2013/05/07 17:29:40 UTC
[Apache Bloodhound] #516: No ticket view permission for nightly
build demo configuration
#516: No ticket view permission for nightly build demo configuration
---------------------+---------------
Reporter: andrej | Owner:
Type: defect | Status: new
Priority: major | Version:
Resolution: |
---------------------+---------------
It looks like nightly build demo (bh-demo1.apache.org) is does not allow
anonymous user to view tickets. That's probably has something to do with
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/516>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #516: No ticket view permission for nightly
build demo configuration
Posted by Apache Bloodhound <de...@bloodhound.apache.org>.
#516: No ticket view permission for nightly build demo configuration
------------------------+--------------------------------
Reporter: andrej | Owner: nobody
Type: defect | Status: closed
Priority: major | Milestone:
Component: siteadmin | Version:
Resolution: fixed | Keywords: nightly-build-demo
------------------------+--------------------------------
Changes (by rjollos):
* component: dashboard => siteadmin
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/516#comment:3>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #516: No ticket view permission for nightly
build demo configuration
Posted by Ryan Ollos <ry...@wandisco.com>.
On Thu, May 30, 2013 at 10:21 PM, Olemis Lang <ol...@gmail.com> wrote:
> On 5/30/13, Ryan Ollos <ry...@wandisco.com> wrote:
> > On Thu, May 9, 2013 at 12:46 PM, Olemis Lang <ol...@gmail.com> wrote:
> >
> >> On 5/8/13, Gary Martin <ga...@wandisco.com> wrote:
> >> > On 08/05/13 18:06, Olemis Lang wrote:
> >> >> On 5/8/13, Gary Martin <ga...@wandisco.com> wrote:
> >> >>> On 08/05/13 16:15, Olemis Lang wrote:
> >> >>>> On 5/8/13, Gary Martin <ga...@wandisco.com> wrote:
> >> >> [...]
> >> >>>>> If it is, how does that allow me to add a resolution enum to a
> >> >>>>> product,
> >> >>>>> for example?
> >> >>>>>
> >> >>>> Product prefix = test
> >> >>>>
> >> >>>> {{{
> >> >>>> #!sh
> >> >>>>
> >> >> [...]
> >> >>>> Trac [/path/to/trac/env]> product admin test resolution add custom
> >> >>>> Trac [/path/to/trac/env]> product admin test resolution list
> >> >>>>
> >> >> [...]
> >> >>>> }}}
> >> >>>>
> >> >>> Fair enough. I didn't spot that in the list of commands. I obviously
> >> was
> >> >>> not looking hard enough.
> >> >>>
> >> >> JFTR the second part of the command (i.e. resolution ...) is
> >> >> «re-dispatched» to the target admin command handler but in product
> >> >> scope . Therefore help msg is generic Supported command list might be
> >> >> even different to global cmd list given the fact that component
> >> >> enable/disable rules in product scope might be different to global
> >> >> list .
> >> >>
> >> >> Therefore maybe it's ok to improve product admin cmd help docs ... or
> >> >> just add a reference to a wiki page clarifying its usage .
> >> >>
> >> >
> >> > It seems a reasonable solution. I might expect something like "product
> >> > admin [product] help" or "product help admin [product]" for the
> purpose
> >> > of listing the available product admin commands.
> >> >
> >>
> >> Done! Please review the patch submitted for #518 .
> >>
> >
> > I noticed a possible minor issue while testing the patch (issue not
> caused
> > by the patch itself). I'm interested to hear your thoughts on the
> expected
> > behavior before I create a ticket.
> >
> > With TracStandalone,
> >
> >> config set components trac.wiki.* disabled
> >
> > and a page refresh immediately shows that the wiki is disabled. However,
> > when the corresponding product command is run, tracd must be killed and
> > restarted for the change to take effect.
> >
> >> product admin prod1 config set components trac.wiki.* disabled
> >
> > I tested while disabling/enabling other components and had the same
> result.
> > Another possibly-related result of this is that the TracAdmin console
> must
> > be exited before the allowed commands for a disabled component are no
> > longer shown.
> >
>
> I'd have to confirm my hypothesis but maybe this is because of caching
> . Components enabled / disabled state is cached in-memory . There's a
> chance for it to get updated once config file is written because it's
> reloaded from scratch afterwards (or based on file timestamps) .
> Nevertheless , there's no such reloading mechanism for DB config
> values .
>
> This is a good catch , if you please could create a new ticket then
> I'll take a look and should be ready for next release .
>
> --
> Regards,
>
> Olemis.
>
Thanks, Olemis. Ticket opened is #539.
Re: [Apache Bloodhound] #516: No ticket view permission for nightly
build demo configuration
Posted by Olemis Lang <ol...@gmail.com>.
On 5/30/13, Ryan Ollos <ry...@wandisco.com> wrote:
> On Thu, May 9, 2013 at 12:46 PM, Olemis Lang <ol...@gmail.com> wrote:
>
>> On 5/8/13, Gary Martin <ga...@wandisco.com> wrote:
>> > On 08/05/13 18:06, Olemis Lang wrote:
>> >> On 5/8/13, Gary Martin <ga...@wandisco.com> wrote:
>> >>> On 08/05/13 16:15, Olemis Lang wrote:
>> >>>> On 5/8/13, Gary Martin <ga...@wandisco.com> wrote:
>> >> [...]
>> >>>>> If it is, how does that allow me to add a resolution enum to a
>> >>>>> product,
>> >>>>> for example?
>> >>>>>
>> >>>> Product prefix = test
>> >>>>
>> >>>> {{{
>> >>>> #!sh
>> >>>>
>> >> [...]
>> >>>> Trac [/path/to/trac/env]> product admin test resolution add custom
>> >>>> Trac [/path/to/trac/env]> product admin test resolution list
>> >>>>
>> >> [...]
>> >>>> }}}
>> >>>>
>> >>> Fair enough. I didn't spot that in the list of commands. I obviously
>> was
>> >>> not looking hard enough.
>> >>>
>> >> JFTR the second part of the command (i.e. resolution ...) is
>> >> «re-dispatched» to the target admin command handler but in product
>> >> scope . Therefore help msg is generic Supported command list might be
>> >> even different to global cmd list given the fact that component
>> >> enable/disable rules in product scope might be different to global
>> >> list .
>> >>
>> >> Therefore maybe it's ok to improve product admin cmd help docs ... or
>> >> just add a reference to a wiki page clarifying its usage .
>> >>
>> >
>> > It seems a reasonable solution. I might expect something like "product
>> > admin [product] help" or "product help admin [product]" for the purpose
>> > of listing the available product admin commands.
>> >
>>
>> Done! Please review the patch submitted for #518 .
>>
>
> I noticed a possible minor issue while testing the patch (issue not caused
> by the patch itself). I'm interested to hear your thoughts on the expected
> behavior before I create a ticket.
>
> With TracStandalone,
>
>> config set components trac.wiki.* disabled
>
> and a page refresh immediately shows that the wiki is disabled. However,
> when the corresponding product command is run, tracd must be killed and
> restarted for the change to take effect.
>
>> product admin prod1 config set components trac.wiki.* disabled
>
> I tested while disabling/enabling other components and had the same result.
> Another possibly-related result of this is that the TracAdmin console must
> be exited before the allowed commands for a disabled component are no
> longer shown.
>
I'd have to confirm my hypothesis but maybe this is because of caching
. Components enabled / disabled state is cached in-memory . There's a
chance for it to get updated once config file is written because it's
reloaded from scratch afterwards (or based on file timestamps) .
Nevertheless , there's no such reloading mechanism for DB config
values .
This is a good catch , if you please could create a new ticket then
I'll take a look and should be ready for next release .
--
Regards,
Olemis.
Re: [Apache Bloodhound] #516: No ticket view permission for nightly
build demo configuration
Posted by Ryan Ollos <ry...@wandisco.com>.
On Thu, May 9, 2013 at 12:46 PM, Olemis Lang <ol...@gmail.com> wrote:
> On 5/8/13, Gary Martin <ga...@wandisco.com> wrote:
> > On 08/05/13 18:06, Olemis Lang wrote:
> >> On 5/8/13, Gary Martin <ga...@wandisco.com> wrote:
> >>> On 08/05/13 16:15, Olemis Lang wrote:
> >>>> On 5/8/13, Gary Martin <ga...@wandisco.com> wrote:
> >> [...]
> >>>>> If it is, how does that allow me to add a resolution enum to a
> >>>>> product,
> >>>>> for example?
> >>>>>
> >>>> Product prefix = test
> >>>>
> >>>> {{{
> >>>> #!sh
> >>>>
> >> [...]
> >>>> Trac [/path/to/trac/env]> product admin test resolution add custom
> >>>> Trac [/path/to/trac/env]> product admin test resolution list
> >>>>
> >> [...]
> >>>> }}}
> >>>>
> >>> Fair enough. I didn't spot that in the list of commands. I obviously
> was
> >>> not looking hard enough.
> >>>
> >> JFTR the second part of the command (i.e. resolution ...) is
> >> «re-dispatched» to the target admin command handler but in product
> >> scope . Therefore help msg is generic Supported command list might be
> >> even different to global cmd list given the fact that component
> >> enable/disable rules in product scope might be different to global
> >> list .
> >>
> >> Therefore maybe it's ok to improve product admin cmd help docs ... or
> >> just add a reference to a wiki page clarifying its usage .
> >>
> >
> > It seems a reasonable solution. I might expect something like "product
> > admin [product] help" or "product help admin [product]" for the purpose
> > of listing the available product admin commands.
> >
>
> Done! Please review the patch submitted for #518 .
>
I noticed a possible minor issue while testing the patch (issue not caused
by the patch itself). I'm interested to hear your thoughts on the expected
behavior before I create a ticket.
With TracStandalone,
> config set components trac.wiki.* disabled
and a page refresh immediately shows that the wiki is disabled. However,
when the corresponding product command is run, tracd must be killed and
restarted for the change to take effect.
> product admin prod1 config set components trac.wiki.* disabled
I tested while disabling/enabling other components and had the same result.
Another possibly-related result of this is that the TracAdmin console must
be exited before the allowed commands for a disabled component are no
longer shown.
Re: [Apache Bloodhound] #516: No ticket view permission for nightly
build demo configuration
Posted by Olemis Lang <ol...@gmail.com>.
On 5/8/13, Gary Martin <ga...@wandisco.com> wrote:
> On 08/05/13 18:06, Olemis Lang wrote:
>> On 5/8/13, Gary Martin <ga...@wandisco.com> wrote:
>>> On 08/05/13 16:15, Olemis Lang wrote:
>>>> On 5/8/13, Gary Martin <ga...@wandisco.com> wrote:
>> [...]
>>>>> If it is, how does that allow me to add a resolution enum to a
>>>>> product,
>>>>> for example?
>>>>>
>>>> Product prefix = test
>>>>
>>>> {{{
>>>> #!sh
>>>>
>> [...]
>>>> Trac [/path/to/trac/env]> product admin test resolution add custom
>>>> Trac [/path/to/trac/env]> product admin test resolution list
>>>>
>> [...]
>>>> }}}
>>>>
>>> Fair enough. I didn't spot that in the list of commands. I obviously was
>>> not looking hard enough.
>>>
>> JFTR the second part of the command (i.e. resolution ...) is
>> «re-dispatched» to the target admin command handler but in product
>> scope . Therefore help msg is generic Supported command list might be
>> even different to global cmd list given the fact that component
>> enable/disable rules in product scope might be different to global
>> list .
>>
>> Therefore maybe it's ok to improve product admin cmd help docs ... or
>> just add a reference to a wiki page clarifying its usage .
>>
>
> It seems a reasonable solution. I might expect something like "product
> admin [product] help" or "product help admin [product]" for the purpose
> of listing the available product admin commands.
>
Done! Please review the patch submitted for #518 .
--
Regards,
Olemis.
Re: [Apache Bloodhound] #516: No ticket view permission for nightly
build demo configuration
Posted by Gary Martin <ga...@wandisco.com>.
On 08/05/13 18:06, Olemis Lang wrote:
> On 5/8/13, Gary Martin <ga...@wandisco.com> wrote:
>> On 08/05/13 16:15, Olemis Lang wrote:
>>> On 5/8/13, Gary Martin <ga...@wandisco.com> wrote:
> [...]
>>>> If it is, how does that allow me to add a resolution enum to a product,
>>>> for example?
>>>>
>>> Product prefix = test
>>>
>>> {{{
>>> #!sh
>>>
> [...]
>>> Trac [/path/to/trac/env]> product admin test resolution add custom
>>> Trac [/path/to/trac/env]> product admin test resolution list
>>>
> [...]
>>> }}}
>>>
>> Fair enough. I didn't spot that in the list of commands. I obviously was
>> not looking hard enough.
>>
> JFTR the second part of the command (i.e. resolution ...) is
> «re-dispatched» to the target admin command handler but in product
> scope . Therefore help msg is generic Supported command list might be
> even different to global cmd list given the fact that component
> enable/disable rules in product scope might be different to global
> list .
>
> Therefore maybe it's ok to improve product admin cmd help docs ... or
> just add a reference to a wiki page clarifying its usage .
>
It seems a reasonable solution. I might expect something like "product
admin [product] help" or "product help admin [product]" for the purpose
of listing the available product admin commands.
Cheers,
Gary
Re: [Apache Bloodhound] #516: No ticket view permission for nightly
build demo configuration
Posted by Olemis Lang <ol...@gmail.com>.
On 5/8/13, Gary Martin <ga...@wandisco.com> wrote:
> On 08/05/13 16:15, Olemis Lang wrote:
>> On 5/8/13, Gary Martin <ga...@wandisco.com> wrote:
[...]
>>> If it is, how does that allow me to add a resolution enum to a product,
>>> for example?
>>>
>> Product prefix = test
>>
>> {{{
>> #!sh
>>
[...]
>>
>> Trac [/path/to/trac/env]> product admin test resolution add custom
>> Trac [/path/to/trac/env]> product admin test resolution list
>>
[...]
>>
>> }}}
>>
>
> Fair enough. I didn't spot that in the list of commands. I obviously was
> not looking hard enough.
>
JFTR the second part of the command (i.e. resolution ...) is
«re-dispatched» to the target admin command handler but in product
scope . Therefore help msg is generic Supported command list might be
even different to global cmd list given the fact that component
enable/disable rules in product scope might be different to global
list .
Therefore maybe it's ok to improve product admin cmd help docs ... or
just add a reference to a wiki page clarifying its usage .
--
Regards,
Olemis.
Re: [Apache Bloodhound] #516: No ticket view permission for nightly
build demo configuration
Posted by Gary Martin <ga...@wandisco.com>.
On 08/05/13 16:15, Olemis Lang wrote:
> On 5/8/13, Gary Martin <ga...@wandisco.com> wrote:
>> On 07/05/13 20:10, Olemis Lang wrote:
>>> On 5/7/13, Gary Martin <ga...@wandisco.com> wrote:
>>>> On 7 May 2013 16:31, Apache Bloodhound <de...@bloodhound.apache.org>
>>>> wrote:
>>>>
>>> [...]
>>>> Talking of which, we could probably do with admin commands updating so
>>>> that
>>>> it is possible to set these details from the command line.
>>>>
>>> Is this comment related somehow to #475 ?
>>>
>> If it is, how does that allow me to add a resolution enum to a product,
>> for example?
>>
> Product prefix = test
>
> {{{
> #!sh
>
> $ sudo trac-admin /path/to/trac/env
> Welcome to trac-admin 1.0.1
> Interactive Trac administration console.
> Copyright (C) 2003-2013 Edgewall Software
>
> Type: '?' or 'help' for help on commands.
>
> Trac [/path/to/trac/env]> product admin test resolution list
>
> Possible Values
> ---------------
> fixed
> invalid
> wontfix
> duplicate
> worksforme
>
> Trac [/path/to/trac/env]> product admin test resolution add custom
> Trac [/path/to/trac/env]> product admin test resolution list
>
> Possible Values
> ---------------
> fixed
> invalid
> wontfix
> duplicate
> worksforme
> custom
>
> }}}
>
Fair enough. I didn't spot that in the list of commands. I obviously was
not looking hard enough.
Cheers,
Gary
Re: [Apache Bloodhound] #516: No ticket view permission for nightly
build demo configuration
Posted by Olemis Lang <ol...@gmail.com>.
On 5/8/13, Gary Martin <ga...@wandisco.com> wrote:
> On 07/05/13 20:10, Olemis Lang wrote:
>> On 5/7/13, Gary Martin <ga...@wandisco.com> wrote:
>>> On 7 May 2013 16:31, Apache Bloodhound <de...@bloodhound.apache.org>
>>> wrote:
>>>
>> [...]
>>> Talking of which, we could probably do with admin commands updating so
>>> that
>>> it is possible to set these details from the command line.
>>>
>> Is this comment related somehow to #475 ?
>>
>
> If it is, how does that allow me to add a resolution enum to a product,
> for example?
>
Product prefix = test
{{{
#!sh
$ sudo trac-admin /path/to/trac/env
Welcome to trac-admin 1.0.1
Interactive Trac administration console.
Copyright (C) 2003-2013 Edgewall Software
Type: '?' or 'help' for help on commands.
Trac [/path/to/trac/env]> product admin test resolution list
Possible Values
---------------
fixed
invalid
wontfix
duplicate
worksforme
Trac [/path/to/trac/env]> product admin test resolution add custom
Trac [/path/to/trac/env]> product admin test resolution list
Possible Values
---------------
fixed
invalid
wontfix
duplicate
worksforme
custom
}}}
--
Regards,
Olemis.
Re: [Apache Bloodhound] #516: No ticket view permission for nightly
build demo configuration
Posted by Gary Martin <ga...@wandisco.com>.
On 07/05/13 20:10, Olemis Lang wrote:
> On 5/7/13, Gary Martin <ga...@wandisco.com> wrote:
>> On 7 May 2013 16:31, Apache Bloodhound <de...@bloodhound.apache.org> wrote:
>>
> [...]
>> Talking of which, we could probably do with admin commands updating so that
>> it is possible to set these details from the command line.
>>
> Is this comment related somehow to #475 ?
>
If it is, how does that allow me to add a resolution enum to a product,
for example?
Cheers,
Gary
Re: [Apache Bloodhound] #516: No ticket view permission for nightly
build demo configuration
Posted by Olemis Lang <ol...@gmail.com>.
On 5/7/13, Gary Martin <ga...@wandisco.com> wrote:
> On 7 May 2013 16:31, Apache Bloodhound <de...@bloodhound.apache.org> wrote:
>
[...]
>
> Talking of which, we could probably do with admin commands updating so that
> it is possible to set these details from the command line.
>
Is this comment related somehow to #475 ?
--
Regards,
Olemis.
Re: [Apache Bloodhound] #516: No ticket view permission for nightly
build demo configuration
Posted by Gary Martin <ga...@wandisco.com>.
On 07/05/13 16:42, Gary Martin wrote:
>
> On 7 May 2013 16:31, Apache Bloodhound <dev@bloodhound.apache.org
> <ma...@bloodhound.apache.org>> wrote:
>
> #516: No ticket view permission for nightly build demo configuration
> ------------------------+--------------------------------
> Reporter: andrej | Owner: nobody
> Type: defect | Status: new
> Priority: major | Milestone:
> Component: dashboard | Version:
> Resolution: | Keywords: nightly-build-demo
> ------------------------+--------------------------------
> Changes (by andrej):
>
> * owner: => nobody
> * keywords: => nightly-build-demo
> * component: => dashboard
>
>
> Old description:
>
> > It looks like nightly build demo (bh-demo1.apache.org
> <http://bh-demo1.apache.org>) is does not allow
> > anonymous user to view tickets. That's probably has something to
> do with
>
> New description:
>
> It looks like nightly build demo (bh-demo1.apache.org
> <http://bh-demo1.apache.org>) is does not allow
> anonymous user to view tickets. That's probably has something to
> do with
> multi-product permissions.
>
> --
>
> --
> Ticket URL:
> <https://issues.apache.org/bloodhound/ticket/516#comment:1>
> Apache Bloodhound <https://issues.apache.org/bloodhound/>
> The Apache Bloodhound issue tracker
>
>
>
> It might be down to the method of populating the database. We are
> swapping from postgresql to sqlite which is probably something that we
> do not care about supporting exactly. Other symptoms are the lack of
> resolutions and stuff. I can probably swap to throwing in an sqlite
> snapshot instead.
>
> Talking of which, we could probably do with admin commands updating so
> that it is possible to set these details from the command line.
>
> Cheers,
> Gary
https://bh-demo1.apache.org/products/%40/ticket/1
I'd call this fixed now. I'll close the ticket.
Cheers,
Gary
Re: [Apache Bloodhound] #516: No ticket view permission for nightly
build demo configuration
Posted by Gary Martin <ga...@wandisco.com>.
On 7 May 2013 16:31, Apache Bloodhound <de...@bloodhound.apache.org> wrote:
> #516: No ticket view permission for nightly build demo configuration
> ------------------------+--------------------------------
> Reporter: andrej | Owner: nobody
> Type: defect | Status: new
> Priority: major | Milestone:
> Component: dashboard | Version:
> Resolution: | Keywords: nightly-build-demo
> ------------------------+--------------------------------
> Changes (by andrej):
>
> * owner: => nobody
> * keywords: => nightly-build-demo
> * component: => dashboard
>
>
> Old description:
>
> > It looks like nightly build demo (bh-demo1.apache.org) is does not allow
> > anonymous user to view tickets. That's probably has something to do with
>
> New description:
>
> It looks like nightly build demo (bh-demo1.apache.org) is does not allow
> anonymous user to view tickets. That's probably has something to do with
> multi-product permissions.
>
> --
>
> --
> Ticket URL: <https://issues.apache.org/bloodhound/ticket/516#comment:1>
> Apache Bloodhound <https://issues.apache.org/bloodhound/>
> The Apache Bloodhound issue tracker
>
It might be down to the method of populating the database. We are swapping
from postgresql to sqlite which is probably something that we do not care
about supporting exactly. Other symptoms are the lack of resolutions and
stuff. I can probably swap to throwing in an sqlite snapshot instead.
Talking of which, we could probably do with admin commands updating so that
it is possible to set these details from the command line.
Cheers,
Gary
Re: [Apache Bloodhound] #516: No ticket view permission for nightly
build demo configuration
Posted by Apache Bloodhound <de...@bloodhound.apache.org>.
#516: No ticket view permission for nightly build demo configuration
------------------------+--------------------------------
Reporter: andrej | Owner: nobody
Type: defect | Status: new
Priority: major | Milestone:
Component: dashboard | Version:
Resolution: | Keywords: nightly-build-demo
------------------------+--------------------------------
Changes (by andrej):
* owner: => nobody
* keywords: => nightly-build-demo
* component: => dashboard
Old description:
> It looks like nightly build demo (bh-demo1.apache.org) is does not allow
> anonymous user to view tickets. That's probably has something to do with
New description:
It looks like nightly build demo (bh-demo1.apache.org) is does not allow
anonymous user to view tickets. That's probably has something to do with
multi-product permissions.
--
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/516#comment:1>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #516: No ticket view permission for nightly
build demo configuration
Posted by Apache Bloodhound <de...@bloodhound.apache.org>.
#516: No ticket view permission for nightly build demo configuration
------------------------+--------------------------------
Reporter: andrej | Owner: nobody
Type: defect | Status: closed
Priority: major | Milestone:
Component: dashboard | Version:
Resolution: fixed | Keywords: nightly-build-demo
------------------------+--------------------------------
Changes (by gjm):
* status: new => closed
* resolution: => fixed
Comment:
After adjusting the way the demos build, this appears to be working.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/516#comment:2>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker