cvcpkg(libcvc): wasm republish — .cvcnav v2 host + CVC_STATE_EXEC=ON + guard gRPC deps off wasm (rev 2→3) - #438
Merged
Conversation
…uard gRPC deps off wasm (rev 2->3) Coordinated wasm-mt republish so the catalog carries the coef_mlp .cvcnav format v2 (two-head sigmoid, #436), and to fix two wasm defects: - CVC_STATE_EXEC was wrongly forced OFF in the wasm build; the state_exec evaluator has no gRPC dependency and must always build. Turned ON. - the gRPC/xmlrpc transport deps (openssl/c-ares/re2/abseil/protobuf/grpc) were declared for ALL platforms incl wasm, but wasm builds without that transport and they are not published for wasm -> 'cvcpkg install cvc/libcvc --platform wasm-mt' could not resolve. Guarded to the native build matrix (linux/macos/windows). cvc_revision 2->3 so publish-cvcgl-wasm produces a fresh 3.4.0+cvc.3.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Coordinated wasm-mt republish of
cvc/libcvcat 3.4.0+cvc.3, carrying three things:.cvcnavformat v2 (two-head sigmoid λ_soft/λ_hard, nav: two-head sigmoid (λ_soft, λ_hard) — .cvcnav format v2 #436) into the wasm-mt host.CVC_STATE_EXEC=ONfor wasm — it was wrongly forcedOFFin the wasm build since the wasm publish workflow was created (ci: publish libcvc/cvcgl for wasm-mt #371). The state_exec DSL evaluator/scheduler is pure C++20 and has no gRPC dependency (that'sCVC_ENABLE_GRPC/CVC_USING_XMLRPC); it must always build. Directive: CVC_STATE_EXEC must always be on.openssl/c-ares/re2/abseil/protobuf/grpcwere declared for all platforms, but the wasm build links none of them (xmlrpc/grpc off) and they aren't published for wasm, socvcpkg install cvc/libcvc --platform wasm-mtfailed to resolve (no candidate for 'abseil'). Scoped to the native build matrix (linux/macos/windows).Why now
The cvcdbg wasm gallery deploy (cyberpcangel.com/cvcdbg) has been failing since the gRPC stack landed (~Sep 2-4) because of (3); and the demo3 two-head policy needs (1)+(2). This unblocks the demo3 deploy and the two-head retrain.
Rollout note
A v2
.cvcnavhard-fails on a pre-v2 host, so this republish (the v2-capable host) must land before any v2 blob ships. Sequence: merge → publish-cvcgl-wasm (dry_run compile-check first, then publish 3.4.0+cvc.3) → cvcdbg nightly rebuilds demo3 against it → then the two-head retrain + weights republish.Recipe-only + workflow-flag change; the
recipes match CMakeLists versioncheck is unaffected (upstream_version 3.4.0 unchanged; only cvc_revision bumps).