On Tue, Dec 13, 2022 at 6:11 PM Don Newbold (GSC) <d...@generalstandards.com> wrote: > > I've received notice of an assertion upon committing some files. > > The assertion was via a dialog box, which is shown in the attached > image. The text of the dialog box is as follows - the Ctrl-C > > > > --------------------------- > 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_subr\subst.c' > line 724: assertion failed (STRING_IS_EOL(newline_buf, newline_len)) > --------------------------- > OK > --------------------------- > > > > WHAT I WAS DOING: > > I was committing several files spread across several directories. This > included .doc files, .docx files and a .txt files. The dialog box > appeared while the .txt file was being processed (based on commit > failure status text). I have many, many times over the years seen > similar commit request fail because of newline inconsistencies with the > .txt file. Upon using dos2unix on the .txt file, the commit normally > goes through to successful completion. I applied dos2unix this time and > the commit completed successfully. > > > > CLIENT HOST: > > Edition Windows 10 Pro (64-bit) > Version 21H2 > Installed on 8/2/2021 > OS build 19044.1889 > Experience Windows Feature Experience Pack 120.2212.4180.0 > > > > CLIENT SOFTWARE > > TortoiseSVN 1.14.0, Build 28885 - 64 Bit , 2020/05/24 13:32:45 > ipv6 enabled > Subversion 1.14.0, -release > apr 1.6.5 > apr-util 1.6.1 > serf 1.3.9 > OpenSSL 1.1.1g 21 Apr 2020 > zlib 1.2.11 > SQLite 3.29.0 > > > > SERVER HOST: > > Edition Windows 10 Pro (64-bit) > Version 21H2 > Installed on 8/16/2022 > OS build 19044.2251 > Experience Windows Feature Experience Pack 120.2212.4180.0 > > > > SERVER SOFTWARE: > > VisualSVN Server Version 5.0.2 > Subversion 1.14.2 > Apache 2.4.53 > > > > > -- > Don Newbold > 256-880-8787, x110 > General Standards
Hi Don, Thank you for the detailed error report. Since you've experienced this error before with .TXT files and the issue appears somehow related to line endings, do you by chance have any svn properties set on the file? In particular, does it have "svn:eol-style", "svn:mime-type", or "svn:keywords" properties? If so, what are these property values? Do you have any other properties set which may seem significant to this issue? To check for property values: If you are using TortoiseSVN, you should be able to right-click the file in Explorer to get the context menu and then TortoiseSVN -> Properties. Alternatively if you have the command line "svn" client, you could check whether the file has properties with: svn proplist FILENAME.TXT and if that shows anything, show the property values with: svn propget svn:eol-style FILENAME.TXT svn propget svn:mime-type FILENAME.TXT etc. Cheers, Nathan
