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

E_NO_STALE_SECRET

A named refusal, raised in 2 places in weft. What it refused, the sentence it prints, and the argument for it.

named refusal weft packages/weft/src/stale.ts·2 places
'…' has no staleSecret in weft.config.ts, so nothing may tell this deployment that it is stale

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/composition.md
Introduced by
A region that lives somewhere else

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_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_CSP_CONFLICT… is declared as 'none' and as …plan
E_NO_LOCAL_REGIONthe registry resolves it to this process and this process renders no such region. A monolith is a topology, not an absence of onekernel
E_NO_REGION_REGISTRYno registry able to resolve a region is bound. A shell composing regions needs one, and a table compiled into the shell would make a roll a redeploykernel
E_NO_SUCH_REGION'…' is served by region '…' and this deployment's registry resolves none by that namekernel