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: 2, Insightful) by Anonymous Coward on Friday April 24 2020, @12:32PM (12 children)
It's git, so you don't /need/ a central repository to exchange commits; you can just sync between everyone else ("origin" is just another remote).
Take your code, push it somewhere else, and keep partying...
Stupid 20-second-attention coder kids, learn to use your tools
(Score: 1, Interesting) by Anonymous Coward on Friday April 24 2020, @01:07PM
If I'm even remotely interested in work project or open source project, I clone it and then add it to my overnight cron job that does a git fetch on all of my repositories. If Github, a Gitlab or Gitea instance, or the company Bitbucket server are down I am operating at most 24 hours behind the latest version. My directory of open source git repos on my own machine has almost a hundred projects and takes up less than 200GB of space.
(Score: 0) by Anonymous Coward on Friday April 24 2020, @01:47PM
Management wants a central repo that they can look at to make irrational decisions.
(Score: 4, Interesting) by PiMuNu on Friday April 24 2020, @02:04PM (8 children)
> Stupid 20-second-attention coder kids, learn to use your tools
Most folks have a commit/code sharing/release procedure. It's a shame, if I am going to do a release and then find the release branch is unavailable because it is hosted on some server that is broke.
Nb: Sure, it's possible to ignore the procedure. But it rarely ends well (e.g. are you going to email all the clients/deployment team/whoever and tell them "for today's release, please clone it off http://mydodgyhomebrewserver.com") [mydodgyhomebrewserver.com]
Most folks use an issue tracker to manage issues, bugs etc. It's a shame, if the issue tracker's server goes down so I can't even see the jobs that need doing, or my customers can't post bugs (not that I ever have any bugs).
Most folks host their documentation somewhere, rather than using printed documentation. It's tough times, if my customers can't pull down the documentation because it's hosted on a blinged server.
Nb: github is pushing the use of their servers for more than just git nowadays. They are trying to beat down gitlab.
(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.
(Score: 0) by Anonymous Coward on Friday April 24 2020, @02:27PM
The "dodgy home brew server", as you call it, is probably a lot more available than github is.
And AFAIK this is the way Linux is developed, the reason for git's existence.
(Score: 1, Touché) by Anonymous Coward on Friday April 24 2020, @11:29PM
Tell that to the CI/CD system that starts with a git clone from github. Or QE setting up test environments from github.
There might be a *whole* lot of infrastructure that starts from github.