ALGO STDOUT-STDERR

[SammyOina]

What type of PR is this?

What does this do?

Which issue(s) does this PR fix/relate to?

• Related Issue #
• Resolves #

Have you included tests for your changes?

Did you document any new/modified feature?

Notes

[dborovcanin]

Let's evaluate this approach:

• simplifies the flow since we rely on "standard" std{in, our, err} approach
• enables unified approach across different runners: binary, Docker, WASM runtime
• less invasive on algorithm - we do not expect algo to be written in such a way that socket is open for streaming process info

However, there are some drawbacks to this approach:

• limited output to a single stream (err for logs and out for result) provides less insight into the algorithm execution
• it still requires code to be written in a certain way, i.e. to redirect all logs to stdout rather than a file

Having this in mind, it's worth exploring if there is a way to "fake" the filesystem for those algorithms that require files for logging. @SammyOina Can you check it? Also, try and test how this approach works with Docker.

[dborovcanin]

Finally, I think it would be an acceptable requirement (though definitely not ideal, ofc) for the algo provider to write all the logs to the stderr, since we do not support a file system.

[dborovcanin]

We will keep the file approach, so this PR can be closed. We will return to it once we have a working and fully functional demo with files.