Web hooks are not reliable. When engineering your system, you need to implement a scheduled based watcher to go back and clean up hook issues.
GitHub is investigating an incident with Pull Requests, Issues and Webhooks
11–20 of 61 posts
Re: GitHub is investigating an incident with Pull Requests, Issues and Webhooks
#12Maybe I wasn't paying attention as much but I never remember Github having this high a frequency of outages before Microsoft bought them.
Re: GitHub is investigating an incident with Pull Requests, Issues and Webhooks
#13Maybe I wasn't paying attention as much but I never remember Github having this high a frequency of outages before Microsoft bought them.
Before Microsoft bought them they were basically at a standstill and no new features were being added to the product. At least, that's my recollection of it, perhaps someone can correct me if I'm wrong.
Re: GitHub is investigating an incident with Pull Requests, Issues and Webhooks
#14It'd be great if the apparent "world's leading AI-powered developer platform" didn't go down every week.
Re: GitHub is investigating an incident with Pull Requests, Issues and Webhooks
#15Web hooks are not reliable. When engineering your system, you need to implement a scheduled based watcher to go back and clean up hook issues.
I gave up trying to be a polite API consumer with GitHub events, etc. Polling the basic resources every minute is way more reliable and your code will survive a junior developer's shenanigans.
I had the REST API e-tag polling working well, but then I discovered my org event stream didn't include label changes. This is a separate thing I needed to poll and at that point I lost my mind. I refuse to keep track of 6+ pieces of state in order to pull essential data from an API.
My current pattern is to list all open issues and then compare their updated_at with persisted copies. If any changes, then I refresh the comments for the issue as well as top-level items (title/body/labels).
Re: GitHub is investigating an incident with Pull Requests, Issues and Webhooks
#16Outages, forced 2FA bullshit, half-wit AI feature because buzzword... all this makes long term customers want to self host. Can someone drop a hint to the CEO please: WE PAY YOU TO BE BORING AND STABLE.
Re: GitHub is investigating an incident with Pull Requests, Issues and Webhooks
#17Kinda sad that my self-hosted Raspberry Pi on consumer Internet, running cgit, stays up longer than GitHub.
The Microsoft acquisition has not been good for them.
Re: GitHub is investigating an incident with Pull Requests, Issues and Webhooks
#18It'd be great if the apparent "world's leading AI-powered developer platform" didn't go down every week.
They are being honest about their position. They do call it "artificial intelligence powered"
Re: GitHub is investigating an incident with Pull Requests, Issues and Webhooks
#19Maybe I wasn't paying attention as much but I never remember Github having this high a frequency of outages before Microsoft bought them.
Microsoft brought to them shitton of new users like big enterprises
which implies a lot of more challenges
Re: GitHub is investigating an incident with Pull Requests, Issues and Webhooks
#20Maybe I wasn't paying attention as much but I never remember Github having this high a frequency of outages before Microsoft bought them.
Before Microsoft bought them they were basically at a standstill and no new features were being added to the product. At least, that's my recollection of it, perhaps someone can correct me if I'm wrong.
The big one-step-forward-five-steps-back UI redesign was before the acquisition, wasn’t it?