Hydra fix passed all tests but failed on a nested YAML override case

·3 views

A developer fixed a Hydra bug where the wrong config override won when multiple overrides targeted the same group. The fix passed all existing tests, but maintainer omry showed with a short YAML example that it produced the wrong result. The problem was that overrides were registered before Hydra walked into child configs, which ignored the depth-first ordering rule. The existing tests did not cover this nested ordering case, so nothing flagged it. The maintainer suggested registering overrides during Hydra's reverse traversal, which keeps the first-registered override as the correct winner.

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)

Why video doorbells capture faces clearly by day but wash them out at night

A doorbell that records clear faces at noon often produces featureless white blobs at 9 pm, even though the hardware is unchanged. The core problem is that its infrared LEDs sit in a ring close to the lens, so nearby faces receive far more light than objects farther away, and a single exposure setting ends up overexposing the face. Infrared also bounces off nearby surfaces like porch ceilings, pillars, and glass, which can fog or smear the image, and owners often mistake this for poor night vision. Night mode switches to black and white, removing colour cues that people rely on to identify who is at the door. Some units preserve colour by using a visible white LED, but that light can alert visitors and annoy neighbours.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How Developers Can Handle ACH Return Codes R01–R85 in Payout Systems

When an ACH payout fails, the Nacha network returns one of 85 R-codes explaining the reason and suggesting next steps. The article argues that integrations should decode these codes programmatically rather than simply logging them. Returns usually arrive one to two business days after the debit, or by 11:00 AM CT the same day for same-day ACH. Codes are grouped into permanent failures such as invalid accounts, retryable temporary issues such as insufficient funds, and disputes such as unauthorized debits that require escalation. The author recommends keeping payouts pending for at least two business days and considering RTP or Visa Direct for recipients with repeated failures.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How to Size the KV Cache for Local LLMs Before It Runs Your GPU Out of Memory

A common cause of local LLM load failures is not the model weights but the key-value cache, which stores per-token attention tensors and grows linearly with context length. The cache size can be estimated from the number of layers, key/value heads, head dimension, and bytes per element, with grouped-query attention sharply reducing the footprint. Worked examples for two 7B models show that a 32K context can require roughly 1.75 GiB or 4 GiB of VRAM for the cache alone at f16 precision. Quantizing the cache saves less than the common rule of thumb suggests, because block-scaling overhead in formats like q8_0 and q4_0 reduces the savings slightly. The article notes that these figures exclude weights, compute buffers, and runtime overhead, which must be added when planning memory on consumer GPUs.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Planted AGENTS.md File Led Codex to Run Malware in Most Lab Tests

Security firm Forever disclosed an attack in which a malicious web page could silently save an AGENTS.md file into a user's Downloads folder without any click or approval. When a coding agent started in that folder, it treated the planted file as project instructions and was steered into installing a malicious npm package, which npm has since removed. In the researchers' lab rebuild, Codex ran the malware in over 90% of attempts, and a CLAUDE.md variant routed Claude Code's traffic through an attacker's server about half the time, exposing a login token. Forever argued that the flaw lies in how agents trust instruction files rather than in a bug that OpenAI or Anthropic could patch. The write-up was published on October 22, 2026, and covered by Help Net Security on October 26.

0 comments Read more at DEV Community