notebook

The warnings at

https://ipython.readthedocs.io/en/stable/config/extensions/autoreload.html

do not mention the issues with reloading modules with enums:

• Enum and Flag are compared by identity (is, even if == is used (similarly to None))
• reloading a module, or importing the same module by a different name, creates new enums (look the same, but are not the same)

Although the results look nice and ideal in all TensorFlow plots and are consistent across all frameworks, there is a small difference (more of a consistency issue). The result training loss/accuracy plots look like they are sampling on a lesser number of points. It looks more straight and smooth and less wiggly as compared to PyTorch or MXNet.

It can be clearly seen in chapter 6([CNN Lenet](ht

/kind bug

What steps did you take and what happened:
Right now the Notebooks controller will be appending new Pod conditions to the Notebook's status https://github.com/kubeflow/kubeflow/blob/master/components/notebook-controller/controllers/notebook_controller.go#L247.

This means that a Notebook could end up with the following conditions being present at the same time:

        {

Problem

At the moment the help plugin is all contained in a single plugin:

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.

Description
It looks the Polynote doesn't support to configure Scala REPL like other notebook product.
For example, jupyter notebook support to configure Scala REPL such as

interp.configureCompiler(_.settings.outputDirs.setSingleOutput(replClassPath))
interp.configureCompiler(_.settings.Yreplclassbased)

Some configuration is hard-coded such as settings.Ydelambdafy.value is s

We currently use some internal Pkg API to make https://github.com/fonsp/Pluto.jl/wiki/%F0%9F%8E%81-Package-management work, we we should try to avoid as much as possible. Take a look at src/packages/PkgCompat.jl to learn more, the compatibility issues are pretty well documented.

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.