: Subversion Exception - assertion failed
Den tis 12 sep. 2023 kl 12:19 skrev Matthias Klose
mailto:m.kl...@automation.de>>:
Hi,
I want to list a failing assertion.
What have I done?:
Preparing a merge on a directory with Doxygen configuration files (maybe not
usefull, but I did it).
choosing o
dry-run option.
> -> this leads into the following exception:
>
> ---
> Subversion Exception!
> ---
> Subversion encountered a serious problem.
> Please take the time to report this on the Subversion mailing list
> with as
the following exception:
---
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 fi
Branko Čibej wrote:
All I can say is that there is no way for our canonicalisation functions
to produce the correct result for *every* possible input.
The new variants that return errors instead of aborting are an improvement,
We should mention the new variants in
http://subversion.apache.org/d
n the directory for my
>>> project, I get a popup that just says “TortoisesSVN client has stopped
>>> working. A problem caused the program to stop working correctly. Please
>>> close the program.” It seems to be a problem with just this project; I can
>>>
gt; > close the program.” It seems to be a problem with just this project; I can
> > click down into other projects in the same repository. I’ll report that
> > separately.
>
> Here again I think you should probably contact the TSVN community. It
> might be related to the
When doing an update on the working copy, since twenty commit has been made
since last update, I got the following:
---
Subversion Exception!
---
Subversion encountered a serious problem.
Please take the time to report this on the Subversion
On 28.12.2018 11:19, Branko Čibej wrote:
> On 28.12.2018 11:05, Bert Huijben wrote:
>> +svn_error_t *
>> +svn_error__malfunction_f(svn_boolean_t can_return,
>> + const char *file, int line,
>> + const char *fmt, ...)
>> +{
>> + apr_pool_t *pool = svn
On 28.12.2018 11:05, Bert Huijben wrote:
> +svn_error_t *
> +svn_error__malfunction_f(svn_boolean_t can_return,
> + const char *file, int line,
> + const char *fmt, ...)
> +{
> + apr_pool_t *pool = svn_pool_create(NULL);
> + va_list ap;
> + const c
+svn_error_t *
+svn_error__malfunction_f(svn_boolean_t can_return,
+ const char *file, int line,
+ const char *fmt, ...)
+{
+ apr_pool_t *pool = svn_pool_create(NULL);
+ va_list ap;
+ const char *expr;
+
+ va_start(ap, fmt);
+ expr = apr_pvsprint
On 15.12.2018 12:24, Branko Čibej wrote:
> On 14.12.2018 19:05, Branko Čibej wrote:
>> On Fri, 14 Dec 2018, 18:14 Julian Foad >
>>> Julian Foad wrote:
Are you willing to add random-input testing for them?
>>> The attached patch 'dirent-uri-test-random-2.patch' tests rules like:
>>>
>>> * eve
On 14.12.2018 19:05, Branko Čibej wrote:
> On Fri, 14 Dec 2018, 18:14 Julian Foad
>> Julian Foad wrote:
>>> Are you willing to add random-input testing for them?
>> The attached patch 'dirent-uri-test-random-2.patch' tests rules like:
>>
>> * every result should pass an X_is_canonical() test (ob
Branko Čibej wrote:
> What inconsistencies? A canonical URI has the scheme and host name in
> lowercase, but the path, query, fragment and user info parts are case-
> sensitive.>
> Similarly, I think we (or APR?) make drive letters lowercase.
In both cases I found examples where is_canonical said
On Fri, 14 Dec 2018, 18:14 Julian Foad Julian Foad wrote:
> > Are you willing to add random-input testing for them?
>
> The attached patch 'dirent-uri-test-random-2.patch' tests rules like:
>
> * every result should pass an X_is_canonical() test (obvious by code
> inspection);
> * every other
On Fri, 14 Dec 2018, 16:18 Julian Foad Branko Čibej wrote:
> > r1848943, for review. [...]
>
> Woo hoo! Thanks, Brane.
>
> Are you willing to add random-input testing for them?
>
> Minor comments:
> * the 'relpath' one is not needed because, AFAIK, it's possible to
> canonicalize any relpath and
Julian Foad wrote:
> Are you willing to add random-input testing for them?
The attached patch 'dirent-uri-test-random-2.patch' tests rules like:
* every result should pass an X_is_canonical() test (obvious by code
inspection);
* every other input should produce SVN_ERR_CANONICALIZATION_FAILE
Branko Čibej wrote:
> r1848943, for review. [...]
Woo hoo! Thanks, Brane.
Are you willing to add random-input testing for them?
Minor comments:
* the 'relpath' one is not needed because, AFAIK, it's possible to
canonicalize any relpath and we already do;
* the non-canonical 'result' and scr
On 13.12.2018 17:00, Branko Čibej wrote:
> On 13.12.2018 16:53, Michael Pilato wrote:
>> On 12/13/18 10:45 AM, Branko Čibej wrote:
>>> Uh. I forgot about the malfunction handler. However this doesn't really
>>> help, other than putting possibly sensitive paths into the crash handler
>>> info? We re
On Fri, 14 Dec 2018, 05:41 Nathan Hartman On Thu, Dec 13, 2018 at 11:59 AM Branko Čibej wrote:
>
>> I never said that it's a good idea to abort in a library. We made a
>> mistake in the early days of this project to allow such patterns.
>
>
>>
>> I am quite angry at the contrariness and stubbornn
On Thu, Dec 13, 2018 at 11:59 AM Branko Čibej wrote:
> I never said that it's a good idea to abort in a library. We made a
> mistake in the early days of this project to allow such patterns.
>
> I am quite angry at the contrariness and stubbornness of one TSVN
> developer, who is *also* a Subve
On 13.12.2018 17:39, Mark Phippard wrote:
>> On Dec 13, 2018, at 11:26 AM, Branko Čibej wrote:
>>
>> On 13.12.2018 17:09, Mark Phippard wrote:
On Dec 13, 2018, at 10:53 AM, Michael Pilato wrote:
> On 12/13/18 10:45 AM, Branko Čibej wrote:
> Uh. I forgot about the malfunction han
> On Dec 13, 2018, at 11:30 AM, Daniel Shahaf wrote:
>
> Mark Phippard wrote on Thu, 13 Dec 2018 11:09 -0500:
>> FWIW, I agree with Stefan on all of this. We should not be doing abort
>> from a library. Whether TSVN could do more to avoid it seems like a
>> separate issue. I do not see why
> On Dec 13, 2018, at 11:26 AM, Branko Čibej wrote:
>
> On 13.12.2018 17:09, Mark Phippard wrote:
>>> On Dec 13, 2018, at 10:53 AM, Michael Pilato wrote:
>>>
On 12/13/18 10:45 AM, Branko Čibej wrote:
Uh. I forgot about the malfunction handler. However this doesn't really
help,
Daniel Shahaf wrote:
> At the same time, I think Brane had a valid point. It is not
> users@subversion's job to triage TortoiseSVN error reports;
It's a valid point of view but please let's stop pushing that point, especially
don't ask Stefan to go over it again. Please let's concentrate on what
Mark Phippard wrote on Thu, 13 Dec 2018 11:09 -0500:
> FWIW, I agree with Stefan on all of this. We should not be doing abort
> from a library. Whether TSVN could do more to avoid it seems like a
> separate issue. I do not see why the library cannot just return a
> useful error and allow the
Daniel Shahaf wrote:
> [...] If you have
> found a value for which svn_foo_is_canonical(svn_foo_canonicalize(value))
> returns false, please tell us what that value is.
Daniel, some examples:
path = "foo";
-> assertion 'svn_uri_is_canonical(svn_uri_canonicalize(f, pool), pool)' failed
#define S
On 13.12.2018 17:09, Mark Phippard wrote:
>> On Dec 13, 2018, at 10:53 AM, Michael Pilato wrote:
>>
>>> On 12/13/18 10:45 AM, Branko Čibej wrote:
>>> Uh. I forgot about the malfunction handler. However this doesn't really
>>> help, other than putting possibly sensitive paths into the crash handler
Branko Čibej wrote on Thu, 13 Dec 2018 17:00 +0100:
> On 13.12.2018 16:53, Michael Pilato wrote:
> > On 12/13/18 10:45 AM, Branko Čibej wrote:
> >> Uh. I forgot about the malfunction handler. However this doesn't really
> >> help, other than putting possibly sensitive paths into the crash handler
>
> On Dec 13, 2018, at 10:53 AM, Michael Pilato wrote:
>
>> On 12/13/18 10:45 AM, Branko Čibej wrote:
>> Uh. I forgot about the malfunction handler. However this doesn't really
>> help, other than putting possibly sensitive paths into the crash handler
>> info? We really shouldn't do it this way
On 13.12.2018 16:53, Michael Pilato wrote:
> On 12/13/18 10:45 AM, Branko Čibej wrote:
>> Uh. I forgot about the malfunction handler. However this doesn't really
>> help, other than putting possibly sensitive paths into the crash handler
>> info? We really shouldn't do it this way, users *will* jus
On 12/13/18 10:45 AM, Branko Čibej wrote:
> Uh. I forgot about the malfunction handler. However this doesn't really
> help, other than putting possibly sensitive paths into the crash handler
> info? We really shouldn't do it this way, users *will* just copy and
> paste the output tot he 'net.
Ahem
Branko Čibej wrote:
> On 13.12.2018 16:42, Johan Corveleyn wrote:
> >> [...] assertion failed
> >> (svn_dirent_is_absolute(local_abspath='C:ImNotAbsolute'))
> > Nice :-). I'm not sure what others think, but IMHO that would make
> > these error reports a lot more useful ...
>
> [...] this doesn't
On 13.12.2018 16:42, Johan Corveleyn wrote:
> On Thu, Dec 13, 2018 at 4:05 PM Julian Foad wrote:
>> Johan Corveleyn wrote:
>>> Just thinking out loud here, but could we perhaps log the
>>> non-canonical value as part of the assertion output?
>>> [...]
>>> something like
>>>
>>> line 10238: assert
On Thu, Dec 13, 2018 at 4:05 PM Julian Foad wrote:
>
> Johan Corveleyn wrote:
> > Just thinking out loud here, but could we perhaps log the
> > non-canonical value as part of the assertion output?
> > [...]
> > something like
> >
> > line 10238: assertion failed
> > (svn_dirent_is_absolute(local_
Johan Corveleyn wrote:
> Just thinking out loud here, but could we perhaps log the
> non-canonical value as part of the assertion output?
> [...]
> something like
>
> line 10238: assertion failed
> (svn_dirent_is_absolute(local_abspath='C:ImNotCanonical'))
Yes, Johan, we could do that.
The atta
On 13.12.2018 14:15, Johan Corveleyn wrote:
> On Wed, Dec 12, 2018 at 10:23 PM Daniel Shahaf
> wrote:
>> Stefan Kueng wrote on Wed, 12 Dec 2018 21:16 +0100:
>>> And as I repeatedly said: TSVN does validate the input as good as it
>>> can. But if svn does neither describe the *exact* specs in the
On Wed, Dec 12, 2018 at 10:23 PM Daniel Shahaf wrote:
> Stefan Kueng wrote on Wed, 12 Dec 2018 21:16 +0100:
> > And as I repeatedly said: TSVN does validate the input as good as it
> > can. But if svn does neither describe the *exact* specs in the docs nor
> > provide any APIs that do that, then T
Stefan Kueng wrote on Wed, 12 Dec 2018 21:16 +0100:
> And as I repeatedly said: TSVN does validate the input as good as it
> can. But if svn does neither describe the *exact* specs in the docs nor
> provide any APIs that do that, then TSVN has to guess.
> And no: specifying that paths/uris have t
*exact* specs in the docs
> nor provide any APIs that do that, then TSVN has to guess.
> And no: specifying that paths/uris have to be "canonicalized" is not
> enough because I do that, using the svn APIs.
> So apparently that's not enough.
Get one of the dumps the
On 12.12.2018 21:12, Branko Čibej wrote:
On 12.12.2018 19:07, Stefan Kueng wrote:
On 12.12.2018 13:55, TortoiseSVN-dev on behalf of Julian Foad wrote:
Subversion encountered a serious problem.
Please take the time to report this on the Subversion mailing list
[…]
https://subversion.apach
On 12.12.2018 19:07, Stefan Kueng wrote:
>
>
> On 12.12.2018 13:55, TortoiseSVN-dev on behalf of Julian Foad wrote:
Subversion encountered a serious problem.
Please take the time to report this on the Subversion mailing list
>> […]
https://subversion.apache.org/mailing-lists.html
>>
On 12.12.2018 13:55, TortoiseSVN-dev on behalf of Julian Foad wrote:
Subversion encountered a serious problem.
Please take the time to report this on the Subversion mailing list
[…]
https://subversion.apache.org/mailing-lists.html
It is likely that this is a problem specific to TortoiseSV
>> Subversion encountered a serious problem.
>> Please take the time to report this on the Subversion mailing list
[…]
>> https://subversion.apache.org/mailing-lists.html
>It is likely that this is a problem specific to TortoiseSVN, and not
>to core SVN. TortoiseSVN has its own mailinglists, so yo
On Mon, Dec 10, 2018 at 9:47 AM Peta Miller wrote:
>
> Hello,
>
>
>
> i got following exception at trying to start the tortoisesvn Project Monitor
> with a doubleclick on the tray icon.
>
> System: WIN 10, Build 15063
>
> -----
Hello,
i got following exception at trying to start the tortoisesvn Project Monitor with a doubleclick on the tray icon.
System: WIN 10, Build 15063
---
Subversion Exception!
---
Subversion encountered a serious problem.
Please take the time
gt;>> "C:\Program Files\TortoiseSVN\bin\TortoiseProc.exe" /command:commit
>>>> /pathfile:"d:\SVN\Work\Source\Project\f2.txt"
>>>>
>>>> File f2.txt contains two strings:
>>>>
>>>> d:\SVN\Work\S
tains two strings:
>
> d:\SVN\Work\Source\Source\Project.Client
> d:\SVN\Work\Source\Source\Project.Server
>
> And I received such result:
>
> ---
> Subversion Exception!
> ---
> Subversion encountered a serious problem.
; > File f2.txt contains two strings:
> >
> > d:\SVN\Work\Source\Source\Project.Client
> > d:\SVN\Work\Source\Source\Project.Server
> >
> > And I received such result:
> >
> > ---
> > Subversion Exception!
> >
gt;
> d:\SVN\Work\Source\Source\Project.Client
> d:\SVN\Work\Source\Source\Project.Server
>
> And I received such result:
>
> ---
> Subversion Exception!
> ---
> Subversion encountered a serious problem.
> Please take the
received such result:
---
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 m
---
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
looks like a bug code that's not in our repository.
-- Brane
On 09.03.2018 16:38, david.le.de...@continental-corporation.com wrote:
> ---
> Subversion Exception!
> ---
> Subversion encountered a serious problem.
> Please take the ti
Dear Andreas
if someone should encounter this error,
point to the eventual existence of the zepto
virus which has encrypted some of my .svn files
Alfred
On 9/13/2016 1:55 PM, Andreas Stieger wrote:
Hi,
Alfred Ultsch wrote:
In file
'D:\Development\SVN\Releases\TortoiseSVN-1.9.3\ext\s
Hi,
Alfred Ultsch wrote:
> In file
>
> 'D:\Development\SVN\Releases\TortoiseSVN-1.9.3\ext\subversion\subversion\libsvn_client\cleanup.c'
> line 227: assertion failed (svn_dirent_is_absolute(dir_abspath))
Upgrade to 1.9.4 and try again.
Andreas
In file
'D:\Development\SVN\Releases\TortoiseSVN-1.9.3\ext\subversion\subversion\libsvn_client\cleanup.c'
line 227: assertion failed (svn_dirent_is_absolute(dir_abspath))
Hi there! Just FYI
---
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
Hello, I find an Subversion exception, I just update code by [SVN Update] and
it happens.
FYI
---
Subversion Exception!
---
Subversion encountered a serious problem.
Please take the time to report this on the Subversion mailing list
with as much
Hi, Markus.
MS> As stated in the error message, could you please provide us with as much
MS> information as possible what you were trying to do when the error happened?
I have a project (hosted on unfuddle.com) with 3 folders:
/Folder1
/Folder2
/Folder3
When I tried to update root folder or Fol
Hi, Alexander,
Von: Alexander A. Boyko [mailto:alexander.bo...@gmail.com]
>
> ---
> Subversion Exception!
> ---
> Subversion encountered a serious problem.
> Please take the time to report this on the Subversion mailing l
---
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
---
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
---
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
62 matches
Mail list logo
