[deleted]
Incident with GitHub Actions, API requests, Codespaces, Git operations, Issues
31–40 of 123 posts
Re: Incident with GitHub Actions, API requests, Codespaces, Git operations, Issues
#32And of course my developer teammates are still trying to merge PRs.
I don't care that it works "some of the time"! Don't mess with the repos when the repo host is having seemingly random issues.
Re: Incident with GitHub Actions, API requests, Codespaces, Git operations, Issues
#33Whew, outage timestamps in UTC.
Now I won't have to know what time is it California, and if California currently has PST, PDT, PTSD, etc
Re: Incident with GitHub Actions, API requests, Codespaces, Git operations, Issues
#34Does 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
#35I'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"
Re: Incident with GitHub Actions, API requests, Codespaces, Git operations, Issues
#36The github.com homepage, as well as api (via `gh`) are not working for me either.
Their status page is reflecting the new outages. Good on GitHub for actually updating that quickly.
We've been experiencing problems here in Asia for almost 12 hours now, and it's been "all green" the whole time.
Re: Incident with GitHub Actions, API requests, Codespaces, Git operations, Issues
#37I'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.
Add some kind of exponential backoff to be a good citizen!
Re: Incident with GitHub Actions, API requests, Codespaces, Git operations, Issues
#38Whew, 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.
It's been like that for at least 6 hours, randomly appearing. I would take a pause and try again and then it would work, but now it's definitely much more persistent. Guess it's time to go play some video games.... https://xkcd.com/303/
Here you go:
$ while ! git push my; do sleep 1; done
Re: Incident with GitHub Actions, API requests, Codespaces, Git operations, Issues
#39Here we go again. GitHub going completely down at least once a month as I said. [0] So nothing has changed. That is excluding the smaller intermittent issues. Let's see if anyone implemented a self-hosted backup or failsafe just in case. Oh dear. [0] https://news.ycombinator.com/item?id=30149071
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.
Re: Incident with GitHub Actions, API requests, Codespaces, Git operations, Issues
#40Whew, 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.
same here, I was having internet issues yesterday, and now that my internet is working github isn't, haha.