I had a similar (?) problem recently.
I had a large repo with more than 100 000 files, and I would create an overflow when I tried to update other than “full” because there seems to be a list of files sent
as one request, and the server has a size limit for this type of requests. I could update only in parts.
If the revision graph routine requests the full log, the reply can not be split into parts and the reply size is limited to x MBytes, one day the log will exceed that and will be truncated or not sent at all?
Hartmut
--
You received this message because you are subscribed to the Google Groups "TortoiseSVN" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
tortoisesvn...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/4b9b6292-e3aa-462d-a80a-566adabd19ac%40googlegroups.com.
I'm still suffering from this problem.To analyze it, I have opened Wireshark to see the network traffic to/from the SVN server which is going over Apache.When I type "svn log" in a command prompt then i will get all logs. They are coming in chunks some 5 or 10 seconds apart (is this normal?) and this can be seen also in Wireshark.
When trying to show the revision graph from TortoiseSVN there is some traffic observable in Wireshark in the beginning but then nothing is coming until the connection timed out.
Does TortoiseSVN issue the "svn log" command to retrieve the info for the revision graph? Is it possible to make the request string from TortoiseSVN to the server visible? In DebugView i can see "CSVNLogQuery::Log(line 412) svn_client_log5". I would assume in Wireshark I can't see the request as it is a TLS connection.