[EMAIL PROTECTED] wrote: > On Nov 13, 12:43 pm, "Emmanuel Blot" <[EMAIL PROTECTED]> wrote: > >>> would it make sense that trac automatically resyncs, if it already >>> knows that a resync would be necessary? >>> >> I see at least one issue: >> resync can take a very long time to complete, far longer than a >> typical web request timeout... >> > > and the problem would be what? the "of course i like stack trace much > more, it is so helpful. i know immediately something is broken and i > can better bother the admin who then has to log in and start it on the > command line. and of course other users as well should get this > informative stack trace until the resync has completed" ? >
That stack trace is long gone (early 0.11dev days if I recall correctly) and now Trac remains perfectly usable in the meantime, as only a warning is shown. Please stop bothering us with deficiencies of Trac *0.10.x* that we fixed long time ago. I don't really see the point of asking for improvements and at the same time keep using outdated versions. -- Christian --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
