Does Livebook have a way to create a runtime log file? I’m thinking of a flow where a job evaluates a livebook file in ‘background’ mode with no eyes on it. Lets say a specific livebook runtime encounters some errors and now I would like to see them.
Thinking out loud; I suppose the wrapper job could fetch the livebook code, evaluate, then send any errors to a normal log file. It would be really nice though to see all the errors in line with code cells in the livebook markdown. A livebook log file of some sort would be really cool. Open it like any other livebook file and it displays all the rendered output of a previous runtime.
This is in line with this idea but not sure what came of it.
