Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

GitHub was down

githubstatus.com

Post reply on HN
Print view View original

81–88 of 88 posts

Re: GitHub was down

#81

Post by jtdev »

thanatos_dem wrote: post #78
jtdev wrote: post #76

Earlier quoted context omitted.

Glancing at your comment history, I can see that you believe your opinions are edicts and nobody can express differing opinions without you pulling your quasi moralistic hall monitoring trope. The fact is, tech is now under the influence of the woke mob, and I believe that's objectively bad for tech, the people who work in tech, and the prospect of solving REAL problems with tech.

Then just find a new career maybe? I sure as hell wouldn’t hire you at this point.

No. I’ll continue to use my skills to solve real problems and voice my opposition to the groupthink mob.

Re: GitHub was down

#82

Post by serverlessbird »

smallnamespace wrote: post #25
justaguy88 wrote: post #8

What's the best practice for high availability (self-hosted?) repositories? Is there a pass-through proxy for git? Or a leader-follower arrangement that is nice, with a proxy server?

If you're already using a cloud provider, they [1] all [2] have [3] private git repo services. You can set up a cronjob to sync them, or some have built-in config to do the mirroring [4]. I used Google's mirroring option before. It was fine, but we never had to use it (local copies were sufficient when GH was slow one day). [1] https://cloud.google.com/source-repositories [2] https://aws.amazon.com/codecommit/ [3] ht…

GitHub better use something more trusted. AWS outages is so well known :/

Re: GitHub was down

#83

Post by serverlessbird »

smallnamespace wrote: post #25
justaguy88 wrote: post #8

What's the best practice for high availability (self-hosted?) repositories? Is there a pass-through proxy for git? Or a leader-follower arrangement that is nice, with a proxy server?

If you're already using a cloud provider, they [1] all [2] have [3] private git repo services. You can set up a cronjob to sync them, or some have built-in config to do the mirroring [4]. I used Google's mirroring option before. It was fine, but we never had to use it (local copies were sufficient when GH was slow one day). [1] https://cloud.google.com/source-repositories [2] https://aws.amazon.com/codecommit/ [3] ht…

We don`t need to forget about small but better providers, like DNS made easy or it`s younger brother Constellix I also read one guy at webhosting talk. he said DNS simple have some new good features

Re: GitHub was down

#84

Post by swat535 »

bombcar wrote: post #66
usui wrote: post #53

Earlier quoted context omitted.

Why would that be the case? Shouldn't it be more common to find deployments happening early Monday morning? It's common practice to avoid potentially bug-inducing changes right before the weekend hits

If you’re trying to minimize impact to employees you deploy Monday or Tuesday morning. If you’re trying to minimize impact to business customers you deploy Friday night.

Yea exactly , Tuesdays are the ideal days to ship features, this has always been the case everywhere I've worked. Deployments on Friday is just asking for pain and Mondays are often too chaotic for a release..

Re: GitHub was down

#85

Post by thanatos_dem »

jtdev wrote: post #81
thanatos_dem wrote: post #78

Earlier quoted context omitted.

Then just find a new career maybe? I sure as hell wouldn’t hire you at this point.

No. I’ll continue to use my skills to solve real problems and voice my opposition to the groupthink mob.

Out of curiosity, what’s the last “real problem” you solved?

Re: GitHub was down

#86

Post by jtdev »

thanatos_dem wrote: post #85
jtdev wrote: post #81

Earlier quoted context omitted.

No. I’ll continue to use my skills to solve real problems and voice my opposition to the groupthink mob.

Out of curiosity, what’s the last “real problem” you solved?

They’re real enough problems that I’d be violating legal agreements by discussing them here... so no, I won’t be doing that.

Re: GitHub was down

#87

Post by thanatos_dem »

jtdev wrote: post #86
thanatos_dem wrote: post #85

Earlier quoted context omitted.

Out of curiosity, what’s the last “real problem” you solved?

They’re real enough problems that I’d be violating legal agreements by discussing them here... so no, I won’t be doing that.

Cool, you’ve said all you needed to. You can now safely be ignored by our entire industry as far as I’m concerned.

Enjoy your lack of vertical mobility!

Re: GitHub was down

#88

Post by oomathias »

evanelias wrote: post #79
oomathias wrote: post #77

Earlier quoted context omitted.

@keithba I have build a - private - GitHub action around https://github.com/sbdchd/squawk - for Postgres - that lints all our migrations files on each PR. The action extract raw SQL from the codebase and pass them into squawk. It catches many exclusive locks migration or missing `index concurrently` that would otherwise have been release to production and causing downtime or degraded service. Maybe something you shou…

GitHub uses MySQL, not Postgres. They built the best-in-class online schema change tool gh-ost [1], and have a custom declarative schema change execution system built around Skeema [2], which contains a wealth of linters [3]. Even so, it's always possible for an engineer to submit a schema change which is detrimental to performance. For example, dropping an important index, or changing it such that some necessary col…

Thanks, I didn't know about this. Indeed nothing is failproof.
Post reply on HN