Transaction-Science/open-standards
Watch
1
0
Fork
You've already forked open-standards
 0
Code Issues Pull requests Projects Releases 15 Packages Wiki Activity Actions 130
open-standards/eoc/eoc-rs/crates
History
Exact
Repository files (latest commit first)
Filename Latest commit message Latest commit date
Transaction Science 208ffd374f
Some checks failed
energy meters on real hardware / sink decode table · per-task energy and the GPU rail on macOS (push) Successful in 5m13s
Details
repository checks / lockfiles, advisories, tests in CI, workflow hygiene, spec and section references, public text (push) Has been cancelled
Details
energy meters on real hardware / RAPL and NVML on jetson-hub (push) Failing after 2m37s
Details
jouleclaw public surface must stay documented / Public-surface audit (jouleclaw-rs) (push) Failing after 15m17s
Details
energy meters on real hardware / sink decode table · RAPL on jetson-hub (NVML surveyed) (push) Failing after 20s
Details
The public IOReport status variants say what they mean under the 3-tick cap 
The docs of each crate's IoReportStatus still stated the liveness rule as it stood
before the cap: five advances, four in five of the intervals observed, 300 ms of
wall time. Live, and Frozen where it states the rule, now say it as the spec texts
do: what an interval is, that only one no longer than three of the probe's ticks
(75 ms at its 25 ms tick) counts, that a longer one counts as nothing, and that the
300 ms is the summed length of the intervals that count. Frozen also says that a
probe the host held, so that too few of its intervals counted, reads Frozen. In
eoc-meter, jcp-energy, jouleclaw-energy, proof-cascade and sandbox-meter. Doc
comments only.

Changelog: none
Co-Authored-By: Claude Opus 5.5 <[email protected]>
2026-11-07 08:30:52 -05:00
..
eoc Cargo: no minimum-supported-version floor, because the policy is latest stable 2026-11-03 17:42:20 -05:00
eoc-agent Cargo: no minimum-supported-version floor, because the policy is latest stable 2026-11-03 17:42:20 -05:00
eoc-cache Cargo: no minimum-supported-version floor, because the policy is latest stable 2026-11-03 17:42:20 -05:00
eoc-carbon Cargo: no minimum-supported-version floor, because the policy is latest stable 2026-11-03 17:42:20 -05:00
eoc-cascade Cargo: no minimum-supported-version floor, because the policy is latest stable 2026-11-03 17:42:20 -05:00
eoc-core Cargo: no minimum-supported-version floor, because the policy is latest stable 2026-11-03 17:42:20 -05:00
eoc-distributed Cargo: no minimum-supported-version floor, because the policy is latest stable 2026-11-03 17:42:20 -05:00
eoc-embeddings Cargo: no minimum-supported-version floor, because the policy is latest stable 2026-11-03 17:42:20 -05:00
eoc-eval Cargo: no minimum-supported-version floor, because the policy is latest stable 2026-11-03 17:42:20 -05:00
eoc-graph Cargo: no minimum-supported-version floor, because the policy is latest stable 2026-11-03 17:42:20 -05:00
eoc-kv Cargo: no minimum-supported-version floor, because the policy is latest stable 2026-11-03 17:42:20 -05:00
eoc-local Cargo: no minimum-supported-version floor, because the policy is latest stable 2026-11-03 17:42:20 -05:00
eoc-memory Cargo: no minimum-supported-version floor, because the policy is latest stable 2026-11-03 17:42:20 -05:00
eoc-meter The public IOReport status variants say what they mean under the 3-tick cap 2026-11-07 08:30:52 -05:00
eoc-multimodal Cargo: no minimum-supported-version floor, because the policy is latest stable 2026-11-03 17:42:20 -05:00
eoc-neural Cargo: no minimum-supported-version floor, because the policy is latest stable 2026-11-03 17:42:20 -05:00
eoc-observability Cargo: no minimum-supported-version floor, because the policy is latest stable 2026-11-03 17:42:20 -05:00
eoc-quantize Cargo: no minimum-supported-version floor, because the policy is latest stable 2026-11-03 17:42:20 -05:00
eoc-rag Cargo: no minimum-supported-version floor, because the policy is latest stable 2026-11-03 17:42:20 -05:00
eoc-rerank Cargo: no minimum-supported-version floor, because the policy is latest stable 2026-11-03 17:42:20 -05:00
eoc-route-learned Cargo: no minimum-supported-version floor, because the policy is latest stable 2026-11-03 17:42:20 -05:00
eoc-safety Cargo: no minimum-supported-version floor, because the policy is latest stable 2026-11-03 17:42:20 -05:00
eoc-spec-decode Cargo: no minimum-supported-version floor, because the policy is latest stable 2026-11-03 17:42:20 -05:00
eoc-streaming Cargo: no minimum-supported-version floor, because the policy is latest stable 2026-11-03 17:42:20 -05:00
eoc-tools Cargo: no minimum-supported-version floor, because the policy is latest stable 2026-11-03 17:42:20 -05:00
eoc-vendor-api Cargo: no minimum-supported-version floor, because the policy is latest stable 2026-11-03 17:42:20 -05:00
eoc-wasm Cargo: no minimum-supported-version floor, because the policy is latest stable 2026-11-03 17:42:20 -05:00