feat(errors): name a deadline's parameter or environment control in details.limit (#11172)

This commit is contained in:
morluto authored and GitHub committed 2026-11-15 21:49:35 +08:00
1 parent 2d4a97b405
commit 863d82e370
16 files changed
+159 -50

No files matched your search

+11
View File
@@ -291,6 +291,17 @@ Error copying, attribution, redaction, and delivery must preserve these facts.
Human-readable remediation explains the same failure; clients should not need
to parse that sentence to identify an editable setting.
A deadline controlled by something other than a registered setting reports
`details.limit` with `control_kind` instead of `setting`.
`control_kind: "parameter"` names the per-call `parameter` and its `cli_flag`
(`native_command_timeout_ms`, `native_ui_deadline_ms`,
`pwntools_timeout_ms`) and applies on the next call.
`control_kind: "environment"` names the `environment` variable REA reads when
it starts (`REA_SWIFTC_COMPILE_TIMEOUT_MS`): `applies_at` is `next_startup`,
or `next_invocation` for a one-shot invocation. Both carry `effective_value`,
`unit`, `minimum`, `maximum` and `default_value`. `update_analysis_settings`
changes neither. A limit without `control_kind` is a registered setting.
This output is breaking. Results and errors no longer carry the previous
restart boolean or a single effect field, and there is no compatibility alias.
Read `update_mode` to see whether the setter can change the active value, and