Agilo 0.7 BETA2 Discussion

[ANdreaT]

Hi All,
starting from now the BETA2 testing program, I believed we fixed most
of the things you reported in the group, we are also trying to make
our test environment more solid, adding build machine also for Windows
platforms, we have now an XP with Explorer 7 for testing.

Major changes of the BETA2:

#15 Display ticket labels (Agilo displays the ticket
property labels everywhere and not the raw property)
#43 Fields labels (Also for calculated fields)
#24 Improve Sprint Backlog view
#150 Show only the current user tasks (Current user filter,
works with and without JavaScript)
#103 Create a single plugin
#104 Integrate LinkEndPoint and TicketWrapper
#109 Migrate Infrastructure
#110 Migrate ThemeEngine
#111 Integrate the Account Manager Plugin
#132 Improve Product Backlog Handling
#228 Administration Interface
#151 Ease the creation of a new Sprint
#275 Renaming of the Sprint
#245 Proactive Administration Interface, with inline Help
#246 Proactive Backlog Admin interface (Javascript assisted,
and the properties available are ruled by the type)
#177 Save preferences for 'Hide closed tasks' in the session
(Session based backlog preferences)
#237 Create sensible defaults for new environments
#260 Consistency of the relation Sprint, Milestone (Ticket
assigned to a Sprint belong also to the Milestone, Custom Query)

This and other little changes have been made, we hope you like
them :-)

The Agilo Development Team

ANdreaT
FSchwarz
JVPoser
SSchulze

[Joe]

Hi all,

I upgraded to the BETA2 and now I'm getting "error: redefinition of
group name 'it_ticket' as group 20; was group 16" when I try to click
on Wiki, Timeline, Roadmap and View Ticket. Is this something to do
with the Trac?

Thanks in advance,

Joe

[Andrea Tomasini]

On 3 Sep, 2008, at 17:25 , Joe wrote:

> Hi all,

Hi Joe :-)

> I upgraded to the BETA2 and now I'm getting "error: redefinition of
> group name 'it_ticket' as group 20; was group 16" when I try to click
> on Wiki, Timeline, Roadmap and View Ticket. Is this something to do
> with the Trac?

Ever tried the search function? They say Google is pretty good at
that ;-)
http://groups.google.com/group/agilo/search?group=agilo&q=%27it_ticket%27+as+group&qt_g=Search+this+group

> Thanks in advance,

YAW

> Joe

ANdreaT

[Joe]

Ops.. :) Thanks for the link.. :)
That fixes the issue. You are awesome..

On Sep 3, 11:27 am, Andrea Tomasini <andrea.tomas...@agile42.com>
wrote:

> On 3 Sep, 2008, at 17:25 , Joe wrote:
>
> > Hi all,
>
> Hi Joe :-)
>
> > I upgraded to the BETA2 and now I'm getting "error: redefinition of
> > group name 'it_ticket' as group 20; was group 16" when I try to click
> > on Wiki, Timeline, Roadmap and View Ticket.  Is this something to do
> > with the Trac?
>
> Ever tried the search function? They say Google is pretty good at  

> that ;-)http://groups.google.com/group/agilo/search?group=agilo&q=%27it_ticke...

>
> > Thanks in advance,
>
> YAW
>
> > Joe
>
> ANdreaT
>

>  smime.p7s
> 3KViewDownload

[gduq]

I have been using Trac's multiple project setup and I wanted to try
out Agilo 7 beta 2 on one of them. With some effort (manually
installing dependencies etc) I finally got it working. I noticed
though that all the other trac projects became unable to view tickets
giving the error "The Links Configurations didn't initialize
correctly! => 'allow'" even though they don't have the agilo plugin
enabled. Why is the plugin affecting these other projects?

Regards,

Gordon

[gduq]

ok... got it working.

I had to move the agilo project somewhere else and create another
"<Location>" in httpd.conf pointing to the new location and specifying
a different "PythonInterpreter" for it.

[gduq]

couple of errors.

1. When I try to delete a referenced ticket I get a 404 and the error
in the trac.log is:

2008-09-04 00:52:56,000 Trac[log] ERROR: [AgiloTicket]: Calculation
Error: empty string for float()
Traceback (most recent call last):
File "/srv/agilo/dnforms/plugins/agilo-0.7-BETA2.egg/agilo/ticket/
model.py", line 564, in _get_calculated_attribute_value
File "/srv/agilo/dnforms/plugins/agilo-0.7-BETA2.egg/agilo/links/
model.py", line 93, in __call__
ValueError: empty string for float()

