On Thu, Aug 23, 2012 at 3:42 PM, Paul Fox wrote:
> shep was just filing a ticket, and had no way of finding someone's
> trac nick, based on their real name. that reminded me that we could
> still use a page of some sort that lets one do that lookup.
Started this page:
http://wiki.laptop.org/go/T
shep was just filing a ticket, and had no way of finding someone's
trac nick, based on their real name. that reminded me that we could
still use a page of some sort that lets one do that lookup.
of course i have no idea how difficult that would be. even a link to
a ticket whose description conta
Hello,
On Thu, 2012-03-29 at 11:52 -0600, Daniel Drake wrote:
> Martin points out the disadvantage of the text entry field: it lets
> you assign a ticket to a user account that doesn't exist.
Instead of using a drop down box, one could easily write a small plugin
that validates the users when the
On 30.03.2012, at 05:42, Paul Fox wrote:
> saadia husain baloch wrote:
>> One question: How does the assignee field correspond to an email address?
>> Did all those 5500 alias have a @laptop.org address?
>
> there's no requirement that someone have a laptop.org address in order
> to be a bug ass
saadia husain baloch wrote:
> One question: How does the assignee field correspond to an email address?
> Did all those 5500 alias have a @laptop.org address?
there's no requirement that someone have a laptop.org address in order
to be a bug assignee, if that's what you're asking. (at least, i
On Thu, Mar 29, 2012 at 09:46:45PM -0400, Saadia Husain Baloch wrote:
> One question: How does the assignee field correspond to an email
> address? Did all those 5500 alias have a @laptop.org address?
Our trac instance still allows creation of accounts before e-mail
confirmation, and there are rob
On Thu, Mar 29, 2012 at 9:46 PM, Saadia Husain Baloch wrote:
>
> One question: How does the assignee field correspond to an email address?
> Did all those 5500 alias have a @laptop.org address?
We could assign one in the process of setting up the account...
-walter
> -Saadia
>
>
>
>
> On Thu, M
One question: How does the assignee field correspond to an email address?
Did all those 5500 alias have a @laptop.org address?
-Saadia
On Thu, Mar 29, 2012 at 7:51 PM, James Cameron wrote:
> On Thu, Mar 29, 2012 at 07:31:18PM -0400, Paul Fox wrote:
> > the lost advantage of the dropdown list i
On Thu, Mar 29, 2012 at 07:31:18PM -0400, Paul Fox wrote:
> the lost advantage of the dropdown list is that it can serve as a
> reminder of how the intended recipient is identified in trac
> (i.e., "smithbone"? "rsmith"? "richard_smith"? "richard"?). it
> would be a huge help if there could be
daniel wrote:
> On Thu, Mar 29, 2012 at 4:30 PM, James Cameron wrote:
> > I would prefer to switch now.
>
> Chris voted for this as well so I went ahead and made the change. Can
> easily be changed back if it presents problems.
>
> Loading a tickets locally on the server went from taking
On Thu, Mar 29, 2012 at 11:30 PM, James Cameron wrote:
> On Thu, Mar 29, 2012 at 11:52:20AM -0600, Daniel Drake wrote:
>> [...]
>> The main cause of this slowness is that we choose to display potential
>> ticket owners as a drop-down list (rather than a text entry field, the
>> trac default). The
On Thu, Mar 29, 2012 at 4:30 PM, James Cameron wrote:
> I would prefer to switch now.
Chris voted for this as well so I went ahead and made the change. Can
easily be changed back if it presents problems.
Loading a tickets locally on the server went from taking 2.8s to now
taking 1.3s.
Daniel
__
On Thu, Mar 29, 2012 at 11:52:20AM -0600, Daniel Drake wrote:
> [...]
> The main cause of this slowness is that we choose to display potential
> ticket owners as a drop-down list (rather than a text entry field, the
> trac default). The performance issues are well known:
> http://trac.edgewall.org/
On Thu, Mar 29, 2012 at 4:47 PM, Jon Nettleton wrote:
> Another option could be to add some javascript to the page that uses
> ajax to query the users only when the drop down menu is initiated.
For best results you should follow the coding style of Trac and issue
3 XmlHttpRequest()s per user acco
On Thu, Mar 29, 2012 at 9:22 PM, Martin Langhoff
wrote:
> On Thu, Mar 29, 2012 at 2:46 PM, Martin Langhoff
> wrote:
>> On Thu, Mar 29, 2012 at 1:52 PM, Daniel Drake wrote:
>>> Through some profiling I found that an inefficient trac design causes
>>> about 17,000 identical SQL queries to be execu
On Thu, Mar 29, 2012 at 2:46 PM, Martin Langhoff
wrote:
> On Thu, Mar 29, 2012 at 1:52 PM, Daniel Drake wrote:
>> Through some profiling I found that an inefficient trac design causes
>> about 17,000 identical SQL queries to be executed during each page
>> load, related to the number of users in
On Thu, Mar 29, 2012 at 1:52 PM, Daniel Drake wrote:
> Through some profiling I found that an inefficient trac design causes
> about 17,000 identical SQL queries to be executed during each page
> load, related to the number of users in the system (we have about
> 5.5k).
Sad, track is coded by SQL
On Thu, Mar 29, 2012 at 11:52 AM, Daniel Drake wrote:
> Nevertheless, if things become very slow again, I think we should
> switch to the text field and benefit from a huge speedup. Will keep an
> eye on it.
The other discovery made here was that the wsgi instance on
dev.laptop.org (an old ubuntu
Hi,
Yesterday, I imported our trac database into trac 0.12.3 on a separate
machine and found that even on such a setup, each ticket page was
taking 19 seconds to load (same as the production server at
dev.laptop.org).
Through some profiling I found that an inefficient trac design causes
about 17,
19 matches
Mail list logo
