@JimmyBoonen@RBilgil@jessethanley@dhh Agree on this. Codex will always ‘run the narrow tests to prove this change works’ and they do, then ci runs the full suite and it fails. Happens super often to me.
I love how both codex and claude are both amazingly eager to poke holes into each other's specs during adversarial reviews, but then when they have to actually code the stuff they forget half the spec or half implement it.
@gilpinskyy@ClaudeDevs Yeah I must have used it 5 times and was pleased with it then yesterday I checked and it had used $50 from my emergency extra usage stash 😂
@PawelHuryn So far 4.7 consistently ignores any standards defined in Claude.md, even on a fresh context. Today I caught it twice installing modules in the wrong package or doing imports directly instead of using my ui package, not putting mutations in the right place.
Since this is happening daily at the moment, a simple thing you can do to help your clanker (or you) to avoid pulling compromised npm packages is to force them to be at least 48h old. And pin versions ofc.
🚨 CRITICAL: Active supply chain attack on axios -- one of npm's most depended-on packages.
The latest [email protected] now pulls in [email protected], a package that did not exist before today. This is a live compromise.
This is textbook supply chain installer malware. axios has 100M+ weekly downloads. Every npm install pulling the latest version is potentially compromised right now.
Socket AI analysis confirms this is malware. plain-crypto-js is an obfuscated dropper/loader that:
• Deobfuscates embedded payloads and operational strings at runtime
• Dynamically loads fs, os, and execSync to evade static analysis
• Executes decoded shell commands
• Stages and copies payload files into OS temp and Windows ProgramData directories
• Deletes and renames artifacts post-execution to destroy forensic evidence
If you use axios, pin your version immediately and audit your lockfiles. Do not upgrade.
@livingdevops You forgot when a node disappears and all pods were on it so it goes down. So you add a PDB. Now the node can’t be restarted because it violated the PDB. So you add a topology spread constraint, now your pods stay available and nodes can churn.
Wow, Germany has officially launched an alternative to Claude Code https://t.co/q7ICTHZfEZ A fully compliant Tool in collaboration with Deutsche Telekom and the Federal Ministry of Digital Affairs.
This is a very important step for an independent Europe with sovereign tech.
@AndrewCurioso@lemire Try context7, absolute life saver and I use it for everything, I’m pretty sure it would have taught Claude code to do this CI task quite quickly.