2. When I try to create a reference to an existing ticket using the
"Create" button. error in trac.log is:

2008-09-04 00:49:29,500 Trac[log] ERROR: [AgiloTicket]: Calculation
Error: 'list' object has no attribute 'has_key'
Traceback (most recent call last):
File "/srv/agilo/dnforms/plugins/agilo-0.7-BETA2.egg/agilo/ticket/
model.py", line 575, in _get_calculated_attribute_value
AttributeError: 'list' object has no attribute 'has_key'

[Andrea Tomasini]

On 4 Sep, 2008, at 6:05 , gduq wrote:

> ok... got it working.
>
> I had to move the agilo project somewhere else and create another
> "<Location>" in httpd.conf pointing to the new location and specifying
> a different "PythonInterpreter" for it.

If you use mod_python the whole python VM will see the same
PYTHONPATH :-)

Best
ANdreaT

[Gordon DuQuesnay]

Is there any way to use mod_python without getting my plugins muddled like this?  If not what should I use?

[Andrea Tomasini]

On 4 Sep, 2008, at 8:01 , gduq wrote:

> couple of errors.
Great :-) I love errors ;-)

> 1. When I try to delete a referenced ticket I get a 404 and the error
> in the trac.log is:
>
> 2008-09-04 00:52:56,000 Trac[log] ERROR: [AgiloTicket]: Calculation
> Error: empty string for float()
> Traceback (most recent call last):
> File "/srv/agilo/dnforms/plugins/agilo-0.7-BETA2.egg/agilo/ticket/
> model.py", line 564, in _get_calculated_attribute_value
> File "/srv/agilo/dnforms/plugins/agilo-0.7-BETA2.egg/agilo/links/
> model.py", line 93, in __call__
> ValueError: empty string for float()

This is definitely a bug introduced with BETA2, taken :-)

The error is poppig up because in either the ticket you are trying to
link or in the source of your link there is probably the
remaining_time that is an empty space or an empty string and is not
convertible to float... the bug stays because we should check or trap
the ValueError in conversion... but you can try it out ;-) We will
write some more tests here :-)

> 2. When I try to create a reference to an existing ticket using the
> "Create" button. error in trac.log is:
>
> 2008-09-04 00:49:29,500 Trac[log] ERROR: [AgiloTicket]: Calculation
> Error: 'list' object has no attribute 'has_key'
> Traceback (most recent call last):
> File "/srv/agilo/dnforms/plugins/agilo-0.7-BETA2.egg/agilo/ticket/
> model.py", line 575, in _get_calculated_attribute_value
> AttributeError: 'list' object has no attribute 'has_key'

Same as above and same feature... we introduced a new operator for the
calculated properties ;-)

Best
ANdreaT

[gduq]

found another possible bug.

I created a requirement ticket and set it to milestone1. Then I
deleted milestone1 using the WebAdmin and edited the ticket to be
assigned to milestone3. After doing this the cvs export stopped
working for this ticket and mylyn wouldn't display any query that
included this ticket.

error was something like:

AttributeError: 'NoneType' object has no attribute 'encode'

After much hacking around in the trac.db I got it to work again after
deleting the 'sprint' record from the ticket_custom table.

[Andrea Tomasini]

On 4 Sep, 2008, at 9:41 , Gordon DuQuesnay wrote:

> Is there any way to use mod_python without getting my plugins
> muddled like this? If not what should I use?

http://www.modpython.org/python10/ is a bit old, but goes to the
point, the best way I can think of is to create a virtual server per
project (like we do) in which case will be used a new subinterpreter,
and to keep it even more clean you can set different PYTHON_EGG_CACHE
for every virtual server, but be aware of the egg format, here some
more info: http://threebit.net/mail-archive/trac/msg00138.html

Best
ANdreaT

[Andrea Tomasini]

On 4 Sep, 2008, at 9:49 , gduq wrote:

> found another possible bug.
Let's see...

Do you have 'sprint' as a field of the type Requirement?

Best & Thanks
ANdreaT

[Gordon DuQuesnay]

>Do you have 'sprint' as a field of the type Requirement?

