WIP bot stuck and not reporting status

[katiehockman]

Is the bot down right now? Multiple PRs are getting stuck with this status despite not changing any configuration. The titles of those PRs don't include anything "WIP" related either.

[narendrakumar-nj]

+1

[alexeyvoren]

+1

[andrew-garland]

+1

[AmaiaEspinosaTR]

+1

[rmonac]

This effectively blocked my pull requests from being merged. They were stuck on "WIP Expected — Waiting for status to be reported".

---

I've found a workaround to allow merging pull requests untill this gets fixed. Check status can be updated throught the GitHub CLI by running this:

gh api --method POST -H "Accept: application/vnd.github+json" -H "X-GitHub-Api-Version: 2022-11-28" "/repos/{OWNER}/{REPO}/statuses/{SHA} " -f "state=success" -f "description=All good!" -f "context=WIP"

Specify the OWNER, REPO and SHA (the latest commit id from your pull request).
Make sure to set context=WIP. You can also set your own description.

---

Here's how to install and authenticate GitHub CLI.

[gr2m]

Hey sorry folks I'm looking into it

[gr2m]

There is definitely something wrong:

I'll try to turn-it-off-and-on-again 🤷🏼 not seeing anything helpful in logs yet

[gr2m]

No luck. I also reverted to a prior version from 5 days ago that didn't have the problem. I'm not sure what's up yet, I will keep you posted

[gr2m]

I submitted a support case with Vercel. All I see in the logs is "504 Gateway Timeout", no logs from the WIP app at all.

[gr2m]

Okay I think I fixed the problem by reverting back to a prior deployment. Can you please confirm? I'll investigate what caused the problem and will share it here once I found out. I will also look into implementing a more reliable monitoring setup beyond just a ping check.

Sorry again for the trouble!

[andrew-garland]

Okay I think I fixed the problem by reverting back to a prior deployment. Can you please confirm? I'll investigate what caused the problem and will share it here once I found out. I will also look into implementing a more reliable monitoring setup beyond just a ping check.

Sorry again for the trouble!

Worked for me, thanks

[gr2m]

🤦🏼 a probot update sneaked in with this PR: #802. I'll just look into finally upgrading WIP to latest probot, it's way overdue. This is at least the 2nd time I got bitten by this.