Skip to content

fix: restore main build β€” multi-source []string in protocol verify test#50

Merged
markmals merged 1 commit into
mainfrom
fix/protocol-multisource-source
Jun 16, 2026
Merged

fix: restore main build β€” multi-source []string in protocol verify test#50
markmals merged 1 commit into
mainfrom
fix/protocol-multisource-source

Conversation

@markmals

Copy link
Copy Markdown
Owner

Incident: main is red

PR #49 was authored against a stale local main and auto-merged before the build matrix finished. Current main had already refactored VerifyConfig.Source from string β†’ []string (multi-source, #48 line). The protocol regression test merged with Source: "go", which no longer type-checks against []string β€” so go vet / go test fail to compile internal/engine on main:

vet: internal/engine/verify_run_test.go:189:81: cannot use "go" (untyped string constant) as []string value in struct literal

Fix

One line: Source: "go" β†’ Source: []string{"go"}, matching every other test in the file. No behavior change β€” TestVerifyProtocolScenarioJoins still asserts the protocol scenario joins (no Dangling), passes, and locks. The CarriesScenarios() = !k.Singular() fix from #49 is already on main and unaffected.

Verification

mise run ci green against the merged main (fmt, build, vet, go test ./... β€” fresh, uncached). Protocol regression passes against the multi-source API.

PR #49 was authored against a stale local main and merged before the
build matrix finished, breaking main: origin/main had already refactored
VerifyConfig.Source to []string (multi-source), so the protocol
regression's `Source: "go"` no longer type-checks (go vet/test fail to
compile internal/engine). Use `Source: []string{"go"}` to match the
current API. Behavior unchanged β€” TestVerifyProtocolScenarioJoins still
asserts the protocol scenario joins (no dangling), passes, and locks.
@markmals markmals merged commit 039bd91 into main Jun 16, 2026
4 checks passed
@markmals markmals deleted the fix/protocol-multisource-source branch June 16, 2026 19:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant