Browser-compat-data: Auto-labeler outage (Glitch downtime)

[vinyldarkscratch]

Hey @ddbeck, the past couple of PRs I've seen haven't been automatically labeled. Wondering if there's something up with the labeler?

[ddbeck]

@vinyldarkscratch The most recent open PRs have been labeled. Can you link to at least one example of this problem?

[vinyldarkscratch]

Sure thing! Looking back, apparently some of them are getting labeled, but here's one that I saw that wasn't: https://github.com/mdn/browser-compat-data/pull/5842

[ddbeck]

Glitch had some downtime earlier, which coincides with the time on that issue: https://status.glitch.com/incidents/40ttchslv5yg. I don't think there's anything for us to do about it, so I'm going to close this issue.

[vinyldarkscratch]

Ah okay, gotcha -- thanks for the quick response!

[vinyldarkscratch]

Hmm...just created two PRs that didn't get automatically labeled, as well as the PR created before that a day ago. #5856, #5857, #5858. 🙁

Update: my most recent PR, #5859, was automatically labeled, however I think there's still been enough issues that we should try to dig into it more?

[ddbeck]

It looks like Glitch is having some persistent problems: https://status.glitch.com/incidents/rsms0r0vykr7. I suggest we leave this issue open until Glitch's outage is announced as fixed, then check for any missed labels on PRs created during the outage period. I don't think this is critical enough to fuss with redeploying elsewhere.

[ddbeck]

Glitch has marked the outage as resolved and their uptime charts don't show any significant issues in the last few days. I'm going to close this issue. I'll also rename the issue ("Auto-labeler outage (Glitch downtime)") to make it easier to find should we ever need to revisit the uptime question again.