On Wednesday, June 26, 2013 3:05:46 PM UTC-5, RjOllos wrote: > > On Wednesday, June 26, 2013 12:27:13 PM UTC-7, Lukasz Szybalski wrote: >> >> >> >> On Wednesday, June 26, 2013 12:44:17 PM UTC-5, RjOllos wrote: >>> >>> On Wednesday, June 26, 2013 10:02:39 AM UTC-7, hasienda wrote: >>>> >>>> -----BEGIN PGP SIGNED MESSAGE----- >>>> Hash: SHA1 >>>> >>>> On 26.06.2013 16:52, Lukasz Szybalski wrote: >>>> > >>>> > Hello, >>>> > How can I get a python 2.7 egg for batchticketmodify version 0.8.0? >>>> > >>>> > I got the trunk and did python setup.py bdist_egg >>>> > but for some reason the UI does not appear. I'm thinking something >>>> > might be broken in trunk for version 0.12? >>>> > >>>> > See screenshot. >>>> >>>> OT: Never seen such a high ticket number (#817336). Is this a >>>> production >>>> Trac application, and do you possibly know even bigger ones in terms of >>>> ticket count? Would be interesting to know what setup including plugins >>>> installed works, and to know some known performance figures. >>>> >>> >>> Good eye. It would be quite interesting to know more details about this >>> setup. >>> >>> After giving this some more thought, I think the problem is most likely >>> that the user hasn't done a `trac-admin $env deploy /deploy/to/path`, as >>> described in >>> >> Hello, >> >> Thank you!!!!!!!! >> >> cd .....apache >> mv eggs old_eggs >> mkdir eggs >> chown www-data:www-data eggs >> > > I hadn't considered that removing the egg cache could be needed, but I > suppose that is worth keeping in mind. I wonder if you could have just > re-started your webserver to achieve the same end. >
No. That did not resolve it. I have restarted multiple times. I presume cache made a tmp egg that even do it was python2.6 version was somehow interfering with the new trac and python2.7. > > >> I moved it just to make sure I don't lose what is in there but I'm pretty >> sure I could have deleted tmp eggs in there and have apache regenerate them. >> This has fixed my problem. >> >> As far as our trac: >> Yes 817K tickets and going. >> Server: AMD Opteron(tm) Processor 6128 16core >> 1.5TB XFS (ext3 has a 32000 subfolder limit) >> 16GB of ram >> >> Performance is ok...as things grow we got this above server. It looks >> like we will need to make more changes. The only real performance issue is >> the "custom" fields being as BLOB or TEXT which mysql cannot cache/keep in >> memory. So when you search the whole 817K tickets for custom_number= 123456 >> it takes about 3 seconds now. >> > > Are you using an plugins? > > >> The new issue that is coming up in this version is that they have to >> click "modify" on order to close ticket which is more clicks they they used >> to have to do in 0.11. >> > > The collapsed modify section seems to be hotly debated [1]. I'm pretty > sure you could add a bit of JavaScript to your site customizations to show > the #modify div on page load [2]. > > [1] http://trac.edgewall.org/ticket/9807 > [2] > http://trac.edgewall.org/wiki/TracInterfaceCustomization#SiteAppearance > http://trac.edgewall.org/ticket/9807#comment:18 I'll try the updated site.html. Thank you Lucas http://trac.edgewall.org/ticket/9807#comment:18 -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/groups/opt_out.
