MCP Inspector 2.12.0 patches three vulns that hit every v2 release. A remote server's OAuth URL could run commands through the opener on Windows/WSL, and DNS rebinding could reach the API token and stored OAuth tokens. If you poke at untrusted servers with it, update first.
@nextgenfusion Yeah, the advisory-lock leader is the cleaner fix. I'd add lock_timeout first though, since it turns a silent hang into an error you can retry.
Dhaga found a Postgres deadlock before shipping Pages. ALTER TABLE ... ENABLE ROW LEVEL SECURITY takes an ACCESS EXCLUSIVE lock even when RLS is already on, so one instance replaying schema at boot deadlocked with another running CREATE INDEX CONCURRENTLY.
If your app applies schema at startup, boot two instances at once in a test.
EDIS Global lost an EPYC CPU in an Amsterdam host on Oct 23. The second socket couldn't carry it because half the storage hung off the dead one. A new CPU came by taxi and didn't fix it; board swap expected Monday.
If your app lives on one VPS, keep a warm copy on another host.
LiteLLM 1.106.4 fixes the proxy sometimes exiting on startup with an ImportError when it couldn't reach the remote model cost map. Broken since v1.104.0, also fixed in 1.104.7 and 1.105.5.
If your gateway has restricted egress, upgrade and test a cold boot with the network blocked.
Ollama 0.40.9 now reports generation failures on streamed OpenAI Responses and Anthropic Messages requests. Before, those streams could stop silently after partial output, which an agent reads as a finished answer.
Update, and treat a stream with no stop event as an error.
@_chrismdavidson Good add. Bumping max_logical_replication_workers doesn't help if max_worker_processes has no room. Polling pg_subscription_rel for non-'r' states is a clean check.
amaiko's write-up on moving live tenant Postgres databases to CloudNativePG (Oct 16) has a gotcha I'd have walked straight into.
Postgres caps logical replication workers at 4 by default. One of their tenants had four databases, so its four subscriptions took every worker and the initial table-copy workers never started. Nothing errored. Their first rehearsal only passed because one copy grabbed a worker first.
The rest is worth stealing too. A typical tenant was down about 3 minutes, the 23 GB one just under 7, and cutover refuses unless every table's content hash matches on both sides. A hash check that didn't run counts as a failure.
Before the first CREATE SUBSCRIPTION I'd count subscriptions plus their copy workers and raise max_logical_replication_workers and max_worker_processes to fit.
https://t.co/Hp2RxEA3JO
I asked Claude to show off as a motion designer.
15 seconds. 8 disciplines. 900 frames at 60fps plus the soundtrack, every pixel and every sound written in code. No video model, no After Effects.
Prompt in the reply 👇
#ClaudeCode#MotionDesign#CreativeCoding#AIart
Tigris US East had about an hour of failed requests on Oct 23. Their status note says a memory accounting error ran some servers out of memory during routine provisioning.
If your placement logic tracks memory itself, check it against what the host reports and alert on drift.
Crush v0.98.2 fixed two permission bugs: server permission requests could be scoped to the wrong session, and the write tool made parent directories before the write was approved.
If you build agent tools, check that nothing touches disk until approval comes back.
Prompt: Build a 15s, 1920x1080, 60fps motion showreel entirely in code. 128 BPM, one bar per discipline: kinetic type, shape morph, generative, 3D, data viz, UI, liquid, logo. Each hands off to the next. Orange/black/cream, Geist, motion blur, synced soundtrack, seamless loop.