-
Notifications
You must be signed in to change notification settings - Fork 506
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
[Merged by Bors] - Report error to client when SPU is given invalid WASM module #1713
[Merged by Bors] - Report error to client when SPU is given invalid WASM module #1713
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. Just couple of nits
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
bors r+ |
Closes #1143. When supplying an invalid WASM module to the consumer, the client will now return with the following error: ``` $ flvd consume fruits -B --filter=Cargo.toml # note that Cargo.toml is not a valid WASM file Consuming records starting 10 from the end of topic 'fruits' Error: 0: Fluvio client error 1: SmartStream error 2: WASM Module error: failed to parse WebAssembly module ``` Action items: - [x] Implement error delivery - [x] Add integration test
Build failed: |
Oh interesting, I didn't actually know what the crate_version check did until now! Cool catch, and nice script @tjtelan! bors r+ |
Closes #1143. When supplying an invalid WASM module to the consumer, the client will now return with the following error: ``` $ flvd consume fruits -B --filter=Cargo.toml # note that Cargo.toml is not a valid WASM file Consuming records starting 10 from the end of topic 'fruits' Error: 0: Fluvio client error 1: SmartStream error 2: WASM Module error: failed to parse WebAssembly module ``` Action items: - [x] Implement error delivery - [x] Add integration test
Pull request successfully merged into master. Build succeeded: |
Closes #1143.
When supplying an invalid WASM module to the consumer, the client will now return with the following error:
Action items: