mirror of
https://github.com/openglow-org/forgefirm.git
synced 2026-09-27 08:41:13 -07:00
ScottW514
d530f773e2
The pulse header's envelope now reaches the cooling engine: the cloud client (python3-gfhardware c34faa1) derives the coolant window and the fans' minimum speeds from the header and rides them on every report, and the engine (forgectrl 57f6064) resolves each as the stricter of its setting and the job's, never looser and never overruling an off gate. cloud.pause-resume, which runs a real print, now also reads the client's "job limits from the header:" line and the engine's "effective limits:" line from the two logs; two host cases cover the failure paths. The needle guard lists the engine's phrases as not the app's. COOLING.md section 2 explains what a cloud job brings with it; BRINGUP item 19 records the pass-through as landed. Pins: forgectrl 57f6064, forgefirm-app c34faa1 (0.1.14+git); fetch-verified.
13 lines
660 B
PHP
13 lines
660 B
PHP
# forgefirm-app pin (python3-gfhardware repository, forgefirm-app/ tree).
|
|
# Bump deliberately (AUTOREV is not reproducible); keep only SRCREV and PV
|
|
# here - the image manifest leaves *-pin.inc out of the layer content hash
|
|
# because the component entry already identifies the pinned source
|
|
# (forgefirm-image-manifest.bbclass). The python3-gfhardware recipe in
|
|
# meta-glowforge-bsp pins the same repository; move both together.
|
|
SRCREV = "c34faa1402d09c888ab8f7eccdf26dd8ec4be405"
|
|
|
|
# Bump PV with every SRCREV move: the hash-derived package version is not
|
|
# monotonic on its own and buildhistory QA fails the build when it sorts
|
|
# backwards.
|
|
PV = "0.1.14+git"
|