Repository navigation
Billing: Add compute_duration_ms to ExecutionResult - #473
Conversation
|
👋 DylanTinianov, thanks for creating this pull request! To help reviewers, please consider creating future PRs as drafts first. This allows you to self-review and make any final changes before notifying the team. Once you're ready, you can mark it as "Ready for review" to request feedback. Thanks! |
|
|
The latest Buf updates on your PR. Results from workflow Regenerate Protobuf Files / buf (pull_request).
|
The module that executes a workflow reports the run's wall-clock duration on the result it returns: the WASM host times the guest run, and the confidential module carries over the enclave-reported duration. The workflow engine meters whatever is reported as cre:workflow:compute, so it no longer needs to know which module executed, or time the run itself. Presence distinguishes an unavailable measurement from a measured zero. Regenerated sdk.pb.go and the embedded proto sources with the pinned generator versions (protoc 29.3, protoc-gen-go 1.36.6). Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
7a0298a to
5f08266
Compare
Same change as the
capabilities-developmentPR (see the companioncre/sdk: add compute_duration_ms to ExecutionResult), targetingmainso downstream modules can pin a commit that also includes #469. Branch protection will go green once the capdev PR merges (patch-id match, or the proto-subset fallback).What
Adds
optional int64 compute_duration_ms = 5tosdk.v1alpha.ExecutionResult, plus the regeneratedcre/go/sdk/sdk.pb.goand embedded proto sources.Why
Compute metering (CRE-6779) needs one duration per execution that is right for both ordinary and confidential runs. The module that executes the workflow sets it on the result it already returns: the WASM host times the guest run; the confidential module carries over the enclave-reported
execution_duration_ms(#469). The engine meters what is reported and no longer needs to know which module ran, or to time the run itself.Consumers