ic-metrics
Allocation-free saturating measurement arithmetic for Internet Computer crates.
The dependency-free no_std library exports record_sample for consumer-owned
count/total fields and MeasurementSummary for samples, total, latest and maximum.
Zero is a valid observation; an empty summary has no latest or maximum value.
Count and total saturate independently. Consumers establish units, identity and
reset boundaries before comparing observations; saturated totals cannot supply
exact interval arithmetic.
use MeasurementSummary;
let mut summary = EMPTY;
assert_eq!;
summary.record;
assert_eq!;
assert_eq!;
IcyDB, Canic and ic-timers integrate this arithmetic. Their inclusive or exclusive attribution, registries, callback roles, replication, persistence and reporting remain local. IC counter reads also remain consumer-owned. The extraction contract records scope and evidence.
Development
Install rustup, Git, GNU Make, Bash 3.2 or newer and a SHA-256 utility. The pinned
toolchain is Rust 1.99.0 and the MSRV is 1.88.0. Install wasm32-unknown-unknown
for Wasm checks. make help lists focused commands; select named tests during
implementation. Full make ci requires an explicit request outside configured CI.
Install the pinned manifest formatter during developer setup:
make fmt sorts every workspace manifest before Rust formatting. make fmt-check
checks both without changing files; CI installs the same pinned formatter.
Run make install-hooks once per clone and after updating shared tooling. The
repository-local pre-commit hook formats the staged snapshot, refreshes selected
files, rejects partial staging and preserves unrelated working edits. It refuses
to replace existing hook installations. make hook-check exercises these
contracts in scratch repositories without creating commits.
See agent rules, host support and the current handoff. Reviewed shared tooling is vendored; normal checks and release scripts need no Shared Tooling sibling checkout.
Releases and adoption
The public repository is dragginzgame/ic-metrics.
The changelog
preserves the initial 0.1.0 scaffold, the 0.1.1 arithmetic release and later
tooling releases. ic-metrics 0.1.3
is published on crates.io and matches tag v0.1.3. Declare it in the consumer's
root dependency catalog:
[]
= "0.1.3"
Members inherit with ic-metrics = { workspace = true }. Published consumers
must resolve the registry package rather than require a sibling checkout.
The adoption issue
links each consumer's integration evidence. Native qualification is recorded
against its actual revision in
the host record.
Maintainer-owned make release-patch, release-minor and release-major use the
same reviewed workflow,
with RELEASE_REMOTE=origin and
RELEASE_BRANCH=main. They require cargo-edit (cargo set-version) and
cargo-sort 2.1.4, run the complete offline gate, prepare only Cargo metadata
and release notes, commit,
tag and atomically push. They do not publish the crate. Rerun the same release
target after interruption to reconcile the saved candidate without another bump.
make release-resume VERSION=X.Y.Z remains available for explicit selection;
identity, payload and destination conflicts stop recovery.
For a subsequent committed package release, the maintainer can run:
publish-check delegates to Cargo's dry run. publish uploads only ic-metrics to
crates.io, using the existing package version, locked dependencies and normal
Cargo credential setup (cargo login --registry crates-io). Both retain Cargo's
package verification and dirty-tree rejection. Publication creates no Git commit
or tag, does not bump versions and preserves build artifacts.
See Cargo's publication documentation.
cargo package -p ic-metrics --locked --offline --allow-dirty prepares and verifies
a local development archive without uploading it. The package includes the
canonical MIT license text, source and this README; documentation links resolve
to the public repository. The manifest restricts publication to crates.io.