Canonical vs Railway

Canonical announces Zephyr 26.04 LTS, delivering up to 15 years of support for MCU-grade devices

Canonical today announced the upcoming release of Zephyr 26.04 LTS, an enterprise distribution providing a trusted Real-Time Operating System (RTOS) to solve critical Cyber Resilience Act (CRA) compliance and developer experience challenges. Also announced: Ubuntu coming soon to Snapdragon X2 Series platforms, and a new kernel release strategy for faster CVE fixes.

Migrate Cloud TPU API Workloads to Compute Engine

This technical migration guide explains moving TPU workloads from Google Cloud's deprecated Cloud TPU API to Compute Engine instances. The Cloud TPU API is no longer under active development and future TPU hardware generations (starting with TPU7x) are supported only through Compute Engine or Google Kubernetes Engine. Migration requires flag and command mapping (e.g., accelerator-type -> machine-type, tpu-vm ssh -> compute ssh), checking different quota metrics (preemptible vs family quota) and provisioning models (FLEX_START, SPOT, STANDARD, RESERVATION_BOUND), and adjusting startup scripts and images (some Compute Engine accelerator images lack tools like docker). The guide documents practical troubleshooting: using SPOT to probe capacity, checking both quota metrics via the Cloud Quotas API, handling silent failures where RUNNING != ready, and other pitfalls encountered during real migrations.

• Google's Cloud TPU API is no longer under active development; new hardware generations starting with TPU7x are supported only via Compute Engine or GKE.
• Compute Engine uses different flags and flows (e.g., --machine-type=ct6e-standard-1t, --image-family, --request-valid-for-duration, --provisioning-model=FLEX_START) compared with the Cloud TPU API.
• Flex-start provisioning on Compute Engine consumes preemptible quota (PREEMPTIBLE-TPU-V6E-per-project-region) and falls back to the family quota; quota and capacity are separate and reported by different APIs.

Railway urges users to revoke keys after cyberattack

Developer platform Railway confirmed a cyberattack that allowed hackers to access and decrypt some customer secrets, including API keys and passwords. The company urged all users to revoke and rotate their credentials, as the breach may have compromised encrypted environment variables. The attack is likely part of a broader campaign targeting AI inference providers, with possible ties to AI distillation attacks. Railway paused builds during investigation but has since restored service. Affected user count and root cause are undisclosed. Railway plans to publish a post-mortem. The incident follows recent warnings from CISA about China-based AI companies conducting large-scale attacks on U.S. firms.

• Railway confirmed a cyberattack allowing hackers to access and decrypt some customer secrets.
• The company urged all users to revoke and rotate API and cloud keys.
• The attack may be part of a broader campaign targeting AI inference providers.

Introducing Railway Authentication via identity-aware proxy

Railway Authentication implements an identity aware proxy at the service or environment level to lock down sensitive http endpoints

AI Agent Frameworks Have a Critical Engineering Flaw

The author argues that the current enthusiasm for AI "agents" and hot frameworks distracts from the real engineering challenges of production systems. They define a true agent as a system with an objective that decides next actions, handles failure, and knows when it is done. In production, most agent deployments are narrow, purpose-built pipelines (e.g., support triage, document extraction, code review). Teams that succeed focus on tool design, failure handling, and observability rather than swapping models. The author highlights a persistent retrieval problem in RAG pipelines—incorrect chunking and metadata cause context loss and hallucinations—and recommends architectural patterns (plan-then-execute, separate retrieval from reasoning, explicit handoffs) and better data representations over framework chasing.

• Author defines an 'agent' as a system with an objective that decides what to do next, handles failure, and knows when it is done.
• Most production AI agent deployments are narrow and purpose-built (examples: customer support triage, document extraction, code review).
• Successful teams prioritize tool design, failure handling, and observability over only upgrading model versions.