-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
StackoverflowException #6
Comments
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, |
Very stange it's throwing a StackOverflowException when there is an illegal state transition. |
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 |
Just made a couple of changes #20 related to the StackOverflowException. These changes have been released in version 1.5.721 of the Build-Task. |
Closing since no reports of the issue. |
Even with the new 1.3.6 version released, I still receive an error on certain cases.
The text was updated successfully, but these errors were encountered: