Myria writes:
> I just found out that the file causing the error from the large commit
> is not the large file - it's one of the smaller files, about 55 KB.
> If I commit that single smaller file from the large commit, it errors
> the same way as the original 227185 would. This is exactly like t
Daniel Shahaf wrote on Fri, Mar 02, 2018 at 22:57:51 +:
> Myria wrote on Mon, Feb 26, 2018 at 13:41:05 -0800:
> > In other news, unknown whether related to the current problem, my
> > attempt to clone the repository to my local computer is failing:
> >
> > D:\>svnsync sync file:///d:/svnclone
Myria wrote on Thu, Mar 01, 2018 at 18:45:38 -0800:
> Also, I have no control over what was in the repository five years
> ago. The huge files were compiled versions of WebKit libraries.
Note that in 2017, WebKit intentionally committed a SHA-1 collision into their
repository. If you have the We
Myria wrote on Mon, Feb 26, 2018 at 13:41:05 -0800:
> In other news, unknown whether related to the current problem, my
> attempt to clone the repository to my local computer is failing:
>
> D:\>svnsync sync file:///d:/svnclone
> Transmitting file data
> ...
The problem is identical on Windows command line, Windows TortoiseSVN,
Ubuntu-Linux, Ubuntu-Linux on Windows, and macOS. I'm just bad at
GDB.
On Thu, Mar 1, 2018 at 9:09 PM, Nico Kadel-Garcia wrote:
> On Thu, Mar 1, 2018 at 10:25 PM, Myria wrote:
>> I just found out that the file causing the er
On Thu, Mar 1, 2018 at 11:52 PM, NOCERA, ANDY wrote:
> I disabled ssl to simplify. I noticed that svn log sometimes stops with an
> error, sometimes it just stops although there is an error in the log. I
> think I need to review the build.Not sure if it’s the SVN side of the
> build or the
