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

Hello Lichess!

How are you?

I am just writing to ask for the following issue:

When I send a request to https://lichess.org/api#operation/tournament, I am not being able to get the tournament description (it seems that is only possible to get the tournament name/"fullName").

For example:

curl -X GET \
  https://lichess.org/api/tournament/zQKZGjSG \
  -H 'cache-control: no-c

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

The Gatling Plugin does not work with Gradle 7.0, see:

 ❯ ./gradlew clean gatlingRun 
> Task :perf-test:gatlingLogback FAILED

FAILURE: Build failed with an exception.

* What went wrong:
A problem was found with the configuration of task ':perf-test:gatlingLogback' (type 'LogbackConfigTask').
  - Type 'LogbackConfigTask' property 'logbackConfigs' is missing an input or output annot

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

As https://dotty.epfl.ch/docs/reference/other-new-features/open-classes.html mentions:

Traits or abstract classes are always open, so open is redundant for them.

But right now open trait Foo and open abstract class Foo compile without error, they should at least emit a warning, like final object Foo already does.

Remove all additional resolvers from build.sbt, at least for releases, because artifacts published to Maven central repository should not contain additional repositories, and in fact don't need them because all dependencies are already in Maven central repo.

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