Urgent.News

What's breaking now, across thousands of outlets.

Tech

Whose Bug Was It

Twenty-three defects in the last twenty-two runs: eleven in the collector, four in config, three in other services, and five of our own. 👋 Hi, I'm Anton - a software engineer. These days I work on a platform: contracts, generated code, data paths and the tooling around them. Running notes live on my GitHub: github.com/brilliant-almazov . The count covers only the last twenty-two acceptance runs…

The wire material describes a week of integration acceptance testing for a complex system consisting of multiple services. A total of 23 defects were identified across the last 22 acceptance runs, with individual defects ranging from the collector's code to defects in other services and the acceptance agent itself.

Eleven defects were attributed to the collector's code, including issues with timeouts, watchdog thresholds, queue management, task body post, request-log row closure, delivery, priority clamping, configuration defaults, and number type overrides. Two notable defects include the issue with priorities outside the range of 0-100 being refused with an error, and configuration defaults not being set correctly by default.

Four defects were found in the configuration and stand, including an account list fix, an alert job label mismatch, a content service being switched off, and a binary carrying another binary's configuration keys. Three defects were identified in other services, such as unread results, a tenant ID mismatch, and conflicting norms between services.

The five defects identified within the acceptance side include a stale build issue, a spent scenario with an incorrect emulator scenario, and a red mark not being counted on the build containing the fix. These five defects were deemed the most significant and are attributed to the acceptance agent's own mistakes.

Overall, the story highlights the importance of thorough integration testing and the need for teams to collaborate and address defects across various services and layers of the system.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

SLH-DSA changes signature size budgets before it changes the signature model

SLH-DSA changes signature size budgets before it changes the signature model SLH-DSA is a stateless hash-based signature scheme standardized in FIPS 205.

  • SLH-DSA simplifies backup/replication by eliminating signing counter
  • Six parameter sets available, split between small/fast variants
  • Smallest signatures: 7,856 bytes at security level 1

I measured DigImg vs TinyPNG vs ShortPixel on the same images (bytes + SSIM)

A smaller image file is useful. A smaller file that visibly damages a logo, screenshot, or photo is not always a win. So instead of comparing marketing claims, I ran the same four source images…

  • DigImg produced smallest file for photographic images but lowest SSIM score
  • Transparent logos tied between TinyPNG, DigImg, and ShortPixel

What Namespace runners are, and how unit minutes work

Namespace runners are GitHub Actions runners sold by the compute unit rather than the wall-clock minute, where one unit is 1 vCPU plus 2 GB of RAM for a minute, multiplied by 1 on Linux, 2 on Windows…

  • Namespace runners offer unique compute units instead of wall-clock minutes on GitHub Actions
  • Unit equals 1 vCPU + 2 GB RAM per minute, with platform multipliers (1 Linux, 2 Windows, 10 macOS)
  • Team plan includes 100,000 unit minutes, determining wall-clock minutes based on selected machine

A Free Claude Code Skill That Reads Any Site's SEO Playbook

One page template on Wise ranks for 151,315 organic searches. Not a blog post. Not a landing page. One template, filled thousands of times with currency pairs and country codes, pulling in six figures…

  • Claude Code skill reads any site's SEO playbook for keyword, ranking, and backlink data
  • Skill costs 250 to 300 credits, runs 12 OpenSEO calls
  • Only 42 GitHub stars and 259 installs, indicating setup gap

GitHub Actions Required property is missing: jobs

Required property is missing: jobs is the workflow parser telling you that the root of the file has no jobs key where it expects one.

  • Missing "jobs" key at root of YAML file
  • Workflow parser flags invalid-file annotation
  • Fix by ensuring "jobs", "name", and "on" keys at same level

More from Sunday 15 November →