At this moment relu_layer op doesn't allow threshold configuration, and legacy RELU op allows that.
We should add configuration option to relu_layer.

We use sbt-dynver to set the version for the Play project based on git tags.
E.g. when you run sbt in the Play project folder you will see:

// If you haven't you need to get the Play framework source code
git clone git@github.com:playframework/playframework.git
cd ./playframework

// You are in the master branch now, from which we want to rele

The colors given in ui/analyse/src/autoShape.ts by brollin are as follows:

• !? Interesting: #ea45d8
• ! Good: #22ac38
• !! Brilliant: #168226

Convert these to HSL format and define them as sass variables alongside the error ones ($c-blunder, etc) in ui/common/css/theme/_default.scss. Check them with light theme, if they lack sufficient contrast move the previous color defs t

Let's support at least reading "b3" header from a single string, most commonly traceid-spanid-1
It would also be nice to support optionally writing this, especially in message providers or others with constrained environments.

Expected behavior

As discussed on openzipkin/b3-propagation#21 and first implemented here: https://github.com/openzipkin/brave/blob/master/brave/src/main/java/bra

Not that complicated to implement:

• introduce in SslClientContext the same kind of changes as in SslServerContext so it's no longer

https://github.com/lampepfl/dotty/blob/main/scaladoc/src/dotty/tools/scaladoc/site/SidebarParser.scala
contains only general info about the file format and returns a general error for all problems. The idea is to improve the error handling so that user can see an erroneous line or which information is missing.

I just came across the fact that a Show[Throwable] exists.

1. It is not wired up into import Scalaz._, one needs to import scalaz.std.java.throwable._
2. It discards the stack trace entirely.

What's going on with this? :D
Is it OK if I fix both of these (for 7.2 and 7.3)?

steps

I have reproduced the bug with both sbt 1.6.2 and 1.6.0, but no problem with sbt 1.5.8.

To reproduce, just take any SBT project using SBT 1.6 and try to compile with Scala 2.12.4, eg.

sbt new scala/scala-seed.g8
# cd into directory and change Scala version to 2.12.4
sbt compile

Note that the issue does not show up with Scala versions 2.12.2, 2.12.3, nor 2.12.5.

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

The code in question should be here.
https://github.com/scala-native/scala-native/blob/63d07093f6d0a6e9de28cd8f9fb6bc1d6596c6ec/test-interface/src/main/scala/scala/scalanative/testinterface/signalhandling/SignalConfig.scala#L45-L71

Potential idea for a fix.
https://stackoverflow.com/questions/16509614/signal-number-to-name

Problem:

The current log will output something like val_function_0 while it should be val_mean_squared_error_0.

Solution:

"val/{}_{}".format(type(metric).__name__, i) use the name of the type of metric (metric is an instance of torchmetrics.metric.Metric so the type of it is function), that's why the output looks like val_function_0. It should use the name of the metri