[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

AW: E175012 and E175002 when trying to commit

From: Christoph Vogtländer <Christoph.Vogtlaender_at_sigma-surface-science.com>
Date: Wed, 3 Apr 2019 08:35:02 +0000

> Von: Johan Corveleyn [mailto:jcorvel_at_gmail.com]
> Gesendet: Mittwoch, 3. April 2019 10:18
> Perhaps the difference between your first and second attempt is not
> caused by different language settings, but because the working copy
> was in a different state? For instance, if the "base" of your working
> copy is full of mixed revisions, and you're committing a lot of
> changes on top of that, the "edit report" that's sent by the client to
> the server can be much larger (thus hitting some limit on the server).
> Maybe try to execute another 'svn update' on your entire working copy
> so it gets a uniform revision.

No, I don't think so. I'm using a fresh check-out on the branch, there
should be no mixed revisions.
And this issue is reproducible. Running with de_DE.UTF-8 will always try to
send the data, using en_GB.UTF-8 will fail straight away with
'Request Entity Too Large' error. I run these commands in the same local
working copy. Nothing else in between (like cleanup etc.)

> Just another hint to get you started: the client-side timeout can be
> found in the file ~/.subversion/servers on your client machine. Look
> for "http-timeout = ..." (the default is 60 (seconds) I believe).

Nothing set on the client side. The server defines a timeout of 300. When using
de_DE.UTF-8 the commit fails after over 90 Minutes. So this settings does not
seem to be related. But, I will try to increase the timeout and check if that helps.

> Though I would seriously recommend splitting up your huge commit into
> several commits. Perhaps find some logical blocks, or split by
> subdirectories, or ... Huge commits can be a pain later on, for
> instance because every time you query the 'svn log' for one of those
> files later, this huge commit will be part of the result (part of its
> history), and with the '-v' (verbose) option 'svn log' will show all
> the affected paths, which will be huge ...

Unfortunately, this is an import from 3rd party. So, there are no logical blocks.
I might be able to commit on sub-folder after the other. But, I need to merge
this into trunk later which will then be a lot of hassle and error prone.

I will try to commit in a single commit after adapting the server configuration
(Timeout, LimitXMLRequestBody), first.

Sigma Surface Science GmbH, Idsteiner Str. 78, 65232 Taunusstein. Amtsgericht Wiesbaden, HRB 27422. Geschäftsführer: Norbert Nold
Received on 2019-04-03 10:35:26 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.