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
Possibly slightly peripheral to the main issues of Mesos bindings, but when writing schedulers a standard pattern would certainly be to interact with the sandbox and stdout/stderr files in particular?
It would be helpful if there was an idiomatic interface in the bindings for doing this - the HTTP only focus of the next branch might work in this capacity?
The text was updated successfully, but these errors were encountered:
Thanks for bringing this up! It's possible. I briefly considered prototyping support for the other (non-v1) endpoints. Needs more thought. And it's a lower priority than making the v1 scheduler/executor API usable.
Possibly slightly peripheral to the main issues of Mesos bindings, but when writing schedulers a standard pattern would certainly be to interact with the sandbox and stdout/stderr files in particular?
It would be helpful if there was an idiomatic interface in the bindings for doing this - the HTTP only focus of the
next
branch might work in this capacity?The text was updated successfully, but these errors were encountered: