Michael Pilquist
Michael Pilquist
Looks like there are native artifacts for 2.12 and 2.13 but not Scala 3.
Similar to #2392, `Files.walkFileTree` is inconsistent with JVM behavior in presence of walks while following links and encountering cycles. Reproduction case: ```scala //> using scala 3.3.1 import java.nio.file.* import java.nio.file.attribute.BasicFileAttributes...
First noticed in #858 ``` ==> X tests.issue.Test238.see (https://github.com/functional-streams-for-scala/fs2/pull/1989) 0.023s javax.net.ssl.SSLException: Fail to unwrap network record at sun.security.ssl.Alert.createSSLException(Alert.java:133) at sun.security.ssl.TransportContext.fatal(TransportContext.java:360) at sun.security.ssl.TransportContext.fatal(TransportContext.java:303) at sun.security.ssl.SSLEngineImpl.unwrap(SSLEngineImpl.java:470) at sun.security.ssl.SSLEngineImpl.unwrap(SSLEngineImpl.java:433) at javax.net.ssl.SSLEngine.unwrap(SSLEngine.java:637) at fs2.io.net.tls.TLSEngine$$anon$1.$anonfun$unwrap$1(TLSEngine.scala:158)...
The test that hangs is `failed login with SSL.System (ssl available)`. Debug output when it fails: ``` → StartupMessage(jimmy,world,Map(client_min_messages -> WARNING, DateStyle -> ISO, MDY, IntervalStyle -> iso_8601, client_encoding ->...
Drops the specialized `walkEager` optimization as `walkJustInTime` is just as efficient in the case where `chunkSize = Int.MaxValue`. This lets us get rid of the specialized platform traits (`AsyncFilesPlatform`). Merge...
This provides better performance than `Files[F].walk(path).evalMap(p => p -> Files[F].getBasicFileAttributes(p))` given that all implementations of `walk` use file attributes. Some use cases: Computing cumulative size of a tree: ```scala Files[F].walkWithAttributes(path).map(_.attributes.size).compile.foldMonoid...
``` ==> X fs2.StreamCombinatorsSuite.evalFilterNotAsync - filters up to N items in parallel 2.02s java.util.NoSuchElementException: null [1133](https://github.com/mpilquist/fs2/actions/runs/4124422453/jobs/7123653749#step:11:1134) at fs2.Stream$CompileOps.lastOrError$$anonfun$1$$anonfun$1(Stream.scala:4875) [1134](https://github.com/mpilquist/fs2/actions/runs/4124422453/jobs/7123653749#step:11:1135) at scala.Option.fold(Option.scala:263) [1135](https://github.com/mpilquist/fs2/actions/runs/4124422453/jobs/7123653749#step:11:1136) at fs2.Stream$CompileOps.lastOrError$$anonfun$1(Stream.scala:4875) [1136](https://github.com/mpilquist/fs2/actions/runs/4124422453/jobs/7123653749#step:11:1137) at flatMap @ fs2.Compiler$Target.flatMap(Compiler.scala:163) [1137](https://github.com/mpilquist/fs2/actions/runs/4124422453/jobs/7123653749#step:11:1138)...
No longer compiles due to changes in ambiguous extension methods. Related to #9.
ScalaCheck provides a small DSL for writing properties, consisting of syntax like: - implication (`p1 ==> p2`) - combining properties (`&&`, `||`, `==`, `all`, `atLeastOne`) - labeling (`p :| "label"`)...
ScalaCheck supports this like so: ```scala scala> val p = Prop.forAll { (x: Int, y: Int) => (x + y) == (y + x) } val p: org.scalacheck.Prop = Prop...