Related to the Twitter source code leak, perchance?
Given that looking at repos is just about the only thing that I can do then I'd say that seems unlikely.
I was more implying that this could be a result of an attack borne out of retribution.
GitHub issue - resolved
91–100 of 169 posts
Re: GitHub issue - resolved
#92Earlier quoted context omitted.
Everytime something has degraded performance or is down for me: 1. check my internet connection 2. check HN 3. check official statuspage
Step #3 is unfortunately often pointless given that often either: 1. the status page is unavailable too 2. the status page reports the service as green/available even though it's red/down (maybe it's still accessible to the service pinging its health status, maybe it's "accessible" but not actually functional, maybe the engineers were too busy fixing the problem to click the button to update the status page, maybe no…
I suppose a static html page saying everything is fine hosted on the same infrastructure as your service would be an accurate indicator a good chunk of the time.
Re: GitHub issue - resolved
#93Earlier quoted context omitted.
RO system is generally probably easier to keep up than a RW system that is constantly innovating.
I Think he was referring to Google Search in general. I've never witness since Google went live in 1998 any Google Search downtime. Probably happened but I can not remember it.
Google Search is still a RO system - you are mostly just retrieving information from a search index.
Re: GitHub issue - resolved
#94Now's a good opportunity to ask about alternative Git hosts. What other services do HNers use?
I've been unwilling to host any personal projects on GH after Copilot launched and it because clear that GH/MS doesn't really respect the authors of the code they host. Honestly open source in general has gotten a little less compelling to me after Copilot. The recent security issue at GH has also turned me off even more on Git hosting services.
For closed source projects maybe it's just best to store encrypted backups off site and spin up a self hosted option whenever collaboration is needed. Seems pretty inefficient though.
Re: GitHub issue - resolved
#95Now's a good opportunity to ask about alternative Git hosts. What other services do HNers use? I've been unwilling to host any personal projects on GH after Copilot launched and it because clear that GH/MS doesn't really respect the authors of the code they host. Honestly open source in general has gotten a little less compelling to me after Copilot. The recent security issue at GH has also turned me off even more on…
I’ve been happy with SourceHut
Re: GitHub issue - resolved
#96Yup. Tried pushing and got "remote: fatal error in commit_refs". Was trying to understand what I was doing wrong.
Same here haha. StackOverflow informed me that it means GitHub is down, and indeed it was. I have to wonder if Git could somehow report this better. I guess it depends on exactly how GitHub is down, but "fatal error in commit_refs" made me worry that my local repo was somehow hosed.
It reports what it has, if it manages to connect but fetching the metadata or whatever fails, that’s what it’s going to report.
If it can’t even connect it’ll tell you that, but I would assume on github the client will always manage to connect unless their entire network is down.
Re: GitHub issue - resolved
#97Earlier quoted context omitted.
Everytime something has degraded performance or is down for me: 1. check my internet connection 2. check HN 3. check official statuspage
HN is de facto the fastest secondary source for any current event related to tech.
I also use it for connectivity check. Most other sites have so much ads and cookies it creates long lags with adblock in some older systems I use. So I point to HN and get a really fast response that the web is working
Re: GitHub issue - resolved
#98Why GitHub is down so often? Why is it not possible to keep it up 100% of time (without counting physical failure)?. I haven't seen any down time for my system (it has hundreds of thousands of users online) in months since I have completed the setup.
I truly doubt you are running at the scale of GitHub both in terms of users, complexity, and amount of data.
It’s probably more a thing of dev velocity. If you aren’t changing anything it’s easy to keep your system operational.
Re: GitHub issue - resolved
#99Earlier quoted context omitted.
RO system is generally probably easier to keep up than a RW system that is constantly innovating.
I Think he was referring to Google Search in general. I've never witness since Google went live in 1998 any Google Search downtime. Probably happened but I can not remember it.
You don't notice when their indexers cannot write; preforming a search is basically RO.