Cache API silently strips URL fragments, causing chunk overwrites in model storage

·3 views

A developer discovered that their highest-quality AI model tier had never successfully loaded in production due to a subtle Cache API behavior: URL fragments are stripped during both put and match operations. This meant chunk keys like 'key#0' and 'key#7' were treated as the same cache entry, so each new chunk write overwrote the previous one, leaving only the last-written manifest blob. When the app read the cache, it retrieved the tiny JSON manifest instead of the model and passed it to ONNX Runtime, which correctly rejected it as an invalid protobuf. The fix involved switching from fragment-based keys to path-segment keys and adding a magic-byte plus size-floor validation before passing cached bytes to any parser.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Spring AI Brings Model Context Protocol Support for Java MCP Clients and Servers

Model Context Protocol (MCP) is a standardized communication layer that allows AI applications to connect with external tools, resources, and systems without building custom integrations for each one. As AI systems grow more complex, maintaining separate integrations for services like GitHub, CRM platforms, and databases becomes difficult to scale across multiple applications. MCP solves this by introducing a common protocol where an MCP client inside the AI application communicates with one or more MCP servers that expose capabilities through a unified interface. Spring AI now provides dedicated starters and APIs that enable Java developers to build both MCP clients and MCP servers within Spring Boot applications. This approach separates the LLM reasoning layer from the integration layer, making AI architectures more modular and easier to maintain.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Migration Canary: A Lightweight Method to Safely Verify Database Schema Changes

A migration canary is a small, continuously running process designed to verify that database schema changes are safe during the transition window between old and new schemas. As modern systems increasingly rely on independent deploys and AI-generated migrations, a failed schema change can silently corrupt data across multiple services rather than triggering an immediate, obvious failure. The approach follows an expand-canary-measure-gate cycle, where a lightweight worker dual-writes test records and reads them back through both old and new code paths while tracking metrics like read parity, serialization errors, and latency. The canary integrates with rollout tools such as Flagger or Argo Rollouts to automatically block destructive schema steps — like dropping columns — until sufficient error-free runtime has been observed. In a real-world example, this method caught a faulty JSON parser affecting a subset of rows during a 24-hour verification window, preventing a data integrity incident before it reached production.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Developer releases zero-dependency CLI tool to detect OpenAPI spec and code drift

A developer has released oas-drift, an open-source command-line tool that identifies mismatches between an OpenAPI specification and a Python codebase. The tool detects three types of drift: routes defined in the spec but missing from code, routes in code not listed in the spec, and paths where the HTTP method differs between the two. Built using only Python 3.11's standard library with no external dependencies, it parses source files using Python's ast module without executing any code, ensuring fully deterministic output. Unlike many CI-facing tools, oas-drift exits with code 0 regardless of findings, leaving the decision to fail a build to the development team's own policy. The tool supports JSON output for machine-readable reports, making it easy to integrate into CI pipelines alongside filtering tools like jq.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Developer Builds Tool to Evaluate Reliability and Bias in LLM Judge Models

A developer has created a lightweight open-source evaluator designed to assess the performance of large language models when used as automated judges. The tool tests LLM judges across several dimensions, including consistency across repeated runs, position bias, sensitivity to response length, and accuracy in preferring higher-quality answers. Each test case in the dataset includes a task rubric, an ideal response, and a negative response — where the latter represents a less preferred rather than necessarily incorrect answer. The project, currently around 200 lines of code, is publicly available on GitHub under the name JudgeDjudge. The developer is actively seeking community feedback on additional failure modes or alternative approaches to evaluating LLM judges.

0 comments Read more at DEV Community