-
-
Notifications
You must be signed in to change notification settings - Fork 128
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
WIP Expected — Waiting for status to be reported #660
Comments
Same here - |
Same here |
1 similar comment
Same here |
we have the same problem, see for example: Lightning-AI/pytorch-lightning#19442 |
First noticed this yesterday 4pm eastern |
Same here. We have disabled this plugin for the time being |
cc @gr2m |
same for us @afirth |
Sorry folks, there was a problem yesterday for a short time, I thought I resolved it. Looking into it now |
I was able to reproduce the problem here: #661 - sorry for the inconvenience. I'll revert recent changes for now and will be more careful in future. |
Will confirm it's working first |
ugh no luck, I'll keep you posted |
🤦 I had the webhook URL still pointing to a preview deployment. Should all be working again. I'm very sorry for all that, I'll think about putting in a CD check to verify a new deployment to production is working as expected. |
Thank you @gr2m ! |
By the way, existing status are not updated I'm afraid, you will have to edit the pull request title or push a new commit in order to trigger a reset of the WIP status check |
I have pushed a new commit but the "WIP Expected — Waiting for status to be reported" message remains unchanged. |
Can you share the URL of the pull request, even if the repository is private? I can look into it. Can you please file a separate issue as a lot of people are subscribed to this one? Thank you! |
Hi,
We've started having
WIP Expected — Waiting for status to be reported
reported on all of our PRs starting today.Seems to be the same as #174.
Please let me know if theres any extra debugging information I can pass on.
The text was updated successfully, but these errors were encountered: