-
Notifications
You must be signed in to change notification settings - Fork 10
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
two webhooks cause two jira cards created #57
Comments
I believe this also occurred for this issue. Glad I'm not the only one! |
What I wonder about is why this started happening recently. Seems like something that should have been broken all along |
@ca-scribner I assume that github changed the order in which webhooks are sent. Since juju app is unchanged since months now
|
yeah that's unsatisfying but I buy your argument :D Looking through the code, I suspect this jira search is not correctly finding the existing issue. There's no existing log line to confirm this, but I think that's the only way this issue occurs. Going into the Jira Issues page, I queried:
and got no hits even though there is an issue that should match that. Messing with the query some, I can get hits with
seems like the hyphen is breaking things. Why is it suddenly breaking things now? idk I tried using a |
@ca-scribner no, the problem is that you have two hooks sent at 01:00:00, time to process jira card creation is 5s. By time the second hook lands to the server the jira search still returns None, which causes second card creation |
Since our service is stateless, we lack visibility into what each unit of the app has produced and how it has acted.
When an issue is created from the template in GitHub, we receive two consecutive events: one for the issue being opened and another for the issue being labeled. (or even worse scenario when GitHub changes the order of the webhooks, first - Labeled, second - opened; In this case issue opened comes with the label in the payload)
We need to consider how to handle this situation effectively.
See canonical/bundle-kubeflow#1186
First it sent
issue labeled
And a second after:
issue opened
The text was updated successfully, but these errors were encountered: