events: core.lease drops a module's retry: false from read/apply refusals
#206
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Found by the module-rust phase 12 walk. Recorded in
docs/modules/rust/PLAN.md§27.6.core.lease'sperform(server/src/config/coreEventActions.js, around thelease.read(...)andlease.apply(...)calls) rebuilds both failure envelopes as{ ok: false, error }. Neither copies the module'sretry, so the dispatcher's default makes themretry: true.A permanent refusal from the module, such as module-rust's
events-disabled("turn EventsEnabled on") or an unresolved target, is therefore retried three times before the step fails. The Carbon walk's step 27 did exactly this. It is harmless, but it is noise, and it meansretry: falsein a lease callable is unreachable. That contradicts MODULE_API §1.1's rule that a module opts out of retry.Suggested fix: pass
retry: baseline.retry === false ? false : undefined(and the same forapplied) through on both returns.