The GitHub Actions job "Nightly Builds (1.7)" on pekko.git/main has failed.
Run started by GitHub user pjfanning (triggered by pjfanning).

Head commit for run:
ee6965cd58098584dbc17a61d37e038faa5e8f99 / He-Pin(kerr) <[email protected]>
fix: Scala 3.8 syntax compat fixes and import cleanup (#3074)

Motivation:
Scala 3.8 introduces stricter syntax requirements and new warnings for
patterns that will be removed in future versions. Several code patterns
need updates for forward compatibility.

Modification:
- Replace _ wildcard type with ? in scala-3 source directories
  (Platform.scala, ClusterReceptionistProtocol.scala)
- Add explicit using keyword for implicit argument forwarding in
  ByteIterator.scala (scala-3): getShort(using byteOrder)
- Add @unchecked annotations for type-test patterns that cannot be
  checked at runtime in AskPattern.scala and ByteString.scala
- Replace eta expansion syntax apply _ with explicit lambda
  ref => apply(ref) in Patterns.scala (4 occurrences)
- Fix SortedSet.empty implicit ordering in SimpleDnsCache.scala by
  binding ordering as implicit val before calling .empty
- Replace infix type syntax AnyRef JPair AnyRef with JPair[AnyRef, AnyRef]
  in ConstantFun.scala
- Add LogSource implicit val bindings for Logging calls in Ops.scala
- Add implicit def selfSender in SourceRefImpl.scala
- Fix Logging factory call in MultiNodeSpec.scala
- Fix discard result pattern in FixedBufferSpec.scala
- Import reordering and formatting across ~35 files for scalafmt
  compliance
- Fix Scaladoc apostrophe in CallingThreadDispatcher.scala
- Fix doc reference "Java 8" to "Java" in operators/index.md
- Remove unused import in SnapshotStorage.scala

Result:
Code compiles cleanly with Scala 3.8 syntax requirements. No behavioral
changes to the runtime.

Tests:
Not run - syntax compat fixes, verified by cross-compilation

References:
None - proactive Scala 3.8 forward compatibility

Report URL: https://github.com/apache/pekko/actions/runs/27587736909

With regards,
GitHub Actions via GitBox


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to