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.

Are you looking for help?

No.

Play Version

2.6 to 2.8

API

Java / Scala

Expected Behavior

The instructions at https://www.playframework.com/documentation/2.8.x/Deploying-CloudFoundry work.

As it stands (see https://stackoverflow.com/a/62506207/4432837 and cloudfoundry/java-test-applications#20) those instructions are no longer applic

e.g. in https://lichess.org/study/HBTNQi9H/3ttnXzfm#11, Stockfish fails to load this absurd board, following an illegal king capture.
(NNUE in this screenshot, but I did see the same thing with HCE.)

Stockfish does fail loudly, as I indicated: the UI might be able to notice this and emit some error.
![image](https://user-images.githubusercontent.com/5666174/117732143-31038800-b1a4-11eb-9997-b

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

It would be nice to pass multiple actions to a checkIf method , the same way as a check allows through the comma.

So, for example, instead of writing this:

.check(
   checkIf("${first.exists()}")(do_first),
   checkIf("$first.exists()}")(do_second), 
   checkIf("${first.exists()}")do_third)

it would be nice to have API as follows:

check(checkIf("${first.exists()}")(do

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)?

Minimized code

/** @define macro Super */
abstract class Super {
  /** $macro */
  def inherited: Int = 5
  /** $macro */
  def implemented: Unit
  /** $macro */
  def overridden: String = "test"
}
/**
 * @define name default
 * @define dummy dummy
 */
trait A[T] {
  /** List $name */
  def list(): List[T]
  /** Gets the $name with the given $dummy */
  def get(id:

steps

I am using sbt 1.5.1 (with Coursier disabled) and I'm importing multiple libraries, e.g. a and b

a has a transitive dependency to c, version 1.1-prerelease
b has a transitive dependency to c, version 1.0

I am using early-semver as the version scheme.

problem

I'm getting an error when building that there are version conflicts that are suspected to be binary incompatible.

Adding a plain text to the header of a compiled and optimized .js-file may be useful for multiple reasons:

• Adding metadata like version, compiler settings, date, ...
• Adding execution information, e.g. #!/usr/bin/env node
• Adding a License, Author, Support info, URL, ...

Such a plain text header could easily be added to a .js in a postprocessing step after compilation. Howeve

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