SoylentNews is people
SoylentNews
European programmers take an extended lunch break as GitHub goes TITSUP* again:
Big sack o' source GitHub is having a hellish week as the Microsoft tentacle suffered wobbles aplenty even as it tipped the scorn bucket over the emissions of the US administration.
Having fallen over in dramatic style on 21 April, seen its notifications totter on 22 April, and had trouble with Actions Workflows in the small hours of 23 April, the platform decided to take an extended lunch break today.
Twitter[1] was its usual supportive self as developers found themselves faced with the dread error code 500 and a humorous depiction of the GitHub mascot tumbling into a ravine (like the unfortunate Wile E Coyote of Looney Tunes fame).
[...] GitHub itself recognised that there were "issues" at 13:20 UTC. By 13:33 UTC, engineers reckoned they had found the source of the borkage and were
hurriedly plugging the servers back inworking on a fix.[...] Access to Vulture Central, at least, seemed to return shortly before 14:00 UTC.
The issue looked to be global, although the timing meant that much of the US remained in blissful ignorance while Europe and the rest of the world wailed.
[*] Total Inability To Service User Pulls
[1] https://twitter.com/Justin64558161/status/1252629251968376834.
[Update - looks like the issue is resolved- Ed.]
(Score: 0) by Anonymous Coward on Friday April 24 2020, @02:26PM (6 children)
What does that have to do with github being down? You do your releases and then upload the tags when it's back up. What's the problem?
Clients are using Git? Deployment team has no access to any server to sync repos? WTF? And you don't clone off anything ... you just sync a few requests that are missing...
It's a hint you are using Git wrong if all you do is "clone off" the same repo all the time.
(Score: 3, Interesting) by PiMuNu on Friday April 24 2020, @04:23PM (5 children)
> You do your releases and then upload the tags when it's back up
I'm obviously being thick. How do you share code with someone else without access to a common server? Do all of your developers share ssh keys for each other's development machine?
(Score: 2, Informative) by Anonymous Coward on Friday April 24 2020, @08:27PM (3 children)
You can email git commits to each other:
https://git-scm.com/docs/git-send-email [git-scm.com]
(Score: 0) by Anonymous Coward on Friday April 24 2020, @08:42PM
The real request pull pull request.
(Score: 2) by PiMuNu on Saturday April 25 2020, @10:02AM
?wtf? I paid x Megabucks to use github and I'm emailing patches around!
(Score: 2) by PiMuNu on Saturday April 25 2020, @10:05AM
ps: no need to use git, just run diff and patch
heck, why not just print out the difference, mail it, then type it in at the other end.
(Score: 2) by sjames on Saturday April 25 2020, @05:52PM
Setting up just Git is easy to do. Ideally, you set up a VM designated as a Git server and push to that. Use Github for public releases.