Which AI model is it this time?
[flagged]
Incident with Github.com [resolved]
151–160 of 1001 posts
Re: Incident with Github.com [resolved]
#152Ah, so that's what the agent meant by summarizing a documentation page as "Unicorn!" I'd thought it was a very colorful hallucination (it's just GitHub's (unicorn-themed) failure page). Gathered details on embedding request syntax from Unicorn! · GitHub I was querying docs to figure out how to set up RAG to query docs locally. Alas.
i'm surprised the agent didn't take into consideration the http status code
Re: Incident with Github.com [resolved]
#153Re: Incident with Github.com [resolved]
#154Re: Incident with Github.com [resolved]
#155To everyone who is angry: calm down. Github’s servers are constantly on fire as their usage increased something like 50x due to LLM sloppers pushing large amounts of trash code Unless you have a emergency hotfix (you don’t), go hit the gym or walk outside. If a work tool going down triggers you enough mentally to start angrily ranting online, it’s a sign you need to chill out and focus more on your health
What if we're not angry and just perplexed? Do we calm down further or can we still ask questions?
Re: Incident with Github.com [resolved]
#156You would think for a company that has close to a monopoly of developer mind share wrt git that they'd maybe put in the bair minimum to get several 9s.
Re: Incident with Github.com [resolved]
#157Re: Incident with Github.com [resolved]
#158Earlier quoted context omitted.
Ideally something like IPNS to have a mutable ref based on (repo, pubkey, branch) to resolve a commit hash, a DHT for who has what commit hashes, and then just p2p transfers. You could still have a github or gitlab for issues and CI, but code (and maybe issues) could all be p2p like git is already designed for. Your forge could also act as a peer for code cloning, of course.
I do not need it to be meaningfully different than Github, it sounds like that introduces additional complexity. I just want Github that works.
The complexity is in locating what is already a distributed database item (git is fundamentally already designed that way), just using a protocol meant for that. Basically just support `git clone` with e.g. IPFS URIs.
Re: Incident with Github.com [resolved]
#159To everyone who is angry: calm down. Github’s servers are constantly on fire as their usage increased something like 50x due to LLM sloppers pushing large amounts of trash code Unless you have a emergency hotfix (you don’t), go hit the gym or walk outside. If a work tool going down triggers you enough mentally to start angrily ranting online, it’s a sign you need to chill out and focus more on your health
No one ever has to commit anything time sensitive.
Re: Incident with Github.com [resolved]
#160To everyone who is angry: calm down. Github’s servers are constantly on fire as their usage increased something like 50x due to LLM sloppers pushing large amounts of trash code Unless you have a emergency hotfix (you don’t), go hit the gym or walk outside. If a work tool going down triggers you enough mentally to start angrily ranting online, it’s a sign you need to chill out and focus more on your health
Actually, I do have an important fix for a deal we are trying to close that does need to go out. And I am paying GitHub to host this. Once or twice, I can see, but GitHub's SLA is getting worse than just hosting it myself, and that's the entire reason I pay GitHub.