111–120 of 123 posts
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.
Never really realized that github had many technical incidents lol
Earlier quoted context omitted.
They had massive problems with their main database cluster (MySQL). If you read through their engineering blog, most of the outages were related to their growth and the main database cluster. They moved workloads for some features to different clusters, but that's only to buy more time. Eventually they'll do proper shredding (by user or org I guess, not by feature) but that takes time. Their engineering blog is full…
i've noticed this too .. the real head-scratcher is how a solid chunk of github's db & infra folks left to join a database startup, one of them even becoming its ceo!! if they had made github db/infra super-stable before this, it would be a vote of confidence in their new company, but instead imho it is the opposite
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.
Same here got rejected when push. ! [remote rejected] HEAD -> main (Internal Server Error)
Earlier quoted context omitted.
i've noticed this too .. the real head-scratcher is how a solid chunk of github's db & infra folks left to join a database startup, one of them even becoming its ceo!! if they had made github db/infra super-stable before this, it would be a vote of confidence in their new company, but instead imho it is the opposite
Which one are you referring to?
Wow, suddenly staying on-prem with old rusty Jenkins is not so bad. (It has its issues, but at least I had better service levels in last 12 months)
Earlier quoted context omitted.
They had massive problems with their main database cluster (MySQL). If you read through their engineering blog, most of the outages were related to their growth and the main database cluster. They moved workloads for some features to different clusters, but that's only to buy more time. Eventually they'll do proper shredding (by user or org I guess, not by feature) but that takes time. Their engineering blog is full…
i've noticed this too .. the real head-scratcher is how a solid chunk of github's db & infra folks left to join a database startup, one of them even becoming its ceo!! if they had made github db/infra super-stable before this, it would be a vote of confidence in their new company, but instead imho it is the opposite
Earlier quoted context omitted.
i've noticed this too .. the real head-scratcher is how a solid chunk of github's db & infra folks left to join a database startup, one of them even becoming its ceo!! if they had made github db/infra super-stable before this, it would be a vote of confidence in their new company, but instead imho it is the opposite
DB and infra folks are often tasked with shoveling shit uphill, and aren't in total control over how data or schemas get organized.
if they were all sharding experts why wasn't github sharded properly. other large mysql shops have solved this, all the way back to the days of yahoo and flickr and livejournal
Earlier quoted context omitted.
It's OK to be frustrated since we rely on GitHub so much, but this is unkind. Software is complex. GitHub operates at a scale few of us work at. There are people at the other end doing their best traversing complex internal systems (organization and tech). I would argue GitHub has done more for societal good than most tech ventures, by the way.
GitHub actions has been like this for years now. Years. Years!!!! And the crazy thing is you see people on HN demanding that some one person side project/SaaS has to be at 100% uptime with multiple failovers, automatic scaling, etc. etc. There is such an emphasis on scalability on HN and yet... you just brush that all away because "software is tough." Yeah, no shit. Poor Github. They are also Microsoft now. One of th…