[prev in list] [next in list] [prev in thread] [next in thread] 

List:       subversion-issues
Subject:    [Issue 472] New - "svn up" fails if too much svndiff data received
From:       issues () subversion ! tigris ! org
Date:       2001-08-31 0:20:45
[Download RAW message or body]

http://subversion.tigris.org/issues/show_bug.cgi?id=472

*** shadow/issues_15/472	Thu Aug 30 17:20:45 2001
--- shadow/issues_15/472.tmp.16647	Thu Aug 30 17:20:45 2001
***************
*** 0 ****
--- 1,31 ----
+ +============================================================================+
+ | "svn up" fails if too much svndiff data received                           |
+ +----------------------------------------------------------------------------+
+ |      Issue #: 472                       Component: subversion              |
+ |       Status: NEW                         Version: current                 |
+ |   Resolution:                            Platform: All                     |
+ |   Issue type: DEFECT                   OS/Version: All                     |
+ |     Priority: P1                     Subcomponent: src                     |
+ +----------------------------------------------------------------------------+
+ |  Assigned To: issues@subversion.tigris.org                                 |
+ |  Reported By: kfogel@tigris.org                                            |
+ |      CC list: Cc:                                                          |
+ +----------------------------------------------------------------------------+
+ |    Milestone: TargetMilestone: ---                                         |
+ |          URL:                                                              |
+ +============================================================================+
+ |                              DESCRIPTION                                   |
+ Suppose you have a working copy at revision 866, and the repos is now at
+ revision 1000 (i.e., a typical mass-commit scenario).  If you try to
+ update from the top of your working copy, it will fail.  Neon complains
+ "unable to read chunked response".  If you go down to a subdir and update
+ one file at a time, or a small subdir at a time, the updates will succeed.
+ If you do enough of these, then you'll eventually be able to finish off
+ the update by updating from a higher directory, because now there will
+ be much less svndiff data coming down the pike (at least, that's our
+ conjecture as to the reason, but the symptoms point to a firm correlation
+ between amount of diff data and likelihood of update failure).
+ 
+ This is, just barely, not an M3 bug.  People can do their updates in
+ pieces for a while, if necessary.  But it will be painful, hence the
+ P1 priority.
\ No newline at end of file

[prev in list] [next in list] [prev in thread] [next in thread]