windows commands raise an 10054, 'Connection reset by peer' error

I've noticed that is not only with a checkout BUT with every command i do branch, etc...

This appears to be a bug in the network client code on Windows.

This also occurs on a Linux server being used by Windows, but not on the Windows server being used by Linux.

Like I said,
it's maybe a problem of "carriage return + line feed = new line characters in windows" management in bazaar! in linux it's only a line feed = new line, give me a feed back please Adrian.

See same problem when pushing up change over slow link with high latency (U.S. <-> China). OS: Windows Vista + latest service pack.

Connected (version 2.0, client WeOnlyDo)
Authentication (publickey) successful!
Secsh channel 1 opened.
Socket exception: Connection reset by peer (10054)
bzr: ERROR: exceptions.EOFError:

Traceback (most recent call last):
  File "bzrlib\commands.pyo", line 896, in run_bzr_catch_errors
  File "bzrlib\commands.pyo", line 842, in run_bzr
  File "bzrlib\commands.pyo", line 542, in run_argv_aliases
  File "bzrlib\builtins.pyo", line 981, in run
  File "bzrlib\push.pyo", line 160, in _show_push_branch
  File "bzrlib\decorators.pyo", line 138, in read_locked
  File "bzrlib\branch.pyo", line 1970, in push
  File "bzrlib\branch.pyo", line 2681, in _run_with_write_locked_target
  File "bzrlib\branch.pyo", line 2009, in _push_with_bound_branches
  File "bzrlib\branch.pyo", line 2032, in _basic_push
  File "bzrlib\decorators.pyo", line 192, in write_locked
  File "bzrlib\remote.pyo", line 1738, in update_revisions
  File "bzrlib\decorators.pyo", line 192, in write_locked
  File "bzrlib\branch.pyo", line 450, in fetch
  File "bzrlib\remote.pyo", line 824, in fetch
  File "bzrlib\decorators.pyo", line 192, in write_locked
  File "bzrlib\repository.pyo", line 2985, in fetch
  File "bzrlib\repository.pyo", line 2992, in _pack
  File "bzrlib\repofmt\pack_repo.pyo", line 655, in pack
  File "bzrlib\repofmt\pack_repo.pyo", line 830, in _create_pack_from_packs
  File "bzrlib\repofmt\pack_repo.pyo", line 370, in finish
  File "bzrlib\repofmt\pack_repo.pyo", line 293, in _write_data
  File "bzrlib\transport\__init__.pyo", line 268, in write
  File "bzrlib\transport\remote.pyo", line 299, in append_bytes
  File "bzrlib\transport\remote.pyo", line 185, in _call_with_body_bytes
  File "bzrlib\smart\client.pyo", line 154, in call_with_body_bytes
  File "bzrlib\smart\client.pyo", line 76, in _call_and_read_response
  File "bzrlib\smart\client.pyo", line 51, in _send_request
  File "bzrlib\smart\protocol.pyo", line 1206, in call_with_body_bytes
  File "bzrlib\smart\protocol.pyo", line 1104, in _write_end
  File "bzrlib\smart\protocol.pyo", line 1071, in flush
  File "bzrlib\smart\medium.pyo", line 378, in accept_bytes
  File "bzrlib\smart\medium.pyo", line 879, in _accept_bytes
  File "bzrlib\smart\medium.pyo", line 729, in _accept_bytes
  File "paramiko\file.pyo", line 314, in write
  File "paramiko\file.pyo", line 435, in _write_all
  File "paramiko\channel.pyo", line 1213, in _write
  File "paramiko\channel.pyo", line 765, in sendall
  File "paramiko\channel.pyo", line 702, in send
  File "paramiko\transport.pyo", line 1405, in _send_user_message
  File "paramiko\transport.pyo", line 1388, in _send_message
  File "paramiko\packet.pyo", line 310, in send_message
  File "paramiko\packet.pyo", line 260, in write_all
EOFError

bzr 1.12 on python 2.5.2 (win32)
arguments: ['bzr', 'push', 'bzr+ssh://ccguoke2.gicp.net/d:/repo/RightDealRightnow']
encoding: 'cp1252', fsenc: 'mbcs', lang: None
plugins:
  bzrtools C:\Program Files\Bazaar\plugins\bzrtools [1.12]
  launchpad C:\Program Files\Bazaar\plugins\launchpad [unknown...

Lucius, your error is different.

UbuntuBoy, this is probably a difference in how windows reports end of file when the client closes down in the way our client closes down ;).

Thanks for the report, sorry I didn't notice it sooner. I believe this was fixed in 1.16. Here's the relevant NEWS entry:

* ``bzr serve`` on Windows no longer displays a traceback simply because a
  TCP client disconnected. (Andrew Bennetts)

Feel free to reopen this bug (or file a new one) if you still see this after upgrading to 1.16 or newer.