Am 14.04.2010 12:49, schrieb Christian Boos:
Christopher specifically asked for help for *one* ticket (#370), but nobody seems to care so far and this tells a lot.
I'd like to add that I spent 3-4 hours debugging that issue (as it was a problem we found in Agilo). I have a couple of (too complicated) unit tests that uncover the issue.
The problem exists in the generic strategy. The strange thing is that a callable is returned from a method and this callable uses a local variable of that method (basically some extra state for the callable). This extra state is a stack which underflows due to an unknown condition.
The problem which seem to overwhelm my python foo/debugging capabilities is that the problem was introduced in a mass-merge of GSOC work.
If someone of you plans on tackling the issue, please ping me. I'm willing to help with code+debugging. However it's pretty frustrating tackling the thing alone and running against wall every time...
Besides that I think I have another problematic regression in Genshi 0.6 which might be only a test ordering issue.
fs -- You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en.
