stacktrace

6 ms·

1.
by stacktrace 14d ago
Agreed, it makes no sense to send out 404. Unless some agent finally went rogue with absolute permission and did `rm -rf`
2.
by stacktrace 14d ago
As is Claude
3.
ChatGPT outage – Resolved(chatgpt.com)
362 points by stacktrace 14d ago|318 comments
4.
by stacktrace 14d ago
Ahh, thanks for pointing it out. But it's rather interesting that Claude recognised the outage quicker on their status page than Grok.
5.
by stacktrace 14d ago
Not just claude, even grok seems to be down - https://status.x.ai/ If I didn't know any better, I would have said Grok is using Claude behind the hood. But definitely curious now why it’s happening with both these LLM
6.
Critical Next.js RCE Still Missing from GitHub Advisory Database and OSV(api.github.com)
2 points by stacktrace 15d ago|2 comments
7.
by stacktrace 15d ago
We use Grype for container vulnerability scanning, but the recent `GHSA-2xp9-vwfh-vxw4` (CVSS 9.5 rating) vulnerability, which was initially reported on repository advisory on 25th Aug, was completely missed by our scanners. Even our socke
8.
by stacktrace 9mo ago
> It's still a big issue that the models will make up plausible sounding but wrong or misleading explanations for things, and verifying their claims ends up taking time. And if it's a topic you don't care about enough, you
9.
by stacktrace 10mo ago
Will you consider it a stalemate if no party is able to make any further moves?
10.
by stacktrace 10mo ago
Really cool project! We had a situation a while back where some of our e2e tests needed the DB to be in very specific states. Technically we could have handled it with fixtures/transactions/schema resets, but doing that cleanly ac
11.
by stacktrace 10mo ago
Elixir is a great tool for exploring and cross-referencing the Linux codebase but for a new person, Linux can come across as very intimidating and complicated. The above explorer makes it very interesting to explore the codebase. This is ki
12.
by stacktrace 10mo ago
> API rate limit exceeded for 106.51.68.199. (But here's the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.) The GitHub APIs that you are using to list files are getting rate
13.
by stacktrace 10mo ago
Exactly. AWS has its own quirks and frustrations, sure but at the end of the day, I’m not using AWS just for raw compute. I’m paying for the entire ecosystem around it: security and access management, S3, Lambda, networking, monitoring, re
14.
by stacktrace 10mo ago
Very interesting read! But I want to point out a small correction - the DNS collapse issue at HAProxy, along with O(N^2), also had some O(N^3) code paths, which is just mind-blowing. Also, I believe this should be the correct GitHub issue l
15.
by stacktrace 10mo ago
> Even an improvement of a few second per iteration can compound into hours of time savings, both for you and your fellow contributors Completely agree with this. I’ve recently been dealing with building few CI workflows, and honestly, I
16.
by stacktrace 10mo ago
This type of possibility really worries me. Archive.is is much closer to actual history in many ways. If the data there starts getting corrupted or biased, there’s no way to know if what was truly there. The idea that the permanent record o