StackoverflowException about workitemupdater

[tbolon]

Ok, nailed it.

We had a work-item whose state was not valid to move from current state to "Done" state (a required field was empty).

After I edited the specific work-item (8038 in my log) then the build succeed.

What we should need is something to better handle patch error. I do not understand why a StackOverflowException is raised when calling UpdateWorkItemAsync. Perhaps a native trace should be more helpful. The ideal case should be to raise an error with the detail of the Update error instead of a SOE.

Regards,

[BlueBasher]

Very stange it's throwing a StackOverflowException when there is an illegal state transition.
I'll have a look whether there's some way in the api to change this in a proper error.

[philcart]

We're encountering the same StackOverflowException. See attached Release Logs.

While I'd like to utilise this extension, we can't because of this error.

Cheers
Phil

ReleaseLogs_208.zip

[BlueBasher]

Just made a couple of changes #20 related to the StackOverflowException.
I reproduced one case of the SO and that is definitely fixed in this release.
There are multiple reasons for the SO Exception and made some other improvements that hopefully will resolve it.

These changes have been released in version 1.5.721 of the Build-Task.
I'll keep this issue open for now so if any of you are still seeing the issue please let me know so I can dig into it further.

[BlueBasher]

Closing since no reports of the issue.