5 ms·

Whew, 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 whil

Whew, 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.

forgingahead 5y ago
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/ https://xkcd.com/303/
- cik 5y ago
  Also yesterday depending on where you were in the world.
- 5e92cb50239222b 5y ago
  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).
  - klibertp 5y ago
    Having been on the receiving end of things like this: please, make the sleep longer. Adding more requests to already malfunctioning system is not a good way to help in fixing it.
  - forgingahead 5y ago
    Thanks but no thanks - no way am I doing anything to my core app repos when the repo host is fritzing out. This is one of those moments to go for a walk (or bed, depending on your timezone).
  - TimWolla 5y ago
    -f does not sound like a good idea to me in a script like that.
    - 5e92cb50239222b 5y ago
      Good point. I just copy-pasted it from the terminal, as it made sense in my particular situation. I'll remove it.
    - renata 5y ago
      Also pretty much every usage of -f would be better off being --force-with-lease so you're less likely to accidentally clobber someone else's work. I have git fpush aliased to "push --force-with-lease" and try to spread the gospel when possible :)
      - kubanczyk 5y ago
        Yeah, I learned it by using magit or vscode's other magit and they both default to --force-with-lease.
ahmadrosid 5y ago
Same here got rejected when push. ! [remote rejected] HEAD -> main (Internal Server Error)
- mullikine 5y ago
  haha I thought I had finally made one too many git commits (I'm an over-commiter).
dgellow 5y ago
Yep, same here! Good time to make a new coffee :)
lukeinator42 5y ago
same here, I was having internet issues yesterday, and now that my internet is working github isn't, haha.
m3nu 5y ago
dito
adelarsq 5y ago
Time to take some coffee and configure Vim
- wvh 5y ago
  I hope you have a lot of coffee.
- jamil7 5y ago
  But muh plugins are all on Github...
- polishdude20 5y ago
  Don't you guys have other features and stuff to work on locally? What is this "time to take a break when GitHub is down"? I'm saying this a bit tongue in cheek btw :)
  - websap 5y ago
    All my features are part of 1 PR, the PR contains no code to avoid bugs, the features are in my head.
    - coolspot 5y ago
      I can’t see any deficiencies in this approach.
distartin 5y ago
Never really realized that github had many technical incidents lol
- zh3 5y ago
  It's the new Hotmail ;)

forgingahead 5y ago

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/ https://xkcd.com/303/

cik 5y ago
Also yesterday depending on where you were in the world.
5e92cb50239222b 5y ago
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).
- klibertp 5y ago
  Having been on the receiving end of things like this: please, make the sleep longer. Adding more requests to already malfunctioning system is not a good way to help in fixing it.
- forgingahead 5y ago
  Thanks but no thanks - no way am I doing anything to my core app repos when the repo host is fritzing out. This is one of those moments to go for a walk (or bed, depending on your timezone).
- TimWolla 5y ago
  -f does not sound like a good idea to me in a script like that.
  - 5e92cb50239222b 5y ago
    Good point. I just copy-pasted it from the terminal, as it made sense in my particular situation. I'll remove it.
  - renata 5y ago
    Also pretty much every usage of -f would be better off being --force-with-lease so you're less likely to accidentally clobber someone else's work. I have git fpush aliased to "push --force-with-lease" and try to spread the gospel when possible :)
    - kubanczyk 5y ago
      Yeah, I learned it by using magit or vscode's other magit and they both default to --force-with-lease.

ahmadrosid 5y ago

Same here got rejected when push. ! [remote rejected] HEAD -> main (Internal Server Error)

mullikine 5y ago
haha I thought I had finally made one too many git commits (I'm an over-commiter).

dgellow 5y ago

Yep, same here! Good time to make a new coffee :)

lukeinator42 5y ago

same here, I was having internet issues yesterday, and now that my internet is working github isn't, haha.

m3nu 5y ago

dito

adelarsq 5y ago

Time to take some coffee and configure Vim

wvh 5y ago
I hope you have a lot of coffee.
jamil7 5y ago
But muh plugins are all on Github...
polishdude20 5y ago
Don't you guys have other features and stuff to work on locally? What is this "time to take a break when GitHub is down"? I'm saying this a bit tongue in cheek btw :)
- websap 5y ago
  All my features are part of 1 PR, the PR contains no code to avoid bugs, the features are in my head.
  - coolspot 5y ago
    I can’t see any deficiencies in this approach.

distartin 5y ago

Never really realized that github had many technical incidents lol

zh3 5y ago
It's the new Hotmail ;)