[GH] (pekko): Workflow run "Nightly Aeron Tests" failed!

2025-03-12 Thread GitBox
The GitHub Actions job "Nightly Aeron Tests" on pekko.git has failed. Run started by GitHub user jrudolph (triggered by jrudolph). Head commit for run: 2e62c50db51747e9cb17a5a35a2c638bd9488e46 / PJ Fanning Persistence API: add CurrentLastSequenceNumberByPersistenceIdQuery (#1773) * new Curren

[GH] (pekko-persistence-cassandra): Workflow run "Unit Tests" failed!

2025-03-12 Thread GitBox
The GitHub Actions job "Unit Tests" on pekko-persistence-cassandra.git has failed. Run started by GitHub user mdedetrich (triggered by mdedetrich). Head commit for run: 31c9f7579c90f092430b6e75fa04c50f0e4aa4d8 / scala-steward-asf[bot] <147768647+scala-steward-asf[bot]@users.noreply.github.com>

[GH] (pekko): Workflow run "Nightly Builds" failed!

2025-03-12 Thread GitBox
The GitHub Actions job "Nightly Builds" on pekko.git has failed. Run started by GitHub user pjfanning (triggered by pjfanning). Head commit for run: 2e62c50db51747e9cb17a5a35a2c638bd9488e46 / PJ Fanning Persistence API: add CurrentLastSequenceNumberByPersistenceIdQuery (#1773) * new CurrentLa

[GH] (pekko-connectors-kafka): Workflow run "Nightly Build and Test" failed!

2025-03-12 Thread GitBox
The GitHub Actions job "Nightly Build and Test" on pekko-connectors-kafka.git has failed. Run started by GitHub user pjfanning (triggered by pjfanning). Head commit for run: cdf1b100038f36ba195ee21c62a807698d05ae28 / scala-steward-asf[bot] <147768647+scala-steward-asf[bot]@users.noreply.github

Re: [PR] Test Netty 4.2.0.RC4 [pekko]

2025-03-12 Thread via GitHub
He-Pin commented on PR #1794: URL: https://github.com/apache/pekko/pull/1794#issuecomment-2719699031 @pjfanning That will require flink to upgrade netty too. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL abov

[GH] (pekko-connectors): Workflow run "Nightly Builds" failed!

2025-03-12 Thread GitBox
The GitHub Actions job "Nightly Builds" on pekko-connectors.git has failed. Run started by GitHub user He-Pin (triggered by He-Pin). Head commit for run: 401cb12e93ca75790435e2dc0578387903d62d3b / scala-steward-asf[bot] <147768647+scala-steward-asf[bot]@users.noreply.github.com> Update auth, dy

Re: [PR] try protobuf-java 4.29.3 [pekko]

2025-03-12 Thread via GitHub
pjfanning commented on PR #1795: URL: https://github.com/apache/pekko/pull/1795#issuecomment-2717874334 Pekko gRPC uses the io.grpc libs and has a direct dependency on the google protobuf jars. Pekko core depends on our shaded jar. So we can update independently. Pekko gRPC has a PR but it

[GH] (pekko): Workflow run "Binary Compatibility" failed!

2025-03-12 Thread GitBox
The GitHub Actions job "Binary Compatibility" on pekko.git has failed. Run started by GitHub user pjfanning (triggered by pjfanning). Head commit for run: bcbe18228dffe380d6c231144aa97a35886193f2 / PJ Fanning more mima Report URL: https://github.com/apache/pekko/actions/runs/13819274029 With

[GH] (pekko): Workflow run "Binary Compatibility" is working again!

2025-03-12 Thread GitBox
The GitHub Actions job "Binary Compatibility" on pekko.git has succeeded. Run started by GitHub user pjfanning (triggered by pjfanning). Head commit for run: 106ca6799668c26274f031674e9c81630671e525 / PJ Fanning Update protoc4-upgrade.excludes Report URL: https://github.com/apache/pekko/actio

[GH] (pekko): Workflow run "Generate doc check" is working again!

2025-03-12 Thread GitBox
The GitHub Actions job "Generate doc check" on pekko.git has succeeded. Run started by GitHub user pjfanning (triggered by pjfanning). Head commit for run: bcbe18228dffe380d6c231144aa97a35886193f2 / PJ Fanning more mima Report URL: https://github.com/apache/pekko/actions/runs/13819274019 Wit

Re: [PR] try protobuf-java 4.29.3 [pekko]

2025-03-12 Thread via GitHub
raboof commented on PR #1795: URL: https://github.com/apache/pekko/pull/1795#issuecomment-2717857440 > * Seems to work - tests pass Very cool! > * Big binary compatibility diffs for the generated classes > > Do we expect this to cause issues for users? I don't think they

Re: [PR] try protobuf-java 4.29.3 [pekko]

2025-03-12 Thread via GitHub
raboof commented on PR #1795: URL: https://github.com/apache/pekko/pull/1795#issuecomment-2717879531 > Pekko gRPC uses the io.grpc libs and has a direct dependency on the google protobuf jars. Pekko core depends on our shaded jar. So we can update independently. I agree that's the th

[GH] (pekko): Workflow run "Pull Requests" is working again!

2025-03-12 Thread GitBox
The GitHub Actions job "Pull Requests" on pekko.git has succeeded. Run started by GitHub user pjfanning (triggered by pjfanning). Head commit for run: 106ca6799668c26274f031674e9c81630671e525 / PJ Fanning Update protoc4-upgrade.excludes Report URL: https://github.com/apache/pekko/actions/runs

Re: [PR] feat: Add flatmapConcat with parallelism support [pekko]

2025-03-12 Thread via GitHub
He-Pin commented on PR #1702: URL: https://github.com/apache/pekko/pull/1702#issuecomment-2719139551 It it not really related. -- 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

Re: [I] Feature request: Add flatmapConcat with parallelism [pekko]

2025-03-12 Thread via GitHub
He-Pin closed issue #1672: Feature request: Add flatmapConcat with parallelism URL: https://github.com/apache/pekko/issues/1672 -- 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.

Re: [PR] feat: Add flatmapConcat with parallelism support [pekko]

2025-03-12 Thread via GitHub
He-Pin merged PR #1702: URL: https://github.com/apache/pekko/pull/1702 -- 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: notifications-unsubscr...@pekko.a

[GH] (pekko): Workflow run "Nightly Builds (1.1)" failed!

2025-03-12 Thread GitBox
The GitHub Actions job "Nightly Builds (1.1)" on pekko.git has failed. Run started by GitHub user pjfanning (triggered by pjfanning). Head commit for run: 2e62c50db51747e9cb17a5a35a2c638bd9488e46 / PJ Fanning Persistence API: add CurrentLastSequenceNumberByPersistenceIdQuery (#1773) * new Cur

[GH] (pekko-persistence-r2dbc): Workflow run "Nightly Tests (Pekko 1.0.x)" failed!

2025-03-12 Thread GitBox
The GitHub Actions job "Nightly Tests (Pekko 1.0.x)" on pekko-persistence-r2dbc.git has failed. Run started by GitHub user pjfanning (triggered by pjfanning). Head commit for run: dbc17bb394bf559fa5d13ef2589124a81c5f707a / scala-steward-asf[bot] <147768647+scala-steward-asf[bot]@users.noreply.

[PR] update function name to match pekko API change [pekko-persistence-jdbc]

2025-03-12 Thread via GitHub
pjfanning opened a new pull request, #271: URL: https://github.com/apache/pekko-persistence-jdbc/pull/271 adjust #267 to match API agreed in https://github.com/apache/pekko/pull/1773 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to Gi

[GH] (pekko): Workflow run "Timing sensitive tests" is working again!

2025-03-12 Thread GitBox
The GitHub Actions job "Timing sensitive tests" on pekko.git has succeeded. Run started by GitHub user pjfanning (triggered by pjfanning). Head commit for run: 2e62c50db51747e9cb17a5a35a2c638bd9488e46 / PJ Fanning Persistence API: add CurrentLastSequenceNumberByPersistenceIdQuery (#1773) * ne

Re: [PR] Persistence API: add CurrentLastSequenceNumberByPersistenceIdQuery [pekko]

2025-03-12 Thread via GitHub
pjfanning merged PR #1773: URL: https://github.com/apache/pekko/pull/1773 -- 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: notifications-unsubscr...@pekk

Re: [PR] Test Netty 4.2.0.RC4 [pekko]

2025-03-12 Thread via GitHub
pjfanning commented on PR #1794: URL: https://github.com/apache/pekko/pull/1794#issuecomment-2719214435 I wouldn't delay the 1.2.0 release for this but if 4.2.0 final release is made before we make the 1.2.0 final release then I think we should upgrade. -- This is an automated message fro