internal malfunction libsvn_wc\wc_db.c line 10189

["James G. Bunger" <jb...@starrett.com>]

Hi,

I was trying to commit a set of changes that included copying an existing set of folders to two new sets.  Basically creating two new projects from an existing one.  I had gotten a series of failures to commit due to "Non-recursive commit of moved/renamed folder" messages.
This is with Windows 10 64 bit over a VPN connection and using TortoiseSVN.

---------------------------
Subversion Exception!
---------------------------
Subversion encountered a serious problem.
Please take the time to report this on the Subversion mailing list
with as much information as possible about what
you were trying to do.
But please first search the mailing list archives for the error message
to avoid reporting the same problem repeatedly.
You can find the mailing list archives at
https://subversion.apache.org/mailing-lists.html

Subversion reported the following
(you can copy the content of this dialog
to the clipboard using Ctrl-C):

In file
'D:\Development\SVN\Releases\TortoiseSVN-1.13.1\ext\subversion\subversion\libsvn_wc\wc_db.c'
line 10189: internal malfunction
---------------------------
OK
---------------------------

James G. Bunger
Firmware Engineer
[Starrett Logo]
The L.S. Starrett Company
121 Crescent Street
Athol, MA 01331
978-249-3551  x470
JBunger@Starrett.com<ma...@Starrett.com>

Re: internal malfunction libsvn_wc\wc_db.c line 10189

[Nathan Hartman <ha...@gmail.com>]

On Tue, Feb 16, 2021 at 5:48 PM James G. Bunger <jb...@starrett.com>
wrote:

> Hi,
>
>
>
> I was trying to commit a set of changes that included copying an existing
> set of folders to two new sets.  Basically creating two new projects from
> an existing one.  I had gotten a series of failures to commit due to
> “Non-recursive commit of moved/renamed folder” messages.
>
> This is with Windows 10 64 bit over a VPN connection and using TortoiseSVN.
>
>
Hi,

Thanks for reporting this.

Did the series of "non-recursive commit" failures you mentioned occur
within the same commit that failed, or during earlier work?

Also, in the commit that failed, were there also some moves, renames, or
deletes, either in the folders you were copying or in other parts of the
working copy?

To work around the issue:

Is it feasible to checkout a fresh working copy and retry the copy and
commit?

Alternatively, would it be acceptable to make the copies as server-side
copies?

Please let us know if you need help with any of the above.

Thanks again,
Nathan