[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

error not passed to clients

From: SteveKing <steveking_at_gmx.ch>
Date: 2003-09-02 19:39:12 CEST

Hi,

yesterday I updated subversion to HEAD and spent this day
adjusting TSVN to work with the new status-API and the
new prompting providers (btw: a big thanks for those!).

Now I'm at testing some functions and found the following:
If I'm asking for a status with "update" set to true (something
like 'svn st -u') on a https:// repository, then the prompting
provider asked me (as it should) if I wanted to accept the
unknown certificate. If I say yes everything is ok, but if
I say no then the function still returns a valid status, just
all remote statuses are set as "deleted". Even if I create
a subversion error and return that in the prompting
callback the function succeeds.

There's no way for me to check if the function was
successful or if it failed (because of the not accepted
certificate) since that error isn't passed through to
the client.

It does this with the command line client too, but
since the client doesn't show the remote status in
detail but just an asterisk it doesn't matter that much.

Is it possible to pass such errors to clients?

Stefan

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Sep 2 19:40:58 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.