Re: assertion failed - svn_direct_is_absolute(local_abspath)

Hi Todd, you are using an ancient TSVN version. Please upgrade to a later one. I just verified that the current TSVN version (1.9.4) is not suffering the issue anymore. > System ran out of resources while composing previous message. Extra > information: > > > > TortoiseSVN version: 1.7.0, Buil

RE: assertion failed - svn_direct_is_absolute(local_abspath)

System ran out of resources while composing previous message. Extra information: TortoiseSVN version: 1.7.0, Build 22068 - 64 Bit , 2011/10/10 09:48:29 Subversion 1.7.0 Apr 1.4.5 Apr-utils 1.3.12 Neon 0.29.6 OpenSSL 1.0.0e 6 Sep 2011 Zlib 1.2.5 Windows 7 Enterprise, Service Pack 1 System ran o

Re: assertion failed (svn_dirent_is_absolute(local_abspath)) TortoiseSVN-1.8.8

Hello, On 02/07/15 11:34, Valeriy Goncharov wrote: > Subversion Exception! > In file > 'D:\Development\SVN\Releases\TortoiseSVN-1.8.8\ext\subversion\subversion\libsvn_wc\wc_db.c' > line 8731: assertion failed (svn_dirent_is_absolute(local_abspath)) Please update to the latest compatible TortoiseS

Re: assertion failed

Nikolas PATTAKOS writes: > My project's dir structure included : > > lib/ > src/TestA > src/TestB > src/... > > and I changed it to > > lib/Tests/A > lib/Tests/B > src/.. We need more precise instructions otherwise we just have to guess exactly what you did. Perhaps: svn co URL wc svn mkdi

Re: assertion failed

On 06/30/2015 11:26 AM, Stefan Sperling wrote: On Mon, Jun 29, 2015 at 01:55:31PM +0200, Nikolas PATTAKOS wrote: Hi, I am running subversion version 1.8.13 (r1667537) on debian testing. I have a number of svn move commands on my computer pending to be submitted and I did an svn update to updat

Re: assertion failed

On Mon, Jun 29, 2015 at 01:55:31PM +0200, Nikolas PATTAKOS wrote: > Hi, > > I am running subversion version 1.8.13 (r1667537) on debian testing. > > I have a number of svn move commands on my computer pending to be submitted > and I did an svn update to update my branch. This resulted in a number

RE: assertion failed / segfault in svn_ra_do_diff3

> -Original Message- > From: Mikhail Veltishchev [mailto:dichlofos...@yandex.ru] > Sent: maandag 23 juni 2014 12:18 > To: Bert Huijben; users@subversion.apache.org > Subject: Re: assertion failed / segfault in svn_ra_do_diff3 > > Oops, my bad! You're absolutely

Re: assertion failed / segfault in svn_ra_do_diff3

Oops, my bad! You're absolutely right, that was 'svn diff' command. And this mistake was the reason of crash 'disappearing': after that I built svn 1.8.9 from sources and got the same crash again, so it is reproducible. Here is a backtrace for `svn diff -r 1403046 ..` invocation: http://pastebin

RE: assertion failed / segfault in svn_ra_do_diff3

> -Original Message- > From: Mikhail Veltishchev [mailto:dichlofos...@yandex.ru] > Sent: vrijdag 20 juni 2014 20:41 > To: users@subversion.apache.org > Subject: assertion failed / segfault in svn_ra_do_diff3 > > I recently caught a segfault / assertion fail in svn client. > > svn, versi

Re: assertion failed (SV_IS_VALID_REVNUM(*youngest))

On Wed, Aug 21, 2013 at 09:44:00AM -0600, Scott Chantry wrote: > TortoiseSVN 1.8.1 windows x64. I opened up repo browser and after a long > wait, this error popped up. I can't do anything with tortoisesvn1.8.1 I believe this will be fixed with Subversion 1.8.3 (ETA end of next week). Please let u

Re: assertion failed (status != svn_wc__db_status_normal)

On Tue, Aug 28, 2012 at 10:02:06AM -0400, Peter Amstutz wrote: > I get the following error when trying to update a checkout. I did a > cleanup of the checkout, but that did not affect the error. The > problem occurs only with one specific checkout, and on > re-downloading out the same repository

Re: Assertion failed!

On Thu, Aug 2, 2012 at 12:34 PM, Alex Jackson wrote: > This keeps popping up when I try running the cleanup command. > > --- > > Subversion Exception! > > --- > > Subversion encountered a serious problem. > > Please take the ti

Re: assertion failed in 1.7.0

Note up front: please take the time to think up a subject. Am 26.04.2012 10:25, schrieb Glenn Hammond: [...] > with as much information as possible about what > you were trying to do. This is important, it basically renders your report useless when missing. > But please first search the mailing