nope...  and I have other requirement tickets created after that one that don't have  this in the custom props table.  wierd huh?

[Andrea Tomasini]

On 4 Sep, 2008, at 9:59 , Gordon DuQuesnay wrote:

> >Do you have 'sprint' as a field of the type Requirement?
>
> nope... and I have other requirement tickets created after that one
> that don't have this in the custom props table. wierd huh?

Not if you created a Story first, or a Task and than transformed it
into a Requirement?! :-?

Best
ANdreaT

[Gordon DuQuesnay]

Yeah... I see how that could happen.  I don't think so but I can't remember now if that is what I did (and as part of the hacking in the trac.db I wiped out the ticket_changes for this ticket) but I will let you know later if it happens again.

[gduq]

I am trying to force different sub interpreters using the
"PythonInterpreter" setting in httpd.conf like so:

<Location /trac>
.
.
.
PythonInterpreter trac_interpreter
PythonOption TracEnvParentDir /srv/trac
PythonOption TracUriRoot /trac/
PythonOption PYTHON_EGG_CACHE /srv/trac/egg-cache
.
.
</Location>

<Location /agilo>
.
.
.
PythonInterpreter agilo_interpreter
PythonOption PYTHON_EGG_CACHE /srv/agilo/egg-cache
PythonOption TracEnvParentDir /srv/agilo
PythonOption TracUriRoot /agilo/
.
.
.
</Location>

This is kind of working...but I am occasionally getting an
"RuntimeError: instance.__dict__ not accessible in restricted mode"
error in the trac (i.e. non agilo) projects. From researching this
it seems like this may be caused by a bug in mod_python that causing
subinterpreters to share some objects.

I could try creating a virtual server for the agilo projects but I'm
not sure that would help since I it would still just be using two
subinterpreters (with names defaulting to the name of the server).

Also I can't figure out how to set a different PYTHON_EGG_CACHE since
apache seems to be ignoring the "PythonOption PYTHON_EGG_CACHE ...."
setting. It may be that this is why the subinterpreters are sharing
objects *shrug*.

Any help/advice would be appreciated.

Thanks in advance.

Gordon

On Sep 4, 3:52 am, Andrea Tomasini <andrea.tomas...@agile42.com>
wrote:

> On 4 Sep, 2008, at 9:41 , Gordon DuQuesnay wrote:
>
> > Is there any way to use mod_python without getting my plugins  
> > muddled like this?  If not what should I use?
>

> http://www.modpython.org/python10/is a bit old, but goes to the  

> point, the best way I can think of is to create a virtual server per  
> project (like we do) in which case will be used a new subinterpreter,  
> and to keep it even more clean you can set different PYTHON_EGG_CACHE  
> for every virtual server, but be aware of the egg format, here some  
> more info:http://threebit.net/mail-archive/trac/msg00138.html
>
> Best
> ANdreaT
>

>  smime.p7s
> 3KViewDownload

[Graham Dumpleton]

> it seems like this may be caused by a bug inmod_pythonthat causing

> subinterpreters to share some objects.
>
> I could try creating a virtual server for the agilo projects but I'm
> not sure that would help since I it would still just be using two
> subinterpreters (with names defaulting to the name of the server).
>
> Also I can't figure out how to set a different PYTHON_EGG_CACHE since
> apache seems to be ignoring the  "PythonOption PYTHON_EGG_CACHE ...."
> setting.  It may be that this is why the subinterpreters are sharing
> objects *shrug*.
>
> Any help/advice would be appreciated.

It is not a bug in mod_python, it is a bug in a third party C
extension module for Python, usually the subversion Python bindings in
the Trac case.

It is pretty well known that Trac should be forced to run in the main
interpreter instance, ie., first one created by Python, and should not
be run in secondary interpreters.

Thus:

PythonInterpreter main_interpreter

It is therefore not generally recommended to run two Trac instances in
different interpreters within mod_python.

If you need to host multiple distinct Trac instances with Apache and
can't have them coexist in same interpreter using mechanisms that Trac
provides, then you would need to use a hosting mechanism whereby the
Trac instances can be delegated to separate daemon processes.

One example of such hosting mechanism is Apache/mod_wsgi.

http://code.google.com/p/modwsgi/wiki/IntegrationWithTrac

Also see:

http://code.google.com/p/modwsgi/wiki/ApplicationIssues#Multiple_Python_Sub_Interpreters

