Earlier quoted context omitted.
Here you go: $ while ! git push my; do sleep 1; done Works for me eventually, although commits do not appear in web interface (they do in the actual repository).
-f does not sound like a good idea to me in a script like that.
Incident with GitHub Actions, API requests, Codespaces, Git operations, Issues
61–70 of 123 posts
Re: Incident with GitHub Actions, API requests, Codespaces, Git operations, Issues
#62Whew, glad I decided to scroll HN right now. I've been puzzling over why I'm getting "! [remote rejected] master -> master (Internal Server Error)" as well while trying to push and decided to take a break.
Time to take some coffee and configure Vim
Re: Incident with GitHub Actions, API requests, Codespaces, Git operations, Issues
#63Earlier quoted context omitted.
It's fine. Maybe it will force them to finally start paying attention to the quality of their work. If crap I'm writing for a living was misbehaving that frequently, I'd be sweeping the streets by now (or doing some other work that's actually useful to society).
It's OK to be frustrated since we rely on GitHub so much, but this is unkind. Software is complex. GitHub operates at a scale few of us work at. There are people at the other end doing their best traversing complex internal systems (organization and tech). I would argue GitHub has done more for societal good than most tech ventures, by the way.
At the end of the day - our companies also have people that rely on our software working in order to do a lot of societal good.
Re: Incident with GitHub Actions, API requests, Codespaces, Git operations, Issues
#64I'm finding that pushes do go through eventually, this is probably grossly irresponsible, so I don't recommend its use, but I remembered I had this old alias to "push harder" in my ~/.gitconfig: [alias] thrust = "!f() { until git push $@; do sleep 0.5; done; }; f" I've done a few pushes so far, and found that it's going through in <10 tries or so.
Re: Incident with GitHub Actions, API requests, Codespaces, Git operations, Issues
#65Does anybody else remember when GitHub's outage page used to have little graphs showing downtime? Eventually they took it down as their outages were just too often. GitHub has _always_ had terrible uptime. It's a great product - wish something would change but it seems cultural at this point.
Re: Incident with GitHub Actions, API requests, Codespaces, Git operations, Issues
#66Earlier quoted context omitted.
The entire point of git is that it's decentralized, lol. If I've cloned locally like millions of people do daily, I have a backup.
> The entire point of git is that it's decentralized, lol. No-one here is criticizing git itself. That is not the point. It is GitHub that is defeating the whole point of it all, once their hosted central server goes down. The majority of these projects went all in on GitHub, including using GitHub actions, npm packages, hosting their whole website, etc hence as soon as it goes down, they can't push or update anythin…
server != service
assuming its a distributed service vs one server for a multi-billion$ company also group of humans built this service, so its not gonna be perfect :shrug:
companies that use such tools and in trust all the business process to a provided service and do consider an event like this is a blocker should build in contingency plans or accept that there is no real 5-nines of availability more like 90-98%
Re: Incident with GitHub Actions, API requests, Codespaces, Git operations, Issues
#67I'm finding that pushes do go through eventually, this is probably grossly irresponsible, so I don't recommend its use, but I remembered I had this old alias to "push harder" in my ~/.gitconfig: [alias] thrust = "!f() { until git push $@; do sleep 0.5; done; }; f" I've done a few pushes so far, and found that it's going through in <10 tries or so.
Re: Incident with GitHub Actions, API requests, Codespaces, Git operations, Issues
#68These incidents have to hurt Azure's brand value. It's a monster task to run something as big as GitHub, if they ever get it stable it will lend a lot of credibility to Microsoft's cloud skills.
I don't consider this a reflection on Azure at all. It's really just a reflection on GitHub under Microsoft's leadership.
Re: Incident with GitHub Actions, API requests, Codespaces, Git operations, Issues
#69Earlier quoted context omitted.
It's OK to be frustrated since we rely on GitHub so much, but this is unkind. Software is complex. GitHub operates at a scale few of us work at. There are people at the other end doing their best traversing complex internal systems (organization and tech). I would argue GitHub has done more for societal good than most tech ventures, by the way.
People tend not to be very kind when any product they pay for goes down. At the end of the day - our companies also have people that rely on our software working in order to do a lot of societal good.