mdedetrich opened a new pull request, #23080:
URL: https://github.com/apache/flink/pull/23080

   ## What is the purpose of the change
   
   This PR bumps Pekko from v1.0.0 to 1.0.1. The main and hence only change 
from Pekko 1.0.0 to Pekko 1.0.1 is 
https://github.com/apache/incubator-pekko/pull/492, see issue at 
https://github.com/apache/incubator-pekko/issues/491.
   
   Just to provide some context, the core issue is that using `$` in any symbol 
name for user defined classes breaks the JVM spec (initially it was thought 
that it only broke the Scala spec but this was later clarified in 
https://github.com/lampepfl/dotty/issues/18234#issuecomment-1639861800 ).
   
   While it is highly unlikely that using Pekko 1.0.0 will cause any problems, 
if there does happen to be an issue theoretically speaking it wouldn't be self 
contained to only Scala users.
   
   ## Brief change log
   
   * Update Pekko dependency to 1.0.1 as well as updating `NOTICE` file
   
   
   ## Verifying this change
   
   Please make sure both new and modified tests in this PR follows the 
conventions defined in our code quality guide: 
https://flink.apache.org/contributing/code-style-and-quality-common.html#testing
   
   This change is already covered by existing tests, such as *(please describe 
tests)*.
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): yes
     - The public API, i.e., is any changed class annotated with 
`@Public(Evolving)`: no
     - The serializers: no
     - The runtime per-record code paths (performance sensitive): no
     - Anything that affects deployment or recovery: JobManager (and its 
components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
     - The S3 file system connector: no
   
   ## Documentation
   
     - Does this pull request introduce a new feature? no
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to