Re: line 10866: assertion failed (svn_dirent_is_absolute(local_abspath))
> https://subversion.apache.org/mailing-lists.html Sent from Yahoo Mail for iPhone On Tuesday, August 4, 2020, 17:26, Laurentiu Nicula wrote: Hi, I do not have a reproduction script as the bug happens only from Visual Studio using VisualSVN * Does the problem occur when you select folders of those two projects in Windows File Explorer, right-click and select the SVN Commit button? No, it does not happen if I select from Explorer. In Explorer I can only select the entire folder or sub-folders at the same level. I never got this error using SVN from Explorer. The error happens right after the Tortoise UI is displayed, with no user interaction. This is the command line (extracted with Process Explorer)"C:\Program Files\TortoiseSVN\bin\TortoiseProc.exe" /command:commit /pathfile:"s:\temp\tmp69AE.tmp" /deletepathfile /hwnd:5088E I should note that that temp file does not exist but there are no changes to commit so that may be why. See Below the folder structure. I found out that once I removed the two projects (Folder4 and Folder5) from the solution, I could commit the entire solution. Proj1 and Proj2 - FailsProj1 and Proj3- Fails Proj2 and Proj3- OK -RootFolder -Folder2 (Proj1) -Folder3 -Folder4 (Proj2) -Folder5 (Proj3) Regards,Laurentiu Nicula On Tue, Aug 4, 2020 at 2:39 PM Pavel Lyalyakin wrote: Hello Laurentiu, On Wed, Aug 5, 2020 at 12:11 AM Laurentiu Nicula wrote: > > First time user here, please CC me if any reply. > > Using Visual Studio 2019 Community, VisualSVN extension 7.2.0 and Tortoise > 1.14.0 build 28885 > > It worked well for a while but now it is throwing this error when selecting > certain projects from the solution for a commit. I managed to find a pair of > projects that reliably throw the error every time I select them and click > commit. Each one on its own does not throw the error. > Also doing a commit from Explorer (outside VS2019) works fine. > > --- > 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.14.0\ext\subversion\subversion\libsvn_wc\wc_db.c' > line 10866: assertion failed (svn_dirent_is_absolute(local_abspath)) > --- > OK > --- > > Regards, > Laurentiu Nicula Thank you for the report. Could you please show us a reproduction script? I think that the answers to these questions can also help. * Does the problem occur when you select folders of those two projects in Windows File Explorer, right-click and select the SVN Commit button? * What is the layout of your Visual Studio solution and the Subversion working copy? * Are all the projects contained within a single working copy? Or is your solution contained within several working copies? * Do you select projects in the Solution Explorer, right-click, and then select Commit? What exactly happens at this time? Do you receive the error? Or do you receive the error when you click the OK button on the next dialog? Any other information that could help isolate and reproduce this issue would be much appreciated. -- With best regards, Pavel Lyalyakin VisualSVN Team
Re: line 10866: assertion failed (svn_dirent_is_absolute(local_abspath))
Hi, I do not have a reproduction script as the bug happens only from Visual Studio using VisualSVN * Does the problem occur when you select folders of those two projects in Windows File Explorer, right-click and select the SVN Commit button? No, it does not happen if I select from Explorer. In Explorer I can only select the entire folder or sub-folders at the same level. I never got this error using SVN from Explorer. The error happens right after the Tortoise UI is displayed, with no user interaction. This is the command line (extracted with Process Explorer) "C:\Program Files\TortoiseSVN\bin\TortoiseProc.exe" /command:commit /pathfile:"s:\temp\tmp69AE.tmp" /deletepathfile /hwnd:5088E I should note that that temp file does not exist but there are no changes to commit so that may be why. See Below the folder structure. I found out that once I removed the two projects (Folder4 and Folder5) from the solution, I could commit the entire solution. Proj1 and Proj2 - Fails Proj1 and Proj3 - Fails Proj2 and Proj3 - OK -RootFolder -Folder2 (Proj1) -Folder3 -Folder4 (Proj2) -Folder5 (Proj3) Regards, Laurentiu Nicula On Tue, Aug 4, 2020 at 2:39 PM Pavel Lyalyakin < pavel.lyalya...@visualsvn.com> wrote: > Hello Laurentiu, > > On Wed, Aug 5, 2020 at 12:11 AM Laurentiu Nicula > wrote: > > > > First time user here, please CC me if any reply. > > > > Using Visual Studio 2019 Community, VisualSVN extension 7.2.0 and > Tortoise 1.14.0 build 28885 > > > > It worked well for a while but now it is throwing this error when > selecting certain projects from the solution for a commit. I managed to > find a pair of projects that reliably throw the error every time I select > them and click commit. Each one on its own does not throw the error. > > Also doing a commit from Explorer (outside VS2019) works fine. > > > > --- > > 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.14.0\ext\subversion\subversion\libsvn_wc\wc_db.c' > > line 10866: assertion failed (svn_dirent_is_absolute(local_abspath)) > > --- > > OK > > --- > > > > Regards, > > Laurentiu Nicula > > Thank you for the report. Could you please show us a reproduction script? > > I think that the answers to these questions can also help. > > * Does the problem occur when you select folders of those two projects > in Windows File Explorer, right-click and select the SVN Commit > button? > * What is the layout of your Visual Studio solution and the Subversion > working copy? > * Are all the projects contained within a single working copy? Or is > your solution contained within several working copies? > * Do you select projects in the Solution Explorer, right-click, and > then select Commit? What exactly happens at this time? Do you receive > the error? Or do you receive the error when you click the OK button on > the next dialog? > > Any other information that could help isolate and reproduce this issue > would be much appreciated. > > > -- > With best regards, > Pavel Lyalyakin > VisualSVN Team >
Re: line 10866: assertion failed (svn_dirent_is_absolute(local_abspath))
Hello Laurentiu, On Wed, Aug 5, 2020 at 12:11 AM Laurentiu Nicula wrote: > > First time user here, please CC me if any reply. > > Using Visual Studio 2019 Community, VisualSVN extension 7.2.0 and Tortoise > 1.14.0 build 28885 > > It worked well for a while but now it is throwing this error when selecting > certain projects from the solution for a commit. I managed to find a pair of > projects that reliably throw the error every time I select them and click > commit. Each one on its own does not throw the error. > Also doing a commit from Explorer (outside VS2019) works fine. > > --- > 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.14.0\ext\subversion\subversion\libsvn_wc\wc_db.c' > line 10866: assertion failed (svn_dirent_is_absolute(local_abspath)) > --- > OK > --- > > Regards, > Laurentiu Nicula Thank you for the report. Could you please show us a reproduction script? I think that the answers to these questions can also help. * Does the problem occur when you select folders of those two projects in Windows File Explorer, right-click and select the SVN Commit button? * What is the layout of your Visual Studio solution and the Subversion working copy? * Are all the projects contained within a single working copy? Or is your solution contained within several working copies? * Do you select projects in the Solution Explorer, right-click, and then select Commit? What exactly happens at this time? Do you receive the error? Or do you receive the error when you click the OK button on the next dialog? Any other information that could help isolate and reproduce this issue would be much appreciated. -- With best regards, Pavel Lyalyakin VisualSVN Team
Re: Possible bug: "Searching tree conflict details" takes forever
Thanks Stefan. --accept=postpone sounds like just what I need. I ended up discovering that if I committed an empty directory in the location of the conflict, it would skip the deep history search, and show a different tree conflict right away. So that got me out of waiting. But I'll try --accept=postpone next time. You're right — I removed most of the real merge results from my example. I don't think I'm going to be able to create a reproducible repository, unfortunately (it's proprietary). Jacob > On Aug 4, 2020, at 1:51 PM, Stefan Sperling wrote: > > On Tue, Aug 04, 2020 at 06:37:07PM +, Jacob Weber wrote: >> Hi there. I'm doing a merge which seems to be doing a very long-running >> operation (over an hour so far) when it gets to the "Searching tree conflict >> details" step. I'm wondering if there's any way to avoid this. >> >> I'm merging from a branch X where a directory was removed, into a branch Y >> where that same directory was removed. In each case, the removal was >> actually done as part of a reintegrate merge from a different branch. >> >> I can reproduce this every time I revert and restart the merge. >> Unfortunately I can't share the content of my repository. >> >> The output is something like this: >> >> $ cd branchY >> $ svn update >> $ svn merge ^/branchX >> --- Recording mergeinfo for merge of r1 through r2 into '.': >> U . >> --- Merging r20001 through r20100 into '.': >> Afoo >> Abar >> G . >> --- Recording mergeinfo for merge of r20001 through r20100 into '.': >> G . >> Summary of conflicts: >> Text conflicts: 2 >> Tree conflicts: 7 > > The above per-path output shows no new conflicts. I suppose you were actually > seeing lines such as "Cfoo" somewhere, and they are just missing from > your example? > >> Searching tree conflict details for 'path/to/conflict/dir' in repository: >> Checking r9000... >> >> At this point it slowly starts decreasing the revision after "Checking". But >> it seems to be going through my entire repository history, which will take >> forever. >> >> Is there any way to avoid this? > > Yes. The option: --accept=postpone > for svn merge will bypass the conflict resolver and flag a tree conflict > in the working copy. > > This conflict still needs to be resolved before the merge result can be > committed. Note that 'svn resolve' will try to scan history again, so you > will need to use some non-interactive variant of this command. > > If one of the --accept option paremeters achieve the result you want to > resolve to, then you could use --accept with a suitable parameter (see > the output of 'svn help resolve' for a list). > > Otherwise, use this command to simply clear the conflict marker: > svn resolve --accept=working path/to/conflict/dir > And then resolve the actual conflict manually as required. > >> Mac OS 10.14.6 >> SVN client 1.14.0, compiled Jul 4 2020, 20:57:11 on >> x86_64-apple-darwin18.7.0 >> SVN server 1.8.13 > > Some conflicts may be avoided if the server was upgraded to SVN 1.10 or later. > Newer servers can help with avoiding some tree conflicts. > See for example, see https://svn.apache.org/r1760570 -- this bug should > affect you since it was first fixed in 1.9.5. Though I doubt it is related > to your problem at hand since it looks like your conflict is on a directory > rather than a file. > > Unfortunately, deep history crawls cannot always be avoided. Since information > shown by the resolver can save people a lot of time trying to figure out what > happened, it is considered acceptable that the resolver may take a while to > obtain this information. > > Of course, an hour is outside of this acceptable scope. There could also be > a bug to fix in this case. We've found and fixed similar problems before, > for example here: https://svn.apache.org/r1839662 (this particular problem > does *not* affect you since are using a 1.14 client). > But in order to figure this out we'd need a lot more information from you. > Ideally, a script which starts off with an empty repository, populates it > (with deep history if necessary), and then runs a series of SVN commands > which ends in a merge that triggers the problem. > > Cheers, > Stefan >
line 10866: assertion failed (svn_dirent_is_absolute(local_abspath))
First time user here, please CC me if any reply. Using Visual Studio 2019 Community, VisualSVN extension 7.2.0 and Tortoise 1.14.0 build 28885 It worked well for a while but now it is throwing this error when selecting certain projects from the solution for a commit. I managed to find a pair of projects that reliably throw the error every time I select them and click commit. Each one on its own does not throw the error. Also doing a commit from Explorer (outside VS2019) works fine. --- 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.14.0\ext\subversion\subversion\libsvn_wc\wc_db.c' line 10866: assertion failed (svn_dirent_is_absolute(local_abspath)) --- OK --- Regards, Laurentiu Nicula
Re: Possible bug: "Searching tree conflict details" takes forever
On Tue, Aug 04, 2020 at 06:37:07PM +, Jacob Weber wrote: > Hi there. I'm doing a merge which seems to be doing a very long-running > operation (over an hour so far) when it gets to the "Searching tree conflict > details" step. I'm wondering if there's any way to avoid this. > > I'm merging from a branch X where a directory was removed, into a branch Y > where that same directory was removed. In each case, the removal was actually > done as part of a reintegrate merge from a different branch. > > I can reproduce this every time I revert and restart the merge. Unfortunately > I can't share the content of my repository. > > The output is something like this: > > $ cd branchY > $ svn update > $ svn merge ^/branchX > --- Recording mergeinfo for merge of r1 through r2 into '.': > U . > --- Merging r20001 through r20100 into '.': > Afoo > Abar > G . > --- Recording mergeinfo for merge of r20001 through r20100 into '.': > G . > Summary of conflicts: > Text conflicts: 2 > Tree conflicts: 7 The above per-path output shows no new conflicts. I suppose you were actually seeing lines such as "Cfoo" somewhere, and they are just missing from your example? > Searching tree conflict details for 'path/to/conflict/dir' in repository: > Checking r9000... > > At this point it slowly starts decreasing the revision after "Checking". But > it seems to be going through my entire repository history, which will take > forever. > > Is there any way to avoid this? Yes. The option: --accept=postpone for svn merge will bypass the conflict resolver and flag a tree conflict in the working copy. This conflict still needs to be resolved before the merge result can be committed. Note that 'svn resolve' will try to scan history again, so you will need to use some non-interactive variant of this command. If one of the --accept option paremeters achieve the result you want to resolve to, then you could use --accept with a suitable parameter (see the output of 'svn help resolve' for a list). Otherwise, use this command to simply clear the conflict marker: svn resolve --accept=working path/to/conflict/dir And then resolve the actual conflict manually as required. > Mac OS 10.14.6 > SVN client 1.14.0, compiled Jul 4 2020, 20:57:11 on x86_64-apple-darwin18.7.0 > SVN server 1.8.13 Some conflicts may be avoided if the server was upgraded to SVN 1.10 or later. Newer servers can help with avoiding some tree conflicts. See for example, see https://svn.apache.org/r1760570 -- this bug should affect you since it was first fixed in 1.9.5. Though I doubt it is related to your problem at hand since it looks like your conflict is on a directory rather than a file. Unfortunately, deep history crawls cannot always be avoided. Since information shown by the resolver can save people a lot of time trying to figure out what happened, it is considered acceptable that the resolver may take a while to obtain this information. Of course, an hour is outside of this acceptable scope. There could also be a bug to fix in this case. We've found and fixed similar problems before, for example here: https://svn.apache.org/r1839662 (this particular problem does *not* affect you since are using a 1.14 client). But in order to figure this out we'd need a lot more information from you. Ideally, a script which starts off with an empty repository, populates it (with deep history if necessary), and then runs a series of SVN commands which ends in a merge that triggers the problem. Cheers, Stefan
Possible bug: "Searching tree conflict details" takes forever
Hi there. I'm doing a merge which seems to be doing a very long-running operation (over an hour so far) when it gets to the "Searching tree conflict details" step. I'm wondering if there's any way to avoid this. I'm merging from a branch X where a directory was removed, into a branch Y where that same directory was removed. In each case, the removal was actually done as part of a reintegrate merge from a different branch. I can reproduce this every time I revert and restart the merge. Unfortunately I can't share the content of my repository. The output is something like this: $ cd branchY $ svn update $ svn merge ^/branchX --- Recording mergeinfo for merge of r1 through r2 into '.': U . --- Merging r20001 through r20100 into '.': Afoo Abar G . --- Recording mergeinfo for merge of r20001 through r20100 into '.': G . Summary of conflicts: Text conflicts: 2 Tree conflicts: 7 Searching tree conflict details for 'path/to/conflict/dir' in repository: Checking r9000... At this point it slowly starts decreasing the revision after "Checking". But it seems to be going through my entire repository history, which will take forever. Is there any way to avoid this? Mac OS 10.14.6 SVN client 1.14.0, compiled Jul 4 2020, 20:57:11 on x86_64-apple-darwin18.7.0 SVN server 1.8.13
