Incident with GitHub Actions, API requests, Codespaces, Git operations, Issues

Post by ryanbrunner » Thu, Mar 17, 2022, 2:53 PM UTC

arpinum wrote: post #20

These 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.

Post by 5e92cb50239222b » Thu, Mar 17, 2022, 2:54 PM UTC

avar wrote: post #35

I'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.

Post by forgingahead » Thu, Mar 17, 2022, 2:55 PM UTC

5e92cb50239222b wrote: post #38

forgingahead wrote: post #14

Earlier quoted context omitted.

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 Works for me eventually, although commits do not appear in web interface (they do in the actual repository).

Post by fishywang » Thu, Mar 17, 2022, 3:00 PM UTC

Post by 5e92cb50239222b » Thu, Mar 17, 2022, 3:02 PM UTC

TimWolla wrote: post #49

5e92cb50239222b wrote: post #38

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.