Scala

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

The following strings need to be made translatable:

• On the puzzle dashboard: The title itself (Puzzle dashboard), the subtitle (Train, analyse, improve) and the text in the three big "buttons" (PLAYED, PERFORMANCE, SOLVED).
• On the puzzles by topic page, the message on the bottom (These puzzles are in the public domain, and can be downloaded from database.lichess.org.)
• On the improvement

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

"they were deprecated for ages in Scala 2 and were dropped in 2.13"

Compiler version

3.0.0, 3.0.3-RC1-bin-20210727-b902516-NIGHTLY

Minimized code

$ scala3 -Xprint:typer
scala> "\u001b"                                                                                                                                     

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

Use the following project/build.properties:

sbt.version=1.5.4

and the following build.sbt:

inThisBuild(Def.settings(
  crossScalaVersions := Seq("2.12.3", "2.10.6"),
  scalaVersion := "2.12.3",

  crossSbtVersions := Seq("1.0.2", "0.13.16"),
))

lazy val `sbt-platform-deps` = project.in(file("."))
  .enablePlugins(SbtPlugin)

Launch sbt

p

It would be useful to have a java.util.BitSet implementation. It looks like most Java collections are available but this one fell through the cracks (perhaps because it's not part of the Collection hierarchy).

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

$ sw_vers
ProductName:	Mac OS X
ProductVersion:	10.14.6
BuildVersion:	18G9028

struct utsname name;
    if (uname(&name) == 0) {
        printf("os.name=%s\n",name.sysname);
        printf("os.version=%s\n",name.release);
    }
// os.name=Darwin
// os.version=18.7.0

Seems no way to map Darwin version to Mac OS X version.

/usr/libexec/PlistBuddy -c "Print: