Skip to content

test(jco): share the TLS provider's shim instance - #2343

Closed
vados-cosmonic wants to merge 1 commit into
mainfrom
fix/tls-test-shim-identity
Closed

vados-cosmonic wants to merge 1 commit into
mainfrom
fix/tls-test-shim-identity

Conversation

@vados-cosmonic

Copy link
Copy Markdown
Collaborator

The TLS integration fixture resolved WASI sockets from jco's preview2-shim 0.31.0 while its workspace TLS provider resolved preview2-shim 0.30.0. Passing streams between these instances caused eight tests to throw Cannot read private member #id from an object whose class did not declare it, including seven tests using local servers.

Resolve all fixture shim imports relative to the TLS provider so sockets, streams, and TLS share the same resource classes and IO worker even when the workspace packages use different shim versions.

Validation:

  • pnpm --filter @bytecodealliance/jco test test/node/https-wasi-tls.ts — all 12 tests passed.
  • Formatting, lint, and git diff --check passed.

@vados-cosmonic

Copy link
Copy Markdown
Collaborator Author

Going to leave this, because it's inadvertently a good way to test mismatches between jco and jco-std at release time.

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