Repository navigation
build(deps): cascade Verbara.Sdk 2.7.0 and Verbara.Sdk.Pro 2.17.0-pro - #332
Conversation
DeferredPrimaryAmiConnection now forwards ReportsEventActionOutcome, the SendEventGeneratingActionAsync(action, EventActionOutcome?, ct) overload and the StateChanged event to the primary connection. Sdk 2.7.0 gave them default bodies, so the wrapper compiled clean while answering false, dropping the outcome and raising nothing. Four tests lock the forwarding; each fails when its forwarding is removed.
Verbara.Sdk.OpenTelemetry 2.7.0 raises OpenTelemetry to 1.19.1 but still pulls OpenTelemetry.Exporter.Prometheus.AspNetCore 1.15.2-beta.1, whose PrometheusSerializer calls OpenTelemetry.Internal.MathHelper, a type 1.19.1 removed. The exporter swallows the failure, so GET /metrics answered 200 with an empty body (ILC: WriteDouble "will always throw"). Pin the exporter centrally at 1.19.1-beta.1 (transitive pinning is on); the assets diff moves only that package, in Api and Api.Tests. Add a /metrics test on the Api test host that asserts a non-empty scrape with sample lines; it was red before the pin. Remove the pin when the Sdk ships the aligned exporter (cascade C16 / Verbara.Sdk 2.8.0).
H159 lab merge gate: waived, with evidence (not a pass)The H159 itself held on every call that reached the agent: 71 of 71. Each ended with the agent as conversation owner, exactly one
Why calls were not offered.
The code path is identical on both refs: Platform Recommendation, from an independent verifier who recomputed every run from the raw files: merge, recording this waiver. Evidence lives in the |
1 participant
Host leg of the cross-repo change
sdk-2-7-0-pin-cascade(verbara-meta roadmap R-021,decision_ref: Verbara.Sdk/ADR-0040). Pro shipped its leg asv2.17.0-pro(Verbara.Sdk.Pro #180).Do not merge until the H159 lab gate passes: a queued call taken by a member must end with a conversation owner, a screen-pop and the agent Busy. Evidence goes into verbara-lab and the measurement catalog.
What changes
Verbara.Sdk.*pins move from 2.4.0 to 2.7.0, and 22Verbara.Sdk.Pro.*pins move from 2.14.1-pro to 2.17.0-pro. Restore reports no NU1605 or NU1109.DeferredPrimaryAmiConnectionnow forwards the threeIAmiConnectionmembers Sdk 2.7.0 added with default bodies:ReportsEventActionOutcome, theSendEventGeneratingActionAsyncoverload withEventActionOutcome?, andStateChanged. Without forwarding, the compiler stays silent while they are dropped. The tests were written first, and removing each forwarding turns a test red./metricsfix. Sdk 2.7.0 (since 2.6.1, Sdk backlog H167) ships OpenTelemetry 1.19.1 withOpenTelemetry.Exporter.Prometheus.AspNetCore1.15.2-beta.1. That exporter calls a type removed in 1.19.1, soGET /metricsanswered 200 with 0 bytes and logged nothing. ILC warned "will always throw", which no gate reads. This PR adds a central pin of the exporter at 1.19.1-beta.1, plusPrometheusScrapingEndpointTests. That test is red without the pin and green with it. The AOT binary now serves 110 sample lines. The pin goes away with the Sdk 2.8.0 hop (C16).VoiceConversationBridge: comment only. Since Verbara.Sdk#377 the Sdk emits oneCallConnectedEventper queued call taken.[Unreleased]entry.Verification
Local run on the rebased branch:
warning ILand 0 "will always throw";An independent verifier re-ran all of it in a fresh clone and mutation-checked the forwarding and the pin. Locally,
2.17.0-procame from a pack of the identical tree, because this machine has no GitHub Packages credentials. This PR's CI restores it from the real feed.Rollback
Revert this PR. Platform goes back to Sdk 2.4.0 and Pro 2.14.1-pro. There is no schema or configuration change.
🤖 Generated with Claude Code