The docs for IPython.core.interactiveshell.InteractiveShell.set_custom_exc have horribly mangled a warning message into a list of arguments. I can't work out at a glance why this is happening; it might be a sphinx.ext.napoleon bug, or a sphi

Every kubeflow image should be scanned for security vulnerabilities.
It would be great to have a periodic security report.
Each of these images with vulnerability should be patched and updated.

Contributed recipes are not checked in CI, were mostly added a long time ago and so they might be out-of-date.
It would be nice if someone checked them, updated packages versions used there and verified that they still work.

The plotting UI leaves a lot to be desired:

• When you bring up the plotting UI, it's not obvious that you have to do some work to make a plot happen. If you don't, there's no error message, just a never-ending wait. (see https://gitter.im/polynote/polynote?at=5e0e36f9eac8d1511e9ed2ff )
• Why do we make you drag things onto axes? Especially when there is only one axis it could go onto (at leas

test filename :
julia编程.jl

error message:

Error message:

StringIndexError: invalid index [103], valid nearby indices [101]=>'程', [104]=>'.'
Stacktrace:
  [1] string_index_err(s::String, i::Int64)
    @ Base .\strings\string.jl:12
  [2] getindex
    @ .\strings\string.jl:263 [inlined]
  [3] without_pluto_file_extension(s::String)
    @ Pluto C:\Users\15320\.julia\packages\Pl

Use case

Polyaxon tracking can be used to automatically log all information generated by Ludwig.

We should probably think about adding support for Polyaxon's tracking module in Ludwig contrib.