fluencelabs/gitbook-docs
1
0
Fork 0
mirror of https://github.com/fluencelabs/gitbook-docs synced 2025-06-26 13:11:45 +00:00
Code Issues Projects Releases Wiki Activity

GitBook: [main] 54 pages modified

Browse Source
This commit is contained in:
boneyard93501
2021-06-11 01:48:13 +00:00
committed by gitbook-bot
parent 0e966ac367
commit 3c2360eade
4 changed files with 4 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
knowledge_knowledge/knowledge_aquamarine/marine/marine-rs-sdk.md
View File

@ -201,7 +201,7 @@ Please not that if you want to use `curl_request` with testing, see below, the c
since cargo does not have access to the magic in place in the marine rs sdk to handle unsafe.
MountedBinaryResult itself is a Marine-compatible struct containing a binary's return process code, error string, stdout and stderr:
MountedBinaryResult itself is a Marine-compatible struct containing a binary's return process code, error string and stdout and stderr as byte arrays:
```rust
#[marine]
@ -224,8 +224,6 @@ pub struct MountedBinaryResult {
MountedBinaryResult then can be used on a variety of match or conditional tests.
#### Testing
Since we are compiling to a wasm32-wasi target with `ftype` constrains, the basic `cargo test` is not all that useful or even usable for our purposes. To alleviate that limitation, Fluence has introduced the [`[marine-test]` macro ](https://github.com/fluencelabs/marine-rs-sdk/tree/master/crates/marine-test-macro)that does a lot of the heavy lifting to allow developers to use `cargo test` as intended. That is, `[marine-test]` macro generates the necessary code to call Marine, one instance per test function, based on the Wasm module and associated configuration file so that the actual test function is run against the Wasm module not the native code.