On Mon, Apr 13, 2009 at 12:40:32 -0400, Gwern Branwen wrote: > Yes, that looks like the compression bug. The easy diagnosis is > whether 'curl' fails and 'curl --compressed' succeeds.
I can confirm with this diagnosis as well. > Supposedly, it's fixed in happstack-server darcs: > http://groups.google.com.gi/group/HAppS/browse_thread/thread/419a012cdc60cd47 > > But as I comment in a gitit-devel thread, I rebuilt from darcs > everything, and the compressed issue didn't seem to go away. Another issue we have is performance. Loading http://test.darcs.net seems to take about 15s wall time for me. Ian has helped us to figure out what's going on and after some silly ps-usage on my part, we've worked out that one thing it seems to be doing is darcs changes --xml-output --summary FrontPage.page which took 3 seconds wall time on test.darcs.net I suppose this is something that will be helped with the new filecache feature that Benedikt's been working on. But otherwise, why is it doing that? Is it possible to have an overview of what happens darcs-wise when we call up a page in gitit? -- Eric Kow <http://www.nltg.brighton.ac.uk/home/Eric.Kow> PGP Key ID: 08AC04F9
signature.asc
Description: Digital signature
_______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
