On Sat, 2006-07-15 at 17:42 -0700, Eric Anderson wrote:
> When I attempt to pull from venge.net, if I don't have any key
> specified in my _MTN/options file, everything works fine. If I have a
> key specified, then I get:
>
> mtn: connecting to venge.net
> mtn: finding items to synchronize:
> mtn: certificates | keys | revisions
> mtn: 13977 | 26 | 4625
> mtn: bytes in | bytes out | certs in | revs in
> mtn: 0 | 345 | 0 | 0
> mtn: error: I/O failure while talking to peer venge.net, disconnecting
>
> I have to run mtn with -k "" to force it to do an anonymous pull. It
> would be nice if monotone would automatically fall back to an
> anonymous pull if the non-anonymous one is rejected (which is what I
> assume is leading to the I/O failure, I can't see the log on venge.net
> to verify). If that can't be easily fixed, then updating the error
> message to say something like "if you were trying a pull, try adding
> '-k ""' to your command line" would at least explain to people what
> was going wrong. I only discovered the problem with having a key by
> accident of running mtn pull in a directory without one.
This has been improved somewhat, in that the server now sends an error
message before disconnecting. It's still not a very good error message,
but it's slightly better that what we had before.
Having it retry automatically without a key would be slightly more
involved (the client would need to keep track of when it got the error
message, since all the error message contains is a (localized, I think)
human-readable string), but still doable.
Tim
_______________________________________________
Monotone-devel mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/monotone-devel