Graham

> Thanks in advance.
>
> Gordon
>
> On Sep 4, 3:52 am, Andrea Tomasini <andrea.tomas...@agile42.com>
> wrote:
>
> > On 4 Sep, 2008, at 9:41 , Gordon DuQuesnay wrote:
>

> > > Is there any way to usemod_pythonwithout getting my plugins  

> > > muddled like this?  If not what should I use?
>

> >http://www.modpython.org/python10/isa bit old, but goes to the  

[Sakke Wiik]

I want to use the original UI, but it seems like something is
overwriting trac.ini/mainnav , so I cannot customize the navigation
anymore. How can I customize it?

cheers,
Sakke

[Sakke Wiik]

I followed the instructions at http://www.agile42.com/cms/pages/download-configuration/
to recreate the burndown table, but it is not created.
How do I recreate the table after dropping it? 'trac-admin <env>
upgrade' says 'Database is up to date, no upgrade necessary.'

cheers,
Sakke

[Andrea Tomasini]

You'll have to wait the next release, at the moment you could disable
only a part of it :-)

> cheers,
Best

> Sakke
ANdreaT

[Andrea Tomasini]

You'll have to update the table system and remove the row relative to
agilo ;-)

Than upgrade
Best
ANdreaT

[Sakke Wiik]

I have set up two Trac projects running Agilo. One has the Agilo UI
and the other the original Trac UI.
When I open the Dashboard on the project with the Trac UI, I can see
the headers (Available Actions and Available Reports) including the
links under them, but the diagrams are not shown. What could be the
issue? The other project with the Agilo UI shows the diagrams fine, so
I'm confident I have all external packages installed.

I need to use the Trac look for some time to not frighten off my
team ;)

cheers,
Sakke

[Andrea Tomasini]

On 11 Sep, 2008, at 15:43 , Sakke Wiik wrote:

> I have set up two Trac projects running Agilo. One has the Agilo UI
> and the other the original Trac UI.

Since agilo BETA 2 you can't remove the UI... how did you do that?

> When I open the Dashboard on the project with the Trac UI, I can see
> the headers (Available Actions and Available Reports) including the
> links under them, but the diagrams are not shown. What could be the
> issue? The other project with the Agilo UI shows the diagrams fine, so
> I'm confident I have all external packages installed.

The diagrams have nothing to do with the UI, they are generated by
matplotlib...

> I need to use the Trac look for some time to not frighten off my
> team ;)

Next version will have a switch on/off for the "advanced" agilo GUI :-)

> cheers,

Best

> Sakke

ANdreaT

[nverdo]

I have setup agilo BETA2 and do not see the agilo theme, but get the
default trac theme.
I have a multi project trac setup on apache using the TracEnvParentDir
handler, could that be related?

On Sep 12, 8:08 am, Andrea Tomasini <andrea.tomas...@agile42.com>
wrote:

>  smime.p7s
> 3KViewDownload

[Andrea Tomasini]

Hi Niels ;-)
there is a template path you have to set in the trac.ini file, it
was not automatically set in Beta1 but is in Beta2, so if you upgraded
from beta1 you may not have it set.

if you create a new project you should have it set automatically.
The problem is that even removing it will not completely disable agilo
stylesheets, this will come next ;)

Best
ANdreaT

[Sakke Wiik]

A download link on your web page points to an old release:

Points to Beta1 (BETA of Agilo for Scrum 0.7 based on Trac 0.11):
first link at http://www.agile42.com/cms/pages/products/

Points to Beta2 (BETA of Agilo for Scrum 0.7 based on Trac 0.11):
bottom of page http://www.agile42.com/cms/pages/download/

cheers,
Sakke

[Sakke Wiik]

> > I have set up two Trac projects running Agilo. One has the Agilo UI
> > and the other the original Trac UI.
>
> Since agilo BETA 2 you can't remove the UI... how did you do that?
>

If you can do that in Beta1, how do I know that Trac doesn't
accidentally use Beta1? I can find agilo-0.7dev_r520-py2.5.egg in the
plugin-folder, and no references to other plugins in my python
installation...

Another problem I have is that tasks are not linked to User Stories.
Was this fixed in beta2? If not, how could I get that backlink
working? I cannot see any 'user_story'-field in trac.ini to add to the
ticket...

cheers,
Sakke