liulee / gurtle

Automatically exported from code.google.com/p/gurtle
0 stars 0 forks source link

COM error after commit #44

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Two times now I got this error after a commit:

Completed            : At revision: 234
Error                : Failed to start the issue tracker COM provider 'Gurtle'.
Error                : Unknown error 0x80131509
Error                : Operation is not valid due to the current state of
the object.

But this only happens if I don't open the issues dialog from the TSVN
commit dialog first.
I'm using the very latest version of Gurtle (compiled myself) from trunk
(and of course the latest version of TSVN).

I'm not sure if this is an issue of Gurtle or TSVN yet. But the COM error
indicates that there's some kind of exception thrown from Gurtle.

Don't have the time right now to investigate, so I'm opening this issue so
I don't forget.

Original issue reported on code.google.com by tortoisesvn on 13 Oct 2009 at 8:17

GoogleCodeExporter commented 9 years ago
> only happens if I don't open the issues dialog from the TSVN
> commit dialog first

Where else in TSVN can you open the issues dialog from?

> Operation is not valid due to the current state of
> the object.

This is definitely something coming from a .NET Framework exception, as its the 
standard message for for System.InvalidOperationException. It would be great if 
you 
can help to determie the steps to reproduce this.

Original comment by azizatif on 13 Oct 2009 at 9:07

GoogleCodeExporter commented 9 years ago
I've analyzed the problem:
In plugins.cs, line 182, Gurtle throws an InvalidOperationException if the 
project
isn't set. But the project variable is only set if the issuebrowserdialog is 
shown
before.
Since sometimes I do a commit without assigning an issue to it and therefore 
without
first showing that dialog, I then get the error at the end of a commit.

TSVN shows the error only since I've implemented reading the COM error 
description,
it didn't show that error before because the error string variable that gets 
returned
by OnCommitFinished() is empty, so TSVN had nothing to show.

Original comment by tortoisesvn on 14 Oct 2009 at 6:02

GoogleCodeExporter commented 9 years ago

Original comment by tortoisesvn on 14 Oct 2009 at 6:17

GoogleCodeExporter commented 9 years ago
This issue was closed by revision r224.

Original comment by tortoisesvn on 14 Oct 2009 at 6:19