-
Notifications
You must be signed in to change notification settings - Fork 32
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
0pdd closed existing ticket #86
Comments
@yegor256 please, pay attention to this issue |
@amihaiemil it does look weird... Let me investigate. |
@amihaiemil I can't understand why that happened :( Let's monitor this situation. |
@yegor256 sure. I'll keep an eye open for it, see if it happens again :D |
@amihaiemil is it still an issue? If not, please close |
@yegor256 I haven't noticed. Closing for now. |
Oops! There is no order for job |
Oops! Job |
0pdd closed a ticket which still had its puzzle in the code.
Steps:
commit 1: added a puzzle and the new ticket was opened -- ok
commit 2: removed another puzzle from the code, the corresponding ticket was closed, together with the ticket opened in commit 1 (even though its puzzle remained in the code)
The ticket removed at commit 2 was the parent of the one created at commit 1, maybe that is the problem :D
The text was updated successfully, but these errors were encountered: