Humanity has surpassed another barrier!
A Benchy-shaped object was printed in under 60 seconds.
Nobody knows why. Civilization advances anyway. 😂
Bravo, roetz4.0!!!
https://t.co/OijbKbaPsK
I’ve been cranking out code with Opus 4.7 lately, but when it comes to reviewing, I bring in backup.
Composer 2.5 became my surprise sidekick. Along with Opus, it's like they’re on a bug-hunting adventure, finding even more! What’s your go-to LLM combo for code reviews?
Supply chain attacks can’t be solved with one silver bullet. They need a systemic approach.
For every dev layer (not just npm, but CI, Docker, and your editor) ask 4 questions:
1. How can we reduce dependencies?
2. Isolation
3. Update control
4. Review
Thread ↓
The most obvious supply-chain safety knobs just broke a Python lockfile for me in
the dumbest possible way.
I had `uv`'s `exclude-newer = "30 days"` enabled on a project, plus a global PyTorch
`extra-index-url`.
Result: "No solution found when resolving dependencies", but why?!
That combo is self-sabotage: the PyTorch mirror contains sympy/fsspec/networkx
wheels with no upload timestamps. uv cannot prove they are older than the
cutoff, so it filters them out and tells you your pin is unsatisfiable.
The weirdest part:
The package exists. The metadata path is wrong.
Resolution: make the PyTorch index `explicit = true`, then route only `torch`
/ `torchaudio` / etc. through it. Done!
Full story: https://t.co/UWSUIvVSv0
@adrienpoly I suggest setting up any kind of monitoring system to get a glimpse of what processes leak and when. Also an instrumentation/profiling for the apps is a good choice too. Have you tried NewRelic or DataDog?
"It's surprising to me that there isn't more pressure yet to cut costs at companies paying such princely sums for their SaaS software. But I think it's coming. Someone is going to look at those margins and see an opportunity." https://t.co/iLv7eVbQWu
MRSK hype is blazing at full capacity. So, will it change the deployment game and make deploying Docker containers dead simple? Head of SRE @agonsmith shares our attempt at an objective analysis of MRSK's promises, potential, and more. https://t.co/SdKh4NHZ1R
Ok, let’s say it one more time: it’s called “imgproxy”.
Not “ImgProxy”.
Not “imgProxy”.
Not “IMGproxy”.
Not “ImageProxy”.
Not even “Imgproxy”.
Just “imgproxy”.
@Saint_Monro@romanshamin Мои искренние извинения. Мы на тот момент и правда не нанимали в SRE команду, но все равно должны были ответить и дать вам об этом знать. Сделаем все, чтобы такого не повторилось!