notebook

Python 3.10 added suggestions for AttributeError and NameError in the error messages. It seems the suggestions are not stored in the exception object but calculated when Error is displayed. There is a note that that this won't work with IPython but it will be good to see if it's feasible. Opening an issue for discussion.

https://bugs.python.org/issue38530
https://docs.python.org/3/whatsnew/3.

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 feature

Why you need this feature:

Sub-issue of kubeflow/kubeflow#6353

To have support for K8s 1.22 we need to ensure all our crud web apps, Jupyter, TensorBoards, Volumes, are using the v1 version of SubjectAccessReviews. https://kubernetes.io/docs/reference/using-api/deprec

Now that #3490 has been merged, we should add more prometheus metrics to the notebook server!

Some ideas for metrics to add...

1. Number of kernels running (labeled by type)
2. Number of sessions open (not sure if this is useful?)
3. Number of terminals open
4. Mirror of the activity tracking metrics
5. Kernel start / stop latency metric

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 have a couple of combinations of let and global that are not analyzed correctly, like:

let
	a = 1
	global a = 2
end

defines a global a, but Pluto prioritizes the let block.

@test_broken means that we still need to fix it:

https://github.com/fonsp/Pluto.jl/blob/c1d23122845e7864ef3dfe15a8428366c98f95eb/test/ExpressionExplorer.jl#L368-L379

This is a good firs

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.