-
Notifications
You must be signed in to change notification settings - Fork 649
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 when two feature branches are pointing to the same commit #411
Milestone
Comments
johannesegger
changed the title
StackoverflowException when two feature branches are pointing to the same commit
Apr 1, 2015
StackoverflowException
when two feature branches are pointing to the same commit
johannesegger
changed the title
StackoverflowException when two feature branches are pointing to the same commit
StackOverflowException when two feature branches are pointing to the same commit
Apr 1, 2015
Can you please share the complete stack trace? |
@nulltoken this will likely be my branch inheriting code as it is recursive. I will create a repro test and fix |
I don't get a complete stack trace when I run this from the command line, but I could probably checkout the branch and run it with an attached debugger if you want me to? |
yannisgu
pushed a commit
to unic/GitVersion
that referenced
this issue
Apr 23, 2015
Merged
yannisgu
pushed a commit
to unic/GitVersion
that referenced
this issue
Apr 23, 2015
yannisgu
pushed a commit
to unic/GitVersion
that referenced
this issue
Apr 23, 2015
yannisgu
pushed a commit
to unic/GitVersion
that referenced
this issue
Apr 23, 2015
JakeGinnivan
added a commit
that referenced
this issue
Apr 23, 2015
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I made a mistake and set two feature branches to point to the same commit. When running
gitversion
on one of the branches it crashes with aStackOverflowException
. Of course this is my mistake because two feature branches shouldn't point to the same commit, but maybe you can detect and break the recursion (or whatever the exception triggers).Run the following commands to reproduce the issue:
The version of GitVersion is used was 3.0.0-Beta1.
The text was updated successfully, but these errors were encountered: