vh/forgefirm
1
0
Fork 0
mirror of https://github.com/openglow-org/forgefirm.git synced 2026-09-28 01:01:12 -07:00
Code Issues Packages Projects Releases Wiki Activity

Name the verdict, not the report, in the stale-verdict rule

Browse Source 
The section describes two channels flowing opposite ways - the
controller's job-state reports and the engine's verdict - so "the report"
pointed at the wrong one directly under a lead that names the verdict.
This commit is contained in:
ScottW514
2026-08-18 07:43:16 -04:00
parent 7012c7d1b2
commit 5a587c3536
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/COOLING.md
+1 -1
View File
@@ -59,7 +59,7 @@ is running — GRBL or cloud — is a client of it, over two channels:
Two properties of that split are worth understanding, because they explain the Two properties of that split are worth understanding, because they explain the
machine's behavior in odd situations: machine's behavior in odd situations:
**A missing verdict is a bad verdict.** If the report is absent or more than two **A missing verdict is a bad verdict.** If the verdict is absent or more than two
seconds old, a controller treats it as *fire blocked, hold*. The engine going seconds old, a controller treats it as *fire blocked, hold*. The engine going
away looks exactly like a fault, never like permission. away looks exactly like a fault, never like permission.