Re: assertion failed (opt || SVN_IS_VALID_REVNUM(rev))

; Last Changed Date: 2012-04-20 19:33:29 -0400 (Fri, 20 Apr 2012) > > > > -Original Message- > From: Daniel Shahaf [mailto:danie...@elego.de] > Sent: Monday, April 23, 2012 1:34 PM > To: Gegerson, Jamie Mr CTR USA USACE > Cc: users@subversion.apache.org > Subject: Re:

Re: assertion failed (opt || SVN_IS_VALID_REVNUM(rev))

Gegerson, Jamie Mr CTR USA USACE wrote on Mon, Apr 23, 2012 at 11:52:06 -0400: > Sending this in because the most recent reference to this failed assertion > occurs in 2010. > > > > Got the following exception when trying to show a revision log range by date > from 2012/01/01 to 2012/04/23. I

Re: Assertion failed with svn diff -r BASE:HEAD ^/trunk

On 04/20/2012 01:06 PM, Stefan Sperling wrote: On Fri, Apr 20, 2012 at 12:39:33PM +0200, Florent Guiliani wrote: Just got this with subversion 1.7.4: $ svn diff -r BASE:HEAD ^/trunk svn: E235000: In file '/build/buildd/subversion-1.7.4/subversion/libsvn_client/diff.c' line 1937: assertion faile

Re: Assertion failed with svn diff -r BASE:HEAD ^/trunk

On Fri, Apr 20, 2012 at 12:39:33PM +0200, Florent Guiliani wrote: > Just got this with subversion 1.7.4: > > $ svn diff -r BASE:HEAD ^/trunk > svn: E235000: In file > '/build/buildd/subversion-1.7.4/subversion/libsvn_client/diff.c' > line 1937: assertion failed (! svn_path_is_url(path2)) > Aborted

Re: Assertion failed with svn diff -r BASE:HEAD ^/trunk

Florent Guiliani writes: > Just got this with subversion 1.7.4: > > $ svn diff -r BASE:HEAD ^/trunk > svn: E235000: In file > /build/buildd/subversion-1.7.4/subversion/libsvn_client/diff.c' line > 1937: assertion failed (! svn_path_is_url(path2)) > Aborted Happens with Subversion trunk as well:

Re: Assertion failed and crash with 1.7.1

On Thu, Nov 17, 2011 at 8:02 PM, Daniel Shahaf wrote: > Johan Corveleyn wrote on Thu, Nov 17, 2011 at 13:55:51 +0100: >> On Thu, Nov 17, 2011 at 1:02 PM, Philip Martin >> wrote: >> > Attila Nagy writes: >> > >> >> On 11/16/11 18:40, Philip Martin wrote: >> >>> Attila Nagy  writes: >> >>> >>

Re: Assertion failed and crash with 1.7.1

