zara-github: fail malformed numeric config with GitHubConfigError #105

New issue

Closed

opened 2026-09-08 02:02:59 +00:00 by nsaspy · 0 comments

nsaspy commented

2026-09-08 02:02:59 +00:00

Owner

Problem

GitHubConfig.load() rejects boolean numeric settings, but otherwise calls float()/int() directly. Malformed values such as None, objects, or non-numeric strings can leak incidental TypeError/ValueError instead of the provider's structured GitHubConfigError boundary.

Slice

deterministic RED coverage for malformed timeout/result/response numeric configuration;
reject invalid numeric descriptors with GitHubConfigError before provider construction/network access;
preserve valid numeric-string configuration and existing bounds;
exact-head compatibility, registry, plugin and generated Nix package gates before merge.

Dependency-ready zara-github correctness slice. No external todo work.

## Problem `GitHubConfig.load()` rejects boolean numeric settings, but otherwise calls `float()`/`int()` directly. Malformed values such as `None`, objects, or non-numeric strings can leak incidental `TypeError`/`ValueError` instead of the provider's structured `GitHubConfigError` boundary. ## Slice - deterministic RED coverage for malformed timeout/result/response numeric configuration; - reject invalid numeric descriptors with `GitHubConfigError` before provider construction/network access; - preserve valid numeric-string configuration and existing bounds; - exact-head compatibility, registry, plugin and generated Nix package gates before merge. Dependency-ready `zara-github` correctness slice. No external todo work.

nsaspy closed this issue

2026-09-08 02:02:59 +00:00

nsaspy referenced this issue

2026-09-08 02:20:01 +00:00

zara-coding: expose pure repository SPEC verification #458