6 ms·
GitHub is investigating an incident with Pull Requests, Issues and Webhooks
- jmuguy 3y agoYep, we're in the midst of doing code review here and can't get our commits to show up on the site.
- CuriousCosmic 3y agofwiw pull requests heads can be accessed locally via ``` ${remote}/pull/${ID}/head ``` where remote is the git remote for the repo (probably `origin`) and id is the pull request number. You may need to fetch to get the up to date head and if it still doesn't work, try just fetching the ref directly from the remote. You can then diff against main/master, try merging into main, etc. which should give you everything you need to code review. If you want to diff the current branch against main/master at the branch point, you can do: ``` git diff $(git merge-base --fork-point master) ``` That will diff against the point in history where the branch diverged.
- samdobreva123 3y ago[flagged]
- samdobreva123 3y ago[flagged]
- samdobreva123 3y ago[flagged]
- technics256 3y agoI came here to check why my merge status wasn't updating and yep, HN breaks news the fastest still. With all of the GithHub Universe AI announcements, it's sad to see the main github product being ignored.
- adnjoo 3y ago:(
- jameswatling 3y agoIt took them a while to flag also. My team ran into issues at least 80 minutes before this was posted
- JLCarveth 3y agoGitHub outages seem to have happened a lot this year.
- baq 3y agoAlso, last year. And the year before. My previous job even floated the idea to come back to onprem infra for this reason.
- FridgeSeal 3y agoI’ve also noticed a lot of consistency issues on their site recently. Open PR; someone comments-doesn’t show up no matter how many hard refreshes, browser restarts, etc. Push a commit to your branch - doesn’t show up in the PR, but shows up in the commit history. If you have auto-merge ticked, it might never merge even when it meets the conditions, and if the branch merges you won’t know, because again, the PR never updates and it still looks open. I have these issues- in varying degrees of duration and severity- about once a week.
- calvinmorrison 3y agoWeb hooks are not reliable. When engineering your system, you need to implement a scheduled based watcher to go back and clean up hook issues.
- bob1029 3y agoI 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).
- calvinmorrison 3y agoIt's part of the Shopify and BigCommerce's design pattern explicity. Like, yes we offer webhooks, but also you need to come back once an X (I typically do hourly) and sweep for missed data. Not to mention with Shopify, webhooks are not guaranteed to be at all ordered. You may receive an order.updated event prior to an order.create event. Delivery milage and timing may vary. So, after all that back and forth we asked ourselves, why do we even bother with webhooks? Well for one, it helps our clients being real time to improve their shipping speed, keeping real time inventory, and so forth. Secondly, it keeps our processing more flat. We might run an hourly cron to pickup stragglers, but we don't do huge data dumps per hour. In some our busier systems it can be a real challenge when clients do things like monthly invoicing all their customers. Using webhooks and processing records as they come in keeps the queue as small as reasonable.
- brazzledazzle 3y agoYeah GitHub doesn't like when you do frequent polling over hooks but you pretty much need to have something polling (infrequently) to catch undelivered hooks.
- noman-land 3y agoMaybe I wasn't paying attention as much but I never remember Github having this high a frequency of outages before Microsoft bought them.
- anuraaga 3y agoAm I the only one that remembers frequent outages before the acquisition? I didn't keep track in a spreadsheet or anything so don't have any data to back it up though but always assumed it's similar to Twitter of the day, hard to make a stable service in Rails. If anyone can actually put out the data that would be great. I suspect there was a period post acquisition of relative stability that dulls our memory of frequently broken PRs which we probably just got used to at the time.
- selykg 3y agoBefore 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.
- hotnfresh 3y agoThe big one-step-forward-five-steps-back UI redesign was before the acquisition, wasn’t it?
- ljm 3y agoOnly now is GH redesigning the UI to be fluid-width everywhere. And GitHub actions were basically sharing the infra of Azure Pipelines.
- aicez 3y agoAgreed. I vaguely recall that there were no new features for more than a year.
- midasuni 3y agoMy screwdriver doesn’t seem to need more features. It’s nice stable and reliable.
- charlesfries 3y agoIt'd be great if the apparent "world's leading AI-powered developer platform" didn't go down every week.
- rymiel 3y agoEvery week? You're being very generous to them
- gumballindie 3y agoThey should understand this. If users move away who’s code will the rinse and resell?
- gtirloni 3y agoMove where exactly? Bitbucket and GitLab aren't that great either. I'm affected by GitHub outages maybe once every 2 months for a couple of hours. Sure, various parts go down but it's never something super impactful to my workflow. It's not great but, IMHO, not outrage worthy.
- gumballindie 3y agoI am not particularly keen on github and microsoft scraping my code and re-selling it via copilot. If you own mission critical ip you can always spin up a vm and setup reliable backups using gitlab, or simply via ssh. It really is that easy to move away.
- kemiller2002 3y agoThey are being honest about their position. They do call it "artificial intelligence powered"
- gonzo41 3y agoThat tag line isn't for you. It's for aging C-suite exec's who like fancy sounding words. As for not going down. Meh, at least you don't have to do on-call for it. That's kind of half the point of paying for SaaS. At the end of the day, it's just a human system.
- contingencies 3y agoOutages, 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.
- richbell 3y ago> forced 2FA bullshit... all this makes long term customers want to self host. An objectively positive security feature makes people want to self host?
- contingencies 3y agoI don't trust security people to do sane things. - Linus Torvalds (2017) Specifically, if you have a happy client paying you monthly who has established a functional workflow and no problems, how is forcibly breaking that based on a series of bullshit assumptions (eg. customer has a static phone number in one country that they have continuous SMS access to, customer wants to install your extra app, whatever) for the nominal benefit of some theoretical attack category a smart idea? It's fine to offer the migration, even to encourage it. But to insist is both wrong and bad for business.
- richbell 3y ago> eg. customer has a static phone number in one country that they have continuous SMS access to, customer wants to install your extra app, whatever GitHub uses TOTP which does not require SMS, can be used with dozens of apps (because it's a protocol), and can be easily transfered using QR codes or seeds.
- sgift 3y agoAlso, they support Passkeys. Which is by all metrics a vastly superior way to secure an account compared to normal passwords.
- zlg_codes 3y agoKinda 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.
- unicornmama 3y agoFrustrating and unproductive day for those trapped in CI driven development mode. Mild annoyance for the rest of us.
- gherkinnn 3y agoI have never worked, or know someone who has, at a place that doesn't rely on CI (does that make it CIDD?). Of all the *DDs, this is one of the few that is done without much complaint or major problems or controversies around it.
- unicornmama 3y agoEver see a PR with 50-100 commits in short succession with messages like “fix”? That’s CIDD.
- hn_ta456 3y agoCI does make sense if your job entails endlessly churning web app features and UI.
- gherkinnn 3y agoThat it be and applies to me. And countless others. Oh the drudge. I also know countless people who work outside of CRUD world who rely on CI. The only exception I can think of are scientists who, well, tend not to use version control beyond folder naming. Not that I blame them, on the contrary.
- adnjoo 3y agoare github runners stalling?
- whalesalad 3y agoAnyone else having issues w/ AWS connectivity too?
- adhamsalama 3y agoHopefully AI can fix this.
- eek2121 3y agoOh, it must be a day that ends in “y”.