Repository navigation
fix: require re-entry-capable Wago and remove stale xfail - #27
Merged
Merged
Conversation
Jairus (JairusSW)
changed the title
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.
The shared-everything dynamic-linking re-entry case is supported by current Wago releases, but this module still depended on an older pre-release where the call hangs. Local workspace tests used the current Wago checkout and exposed a second problem: the old xfail made the passing case fail as an "unexpected conformance pass."
This updates the Wago dependency to
v0.1.0-beta.11, removes the stale xfail, and adds a decoder fuzz target seeded with empty, preamble-only, and real component binaries.Validation:
go test ./...andgo test -race ./...on Darwin/arm64go test ./...andgo test -race ./...on Linux/amd64go vet ./...