The GitHub Actions job "CI" on pekko-connectors.git/main has failed. Run started by GitHub user He-Pin (triggered by He-Pin).
Head commit for run: 8b3824158061e1160a9ea26533537f13b6abce67 / He-Pin(kerr) <[email protected]> Add -Yfuture-lazy-vals for Scala 3.3.x builds (#1674) * feat: Add -Yfuture-lazy-vals for Scala 3.3.x builds Motivation: The Scala 3.3.8 compiler introduced the -Yfuture-lazy-vals flag to optionally use VarHandle instead of sun.misc.Unsafe for lazy val implementation. This prepares libraries for upcoming JDK releases that restrict sun.misc.Unsafe access. Modification: Add -Yfuture-lazy-vals to scalacOptions, conditionally applied only for Scala 3.3.x via CrossVersion.partialVersion or scalaBinaryVersion. Result: Scala 3.3.x build uses the future-proof VarHandle-based lazy val implementation, compatible with all JDK 9+ versions including future releases that restrict sun.misc.Unsafe. References: Refs scala/scala3-lts#637 Refs apache/pekko#3059 * fix: Add MiMa filters for <clinit> removed by -Yfuture-lazy-vals -Yfuture-lazy-vals changes the generated bytecode for companion objects containing lazy vals: the static <clinit> initializer is no longer emitted. Add MiMa filters to exclude these expected binary compatibility changes for: - aws-spi-pekko-http: PekkoHttpClient - google-cloud-bigquery: BigQueryJsonProtocol, BigQueryRestJsonProtocol - google-cloud-pub-sub-grpc: ScalaPB-generated grpc objects * fix: Add missing Handshaker* MiMa filters in google-cloud-pub-sub-grpc Add 4 DirectMissingMethodProblem filters for HandshakerReq, HandshakerResp, HandshakerResult, and HandshakerStatus companion object <clinit> methods that are no longer generated with -Yfuture-lazy-vals. Report URL: https://github.com/apache/pekko-connectors/actions/runs/27499225144 With regards, GitHub Actions via GitBox --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
