Plugin has stop workin'

[T. N.R]

I've installed plugin and all works, but since 2 days it doesn't draw anymore the stats.

On log is nothing to appreciate. (trac.log in DEBUG mode) and here is the output from the bottom of the statssite:

Logger Console

INFO1649638ms (+0) 15:41:53:

Connection

Connection object for transaction 5 destroyed.

INFO1649638ms (+776) 15:41:53:

Connection

Success callback with scope. HTTP code is 200

INFO1648862ms (+0) 15:41:52:

Connection

Transaction 5 sent.

INFO1648862ms (+1) 15:41:52:

Connection

Default HTTP header X-Requested-With set with value of XMLHttpRequest

INFO1648861ms (+7565) 15:41:52:

Connection

XHR object created for transaction 5

INFO1641296ms (+0) 15:41:45:

Connection

Connection object for transaction 4 destroyed.

INFO1641296ms (+1647) 15:41:45:

Connection

Success callback with scope. HTTP code is 200

INFO1639649ms (+1) 15:41:43:

Connection

Transaction 4 sent.

INFO1639648ms (+1) 15:41:43:

Connection

Default HTTP header X-Requested-With set with value of XMLHttpRequest

INFO1639647ms (+1624535) 15:41:43:

Connection

XHR object created for transaction 4

INFO15112ms (+1) 15:14:38:

Connection

Connection object for transaction 3 destroyed.

INFO15111ms (+1199) 15:14:38:

Connection

Success callback with scope. HTTP code is 200

INFO13912ms (+0) 15:14:37:

Connection

Transaction 3 sent.

INFO13912ms (+2) 15:14:37:

Connection

Default HTTP header X-Requested-With set with value of XMLHttpRequest

INFO13910ms (+2355) 15:14:37:

Connection

XHR object created for transaction 3

INFO11555ms (+0) 15:14:35:

Connection

Connection object for transaction 2 destroyed.

INFO11555ms (+255) 15:14:35:

Connection

Success callback with scope. HTTP code is 200

INFO11300ms (+0) 15:14:35:

Connection

Transaction 2 sent.

INFO11300ms (+1) 15:14:35:

Connection

Default HTTP header X-Requested-With set with value of XMLHttpRequest

INFO11299ms (+3927) 15:14:35:

Connection

XHR object created for transaction 2

INFO7372ms (+0) 15:14:31:

Connection

Connection object for transaction 1 destroyed.

INFO7372ms (+256) 15:14:31:

Connection

Success callback with scope. HTTP code is 200

INFO7116ms (+1) 15:14:30:

Connection

Transaction 1 sent.

INFO7115ms (+1) 15:14:30:

Connection

Default HTTP header X-Requested-With set with value of XMLHttpRequest

INFO7114ms (+6653) 15:14:30:

Connection

XHR object created for transaction 1

INFO461ms (+1) 15:14:24:

Connection

Connection object for transaction 0 destroyed.

INFO460ms (+322) 15:14:24:

Connection

Success callback with scope. HTTP code is 200

INFO138ms (+0) 15:14:23:

Connection

Transaction 0 sent.

INFO138ms (+0) 15:14:23:

Connection

Default HTTP header X-Requested-With set with value of XMLHttpRequest

INFO138ms (+1) 15:14:23:

Connection

Initialize transaction header X-Request-Header to XMLHttpRequest.

INFO137ms (+75) 15:14:23:

Connection

XHR object created for transaction 0

INFO62ms (+62) 15:14:23:

LogReader instance0

LogReader initialized

INFO0ms (+0) 15:14:23:

global

Logger initialized

Attached the capture of the plugin

[Ryan J Ollos]

For how long was it working before it stopped working for you? Possibly related to #8296 and #3412. Please try adjusting the start and end dates, and resolution, and see if you are able to get any tickets to appears in the chart.

There are some known issues with the start and end date, and resolution, that I just haven't had time to fix yet, but I hope I will over the holiday.

[T. N.R]

ticketstats?content=render&start_date=12/21/2010&end_date=12/22/2010&resolution=30&milestone=all didnt show anything again.

we've start working with ticketstats near half year. same time as with trac, and until monday all was right...

[T. N.R]

Replying to rjollos:

There are some known issues with the start and end date, and resolution, that I just haven't had time to fix yet, but I hope I will over the holiday.

Merry x-mas and happy new year to you too

[T. N.R]

Problem found, the plugin looks for "priority" what we don't have in our trac.

[Ryan J Ollos]

Replying to theget:

Problem found, the plugin looks for "priority" what we don't have in our trac.

Thanks for posting what you found. Since Priority is a default field in Trac, the original developer probably considered it a safe assumption that the field exists. However, we should be checking that it exists, and creating a patch should be fairly straightforward.

Looking at the source code just now, I see that priority is being selected in the query but don't see a place that it is being used, so the fix may be very easy to do.

[T. N.R]

Should be great to change from priority to severity

[anonymous]

Replying to theget:

Should be great to change from priority to severity

we had remove the "priority" class on adminsite, as there shows " You can remove all items from this list to completely hide this field from the user interface. "

I've added as test again all 5 priorities, and set some tickets with a priority, it starts working again:

[Ryan J Ollos]

This plugin seems to be somewhat broken, so I posted notice to the project wiki page and hope to have it fixed up within a month or two (see #3412, #8296, #8330).

[Ryan J Ollos]

Priority was removed from the SQL queries in [13107]. This ticket should be left open until the same is done in macro.py (or the code is replaced with calls to functions currently in web_ui.py).