Ops, today with the new Monotone 0.42 I always get an interesting new message "peer [...] IO failed in confirmed state (success)" during NETSYNC, although the NETSYNC revision transfer seems to work still fine:
$ mtn sync mtn: connecting to ssh://[email protected]/openpkg-framework/ mtn: finding items to synchronize: mtn: certificates | keys | revisions mtn: 5798 | 2 | 1929 mtn: bytes in | bytes out | certs out | revs out mtn: 4.5 k | 6.4 k | 4/4 | 1/1 mtn: peer ssh://[email protected]/openpkg-framework/ IO failed in confirmed state (success) mtn: successful exchange with ssh://[email protected]/openpkg-framework/ $ mtn sync mtn: connecting to ssh://[email protected]/openpkg-framework/ mtn: finding items to synchronize: mtn: certificates | keys | revisions mtn: 5798 | 2 | 1929 mtn: peer ssh://[email protected]/openpkg-framework/ IO failed in confirmed state (success) mtn: successful exchange with ssh://[email protected]/openpkg-framework/ mtn: bytes in | bytes out | revs in mtn: 934 | 943 | 0/0 $ mtn sync mtn: connecting to ssh://[email protected]/openpkg-framework/ mtn: finding items to synchronize: mtn: certificates | keys | revisions mtn: 5798 | 2 | 1929 mtn: peer ssh://[email protected]/openpkg-framework/ IO failed in confirmed state (success) mtn: successful exchange with ssh://[email protected]/openpkg-framework/ mtn: bytes in | bytes out | revs in mtn: 934 | 943 | 0/0 As you can see, on the first "mtn sync", my new revision was synced upstream just fine, although I got this message. So, is this just a strange message (because of the "failed" + "success" info) in Monotone 0.42 or is there really a problem somewhere? The NETSYNC peer is still running Monotone 0.41, BTW... Ralf S. Engelschall [email protected] www.engelschall.com _______________________________________________ Monotone-devel mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/monotone-devel
