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

Hi,

Following a user asking for help on Discord, the problem he was unable to join a tournament (a liga).
After checks, the user was saying that despite meeting those requirements, the Entry requirements: ≥ 10 rated games message was still there, and he could not join.

Shortly after, after being told that when it's green, it means they are good to go, they realized the join button needed

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

In sbt/sbt@c27ccae#diff-a04ab7c449116d324bc5fe384a88cacb1881c6fdef5b69bc47e13cdedc49f0b6 I diabled

dependency-graph/whatDependsOn* tests.

expectation

Reimplement something that tests this feature.

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