You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
deploy-kit validate accepts a placement cpu that is not a quantity #235
deploy-kit validate accepts a Process whose placement.cpu is not a quantity:
placement:
memory: 64Micpu: lots
node src/cli/index.ts validate <file> printed accepted (1 read) and exited 0. The published project-intent.schema.json types placement.memory and placement.cpu as any non-empty string, with no quantity pattern. Observed while writing JorisJonkers-dev/delivery's project file, on branch feat/197-compose-cli.
What to find out
Whether a malformed memory or cpu is meant to be refused at validate time and, if not, where it is refused. Placement eligibility (E_PLACEMENT_UNSATISFIABLE, chapter 40) compares these quantities against the node contract, so an unparseable value has to fail somewhere. If nothing refuses it before render, decide the refusal code, and say in spec/v1 chapter 10 where it applies.
Acceptance criteria
A Process with an unparseable memory or cpu is refused with a named E_ code, at the step the spec names.
A negative fixture proves it, in both implementations where the parity table binds.
Activity
ExtraToast commentedon Oct 9, 2026
Kept by Decide the fate of the open work that predates the map. TypeScript only, after
emf/is deleted (#99); blocked until then so no parity cost is paid before 30 October.