Johan Corveleyn wrote on Thu, Nov 17, 2011 at 13:55:51 +0100: > On Thu, Nov 17, 2011 at 1:02 PM, Philip Martin > wrote: > > Attila Nagy writes: > > > >> On 11/16/11 18:40, Philip Martin wrote: > >>> Attila Nagy  writes: > >>> > I use pysvn for this and basically the code looks like this (in

Re: Assertion failed and crash with 1.7.1

On Thu, Nov 17, 2011 at 1:02 PM, Philip Martin wrote: > Attila Nagy writes: > >> On 11/16/11 18:40, Philip Martin wrote: >>> Attila Nagy  writes: >>> I use pysvn for this and basically the code looks like this (in python): def update_perms():      for path in propchg:        

Re: Assertion failed and crash with 1.7.1

On Wed, 16 Nov 2011 17:40:55 +, Philip Martin wrote: ... > It might be faster to run a recursive propget, It might also be erroneous. I noticed in an 1.5/1.6 setup that a recursive propget over a big subtree simply fails to yield *all* relevant properties. That is, a svn pg -R svn:externals

Re: Assertion failed and crash with 1.7.1

Attila Nagy writes: > On 11/16/11 18:40, Philip Martin wrote: >> Attila Nagy writes: >> >>> I use pysvn for this and basically the code looks like this (in python): >>> def update_perms(): >>> for path in propchg: >>> proplist = svn.propget('file:permissions', path) >>> if

Re: Assertion failed and crash with 1.7.1

On 11/16/11 18:40, Philip Martin wrote: Attila Nagy writes: I use pysvn for this and basically the code looks like this (in python): def update_perms(): for path in propchg: proplist = svn.propget('file:permissions', path) if not os.path.islink(path) and proplist.has_key

Re: Assertion failed and crash with 1.7.1

Attila Nagy writes: > I use pysvn for this and basically the code looks like this (in python): > def update_perms(): > for path in propchg: > proplist = svn.propget('file:permissions', path) > if not os.path.islink(path) and proplist.has_key(path): > set_perms(path

Re: Assertion failed and crash with 1.7.1

On 10/27/11 14:57, Mark Phippard wrote: On Thu, Oct 27, 2011 at 8:12 AM, Attila Nagy mailto:b...@fsn.hu>> wrote: ZFS. It it worth to make benchmarks with this WC with 1.6 and 1.7? I so, I can try to find the time for it. There are some pretty easy to run benchmarks you can run to s

Re: Assertion failed and crash with 1.7.1

Attila Nagy writes: > ZFS. > It it worth to make benchmarks with this WC with 1.6 and 1.7? I so, I > can try to find the time for it. There are some reports that a mismatch between SQLite page size and ZFS block size can cause performance problems and that better performance is obtained when the

Re: Assertion failed and crash with 1.7.1

On Thu, Oct 27, 2011 at 8:12 AM, Attila Nagy wrote: > ZFS. > It it worth to make benchmarks with this WC with 1.6 and 1.7? I so, I can > try to find the time for it. > There are some pretty easy to run benchmarks you can run to see if 1.7 is simply slower in your environment. See: https://ctf.

Re: Assertion failed and crash with 1.7.1

On 10/27/11 14:13, Philip Martin wrote: Mark Phippard writes: I would imagine svn upgrade is almost entirely writes and I recall it does quite a few transactions. So couldn't the linear slow down just be based on the growth in the amount of bytes that are written to disk each time? Yes, numb

Re: Assertion failed and crash with 1.7.1

Mark Phippard writes: > I would imagine svn upgrade is almost entirely writes and I recall it does > quite a few transactions. So couldn't the linear slow down just be based on > the growth in the amount of bytes that are written to disk each time? Yes, number of transactions matters a lot. Ho

Re: Assertion failed and crash with 1.7.1

On 10/27/11 12:58, Philip Martin wrote: Attila Nagy writes: On 10/26/11 15:37, Philip Martin wrote: Attila Nagy writes: I'm trying to update a working copy of some tens of GBs with svn 1.7.1 Did you upgrade with 1.7.0 or 1.7.1? I've upgraded the WC with 1.7.0, then switched to 1.7.1, wh

Re: Assertion failed and crash with 1.7.1

On 10/27/11 13:47, Mark Phippard wrote: On Thu, Oct 27, 2011 at 4:47 AM, Attila Nagy > wrote: On 10/26/11 15:37, Philip Martin wrote: Attila Nagy writes: I'm trying to update a working copy of some tens of GBs with svn 1.7.1 Did you

Re: Assertion failed and crash with 1.7.1

On Thu, Oct 27, 2011 at 4:47 AM, Attila Nagy wrote: > On 10/26/11 15:37, Philip Martin wrote: > > Attila Nagy writes: > > > I'm trying to update a working copy of some tens of GBs with svn 1.7.1 > > Did you upgrade with 1.7.0 or 1.7.1? > > I've upgraded the WC with 1.7.0, then switched to 1

Re: Assertion failed and crash with 1.7.1

Attila Nagy writes: > On 10/26/11 15:37, Philip Martin wrote: >> Attila Nagy writes: >> >>> I'm trying to update a working copy of some tens of GBs with svn 1.7.1 >> Did you upgrade with 1.7.0 or 1.7.1? > I've upgraded the WC with 1.7.0, then switched to 1.7.1, which I'm > currently using. > The

Re: Assertion failed and crash with 1.7.1

On Thu, Oct 27, 2011 at 09:53:11AM +, Markus Schaber wrote: > Hi, > > > Von: Attila Nagy [mailto:b...@fsn.hu] > > BTW, with the current (1.7) WC-implementation, what possible problems do > > you see where this would be needed? > > Previously with the per-directory .svn directories it was of

Re: Assertion failed and crash with 1.7.1

On 10/27/11 11:28, Stefan Sperling wrote: On Thu, Oct 27, 2011 at 10:47:51AM +0200, Attila Nagy wrote: On 10/26/11 15:37, Philip Martin wrote: Attila Nagy writes: I'm trying to update a working copy of some tens of GBs with svn 1.7.1 Did you upgrade with 1.7.0 or 1.7.1? I've upgraded the

Re: Assertion failed and crash with 1.7.1

On Thu, Oct 27, 2011 at 10:47:51AM +0200, Attila Nagy wrote: > On 10/26/11 15:37, Philip Martin wrote: > >Attila Nagy writes: > > > >>I'm trying to update a working copy of some tens of GBs with svn 1.7.1 > >Did you upgrade with 1.7.0 or 1.7.1? > I've upgraded the WC with 1.7.0, then switched to 1

Re: Assertion failed and crash with 1.7.1

On 10/26/11 15:37, Philip Martin wrote: Attila Nagy writes: I'm trying to update a working copy of some tens of GBs with svn 1.7.1 Did you upgrade with 1.7.0 or 1.7.1? I've upgraded the WC with 1.7.0, then switched to 1.7.1, which I'm currently using. The upgrade took nearly one week (I can'

Re: Assertion failed and crash with 1.7.1

On 10/26/11 15:31, Mark Phippard wrote: On Wed, Oct 26, 2011 at 5:01 AM, Attila Nagy wrote: I'm trying to update a working copy of some tens of GBs with svn 1.7.1 (upgraded the WC to the new -sadly much slower- format) and always get this: Is your WC on a network drive? That is the only scen

Re: Assertion failed and crash with 1.7.1

Attila Nagy writes: > I'm trying to update a working copy of some tens of GBs with svn 1.7.1 Did you upgrade with 1.7.0 or 1.7.1? > $ svn up > Updating '.': > svn: E235000: In file 'subversion/libsvn_wc/update_editor.c' line > 1582: assertion failed (action == svn_wc_conflict_action_edit || > a

Re: Assertion failed and crash with 1.7.1

On Wed, Oct 26, 2011 at 5:01 AM, Attila Nagy wrote: > I'm trying to update a working copy of some tens of GBs with svn 1.7.1 > (upgraded the WC to the new -sadly much slower- format) and always get this: Is your WC on a network drive? That is the only scenario I have seen where 1.7.x was not si

Re: assertion failed

Davor Barcan writes: > During an update I received the following error: > > In file > 'D:\Development\SVN\Releases\TortoiseSVN-1.7.0\ext\subversion\subversion\libsvn_wc\update_editor.c' > line 2898: assertion failed (status != svn_wc__db_status_normal) > > I did not see that error was reported pr

RE: assertion failed

> -Original Message- > From: Davor Barcan [mailto:davor.bar...@markit.com] > Sent: 25 October 2011 17:52 > To: users@subversion.apache.org > Subject: assertion failed > > During an update I received the following error: > > > > In file > > 'D:\Development\SVN\Releases\TortoiseSVN-1.7

RE: Assertion Failed: workqueue.c

>>> So now we want to see the nodes row for each of those four paths: >>> >>> sqlite3 .svn/wc.db "select * from nodes where >>> local_relpath='X/MONSTER.FMX/MONSTER.FMX.csproj'" >>> sqlite3 .svn/wc.db "select * from nodes where >>> local_relpath='X/MONSTER.FMX/Boxes/gbFMXDisplay.resx'" >>> sqlite

Re: Assertion Failed: workqueue.c

Patrick Quirk writes: Is the sqlite3 utility readily available on Windows? If it is then run: sqlite3 .svn/wc.db "select * from work_queue" >>> >>> Yep, here's the output: >>> 79|(file-install X/MONSTER.FMX/MONSTER.FMX.csproj 1 0 1 1) >>> 80|(file-install X/MONSTER.FMX/Boxes/gbFMXDisp

RE: Assertion Failed: workqueue.c

>>> Is the sqlite3 utility readily available on Windows? If it is then run: >>> sqlite3 .svn/wc.db "select * from work_queue" >> >> Yep, here's the output: >> 79|(file-install X/MONSTER.FMX/MONSTER.FMX.csproj 1 0 1 1) >> 80|(file-install X/MONSTER.FMX/Boxes/gbFMXDisplay.resx 1 0 1 1) >> 81|(file-

Re: Assertion Failed: workqueue.c

Patrick Quirk writes: >> Is the sqlite3 utility readily available on Windows? If it is then run: >> sqlite3 .svn/wc.db "select * from work_queue" > > Yep, here's the output: > 79|(file-install X/MONSTER.FMX/MONSTER.FMX.csproj 1 0 1 1) > 80|(file-install X/MONSTER.FMX/Boxes/gbFMXDisplay.resx 1 0

RE: Assertion Failed: workqueue.c

> Is this a working copy that you checked-out with the old 1.6 Tortoise > and upgraded to 1.7, or is it a working copy that you checked-out with > 1.7? This is a 1.6.17 working copy that was upgraded. > A text-conflict or a tree-conflict? Do you have any local modifications > to the working copy

Re: Assertion Failed: workqueue.c

Patrick Quirk writes: > I upgraded to 1.7 yesterday when the new version of Tortoise came out, > and used it with no issues last evening and today until I encountered > this assertion: > > In file > 'D:\Development\SVN\Releases\TortoiseSVN-1.7.0\ext\subversion\subversion\libsvn_wc\workqueue.c' >

Re: Assertion failed in tree_conflicts.c

2010/2/23 Jean-François Davignon : > Overworked DFU, or should I say DFU because overworked: > - renamed branch Project_30 to Project_31 but Project_31 branch already > existed in that location, ignored errors, dismissed dialogs, forgot about > whole thing; > - did update on parent folder, got erro