-
-
Notifications
You must be signed in to change notification settings - Fork 58
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
Webhook delivery timeout issue for the validate_maintenance_branch_pr route handler #254
Comments
One thing that could be taking up time and causing timeout is when it tries to lookup the original |
There were some funny things going on in that backport -- the original commit failed to mention the bpo issue (I missed this when merging it) and the backports created by Miss Islington also missed that. I added it back to the PR subject and body but maybe the damage was done. I also tried to close+open one of the backports (I think 3.9) but somehow one of the bots considered the closing permanent, so I closed it and created a new backport with cherry-picker -- but of course it also failed to have the bpo issue in the subject. (And thanks for unblocking the commit.) |
Hey, If this issue is beginner friendly. I can pick this up. |
@Amyth07 my guess is it's not beginner-friendly as this seems to be a finicky issue. |
@Mariatta Is there anyway to get a log or payload from these delivery errors? I have been making some PRs to |
@DanielNoord unfortunately all we ever have is the delivery details from Settings in GitHub itself, and even then we have to notice and go digging them out in the list of every payload delivered. |
That's too bad.
I'm not sure what this is referring to, see: Lines 89 to 116 in 83a2d22
Lines 70 to 82 in 83a2d22
Lines 142 to 148 in 83a2d22
As far as I can see this handler is only doing lookups in payload dictionaries and some regex matching. I checked the history of the file but that also doesn't give any hints. Without any further details I think it might be hard to debug this. Perhaps others that are subscribed to this issue have more details? Otherwise I fear this might go stale due to a lack of details. |
Here is another failed delivery. I tried to re-deliver and got another 500 error: Click to see delivery details
This is the only failure of the last 48h. Given that this issue is fairly old, it might be that the original failure was caused by something else, and the one I found is unrelated. |
@ezio-melotti Do you have the url to which you tried to deliver? Based on the tests I have one potential idea: |
The delivery I pasted above is the one visible from the GitHub webhook page of the |
While looking into python/cpython#21830, I noticed several failed webhook deliveries.
I attempted to re-deliver the same webhook payloads, but it seems that the webhook event consistently timed out for the payload below. I think we need to further investigate.
I found that if I removed the
[3.9]
from the title, then the status got posted immediately. (no timeout). And if I removed the(GH-21773)
, it also succeeds without timeout.Click to see delivery details
The text was updated successfully, but these errors were encountered: