weft
ir 2.6.0 · warp 1.8.0
generatedextracted from the source that raises it

E_UNKNOWN_FLAG

A named refusal, raised in one place in adapters. What it refused, the sentence it prints, and the argument for it.

named refusal adapters packages/adapters/src/flags.ts
… has no declared axis, so its variants cannot be enumerated

The message as the source writes it, with interpolations shown as an ellipsis. It is a reconstruction of the template, not a capture of a runtime string.

Specified in
spec/kernel/ports.md
Introduced by
Ports, config, and the build

Raised in the same package, or specified in the same document. A refusal rarely stands on its own — the ones beside it are usually the same rule seen from another angle:

CodeWhat it saysRaised in
E_CONSISTENCY_MISMATCHdeclares strong consistency against '…', which is eventualplan
E_CPU_BUDGETgave up waiting after …ms. The render may still be running on the other side, because a … can be abandoned and not killedadapters
E_FLAG_OFF_AXIS… resolved to …, which is not one of its declared values (…)adapters
E_NO_ATOMIC_LEASEan edge key-value store has no atomic compare-and-set, so a lease taken here would be a stampede guard that does not guard and a replay guard that reports every nonce fresh. Bind `leases` — redisLeases, a Durable Object, an advisory lock — or do not declare anything that needs oneadapters
E_NO_RATE_LIMIT… declare a limit and no limits port is bound, so every call is E_NO_RATE_LIMIT. Bind weft.config.ts's \`limits\` — countingLimits({ store, counted }) in @weftjs/adapters, where \`counted\` is the decision a kernel cannot make for youkernel