Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ensures response is handled with the same guest as the request #69

Merged
merged 1 commit into from
May 23, 2023

Conversation

codefromthecrypt
Copy link
Contributor

Before, we had a bug where an arbitrary module was used for response processing. This defeated the goal of request context correlation. This fixes the problem by holding the guest module open until the response is complete.

Fixes #68

Before, we had a bug where an arbitrary module was used for response
processing. This defeated the goal of request context correlation. This
fixes the problem by holding the guest module open until the response
is complete.

Fixes #68

Signed-off-by: Adrian Cole <adrian@tetrate.io>
@codefromthecrypt codefromthecrypt merged commit 88a400f into main May 23, 2023
5 checks passed
@codefromthecrypt codefromthecrypt deleted the response-module branch May 23, 2023 18:19
codefromthecrypt pushed a commit to codefromthecrypt/components-contrib that referenced this pull request May 23, 2023
@Taction noticed a pretty bad bug where request correlation could be
out-of-sync. This is fixed in http-wasm v0.5.0 per http-wasm/http-wasm-host-go#69

Signed-off-by: Adrian Cole <adrian@tetrate.io>
codefromthecrypt pushed a commit to codefromthecrypt/components-contrib that referenced this pull request May 23, 2023
@Taction noticed a pretty bad bug where request correlation could be
out-of-sync. This is fixed in http-wasm v0.5.0 per http-wasm/http-wasm-host-go#69

Signed-off-by: Adrian Cole <adrian@tetrate.io>
codefromthecrypt pushed a commit to codefromthecrypt/components-contrib that referenced this pull request May 23, 2023
@Taction noticed a pretty bad bug where request correlation could be
out-of-sync. This is fixed in http-wasm v0.5.0 per http-wasm/http-wasm-host-go#69

Signed-off-by: Adrian Cole <adrian@tetrate.io>
@codefromthecrypt
Copy link
Contributor Author

forgot docs #78

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.

Using the same wasm instance for one request
1 participant