stable
Clone or download
Part of story #35093 execute custom code as artifact post action If your WASM module returns a wrong formatted output, the error displayed in logs just tell that something is wrong. By adding the explicit mapping error you can know what is error *Testing:* In example module, you can add at the start of main function: println!("{}", json!({"wrong": "tag"})); return Ok(()); Build the module with: cargo build --target wasm32-wasi --release And then upload it for your Tracker, after an execution logs should show an error entry with an error message: An invalid response has been received from the artifact post action WASM module Could not map type `Tuleap\TrackerCCE\WASM\WASMResponseRepresentation` With some details after. Change-Id: I192e48f99274ed23d8862d22e7f424aeb77ed563
Modified Files
| Name | ||||
|---|---|---|---|---|
| M | plugins/tracker_cce/include/TrackerCCE/WASM/ProcessWASMResponse.php | +1 | −1 | Go to diff View file |