error hunting

Hi all, I have a simple request.

For the last week, I've been working on improving our error system.
In olden days, if the server produced an error, the details would get
logged but neon wasn't able to tell the user anything more than "my
request failed." But now we have a system whereby mod_dav_svn can
marshall full svn_error_t's back to libsvn_ra_dav. From here out,
it's just a matter of making *use* of this system everywhere we can.

I've hunted down some of the most common network error-messages and
fixed them with the new system. But I'm sure there are many more.

Rather than hunt for more, I'm now going to join my comrades in the
crusade to squash memory consumption bugs -- it's the highest priority
for our next milestone.

In the meantime, if you see a cryptic network error, can you tell
us/me about it? Post it to the list?

(Keep in mind that our own server, svn.collab.net, hasn't been
upgraded to use the new mod_dav/mod_dav_svn yet, so it's still going
to throw cryptic errors. Nevertheless, if you tell me what you see,
I'll know if I already fixed it. Even better would be to hear about
errors that you're seeing with the absolute latest httpd and svn on
your own machine!)

Thanks,

Ben

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Mar 7 15:44:00 2002