You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 21, 2024. It is now read-only.
All of the infrastructure is in place for kubectl logs. We just need a way to hook output_writer into the wasm3 runtime such that the output of the function call will be written to disk. Right now the output is only written to standard output.
@bacongobbler could you please elaborate on those questions:
Now the bigger question is, how this redirection should be implemented API-wise?
Would the Wasm3 library user need to register read/write callbacks?
Should they handle the iovec logic on their side, or should it be abstracted away?
We're considering to add ability to redirect IO, but would better understand the level of flexibility needed.
All of the infrastructure is in place for
kubectl logs
. We just need a way to hookoutput_writer
into the wasm3 runtime such that the output of the function call will be written to disk. Right now the output is only written to standard output.krustlet-wasm3/src/provider/runtime.rs
Line 94 in 48f3cc1
The text was updated successfully, but these errors were encountered: