[GH] (pekko-persistence-jdbc): Workflow run "Nightly Testing with Pekko 1.0" failed!

2024-11-11 Thread GitBox
The GitHub Actions job "Nightly Testing with Pekko 1.0" on pekko-persistence-jdbc.git has failed. Run started by GitHub user raboof (triggered by raboof). Head commit for run: 38f2c50f972d774efc20d9af2ff857949833d568 / PJ Fanning ignore links in license report (#250) Report URL: https://git

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

2024-11-11 Thread GitBox
The GitHub Actions job "Nightly Build and Test" on pekko-connectors-kafka.git has succeeded. Run started by GitHub user pjfanning (triggered by pjfanning). Head commit for run: 79535cfd4a6e36ecd78606bcbe1dcd2a61a57934 / PJ Fanning ignore broken links in license report (#259) Report URL: htt

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

2024-11-11 Thread GitBox
The GitHub Actions job "Nightly Tests" on pekko-management.git has failed. Run started by GitHub user pjfanning (triggered by pjfanning). Head commit for run: de01b7d7e06dab4e24f16f96c52673bd686095b3 / scala-steward-asf[bot] <147768647+scala-steward-asf[bot]@users.noreply.github.com> Update sbt

[GH] (pekko-management): Workflow run "Integration test for Kubernetes Lease" is working again!

2024-11-11 Thread GitBox
The GitHub Actions job "Integration test for Kubernetes Lease" on pekko-management.git has succeeded. Run started by GitHub user pjfanning (triggered by pjfanning). Head commit for run: de01b7d7e06dab4e24f16f96c52673bd686095b3 / scala-steward-asf[bot] <147768647+scala-steward-asf[bot]@users.no

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

2024-11-11 Thread GitBox
The GitHub Actions job "Nightly Builds" on pekko-http.git has failed. Run started by GitHub user He-Pin (triggered by He-Pin). Head commit for run: 4fb855464824540f9e5a452b5f85a7d1b4ad2a04 / PJ Fanning ignore links in license report (#629) Report URL: https://github.com/apache/pekko-http/acti

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

2024-11-11 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: 7f6ce904237781421060b4d2d9a72ad7dc8e72aa / scala-steward-asf[bot] <147768647+scala-steward-asf[bot]@users.noreply.github.com> Update sbt, scripted

[GH] (pekko): Workflow run "Nightly Builds (1.0)" is working again!

2024-11-11 Thread GitBox
The GitHub Actions job "Nightly Builds (1.0)" on pekko.git has succeeded. Run started by GitHub user pjfanning (triggered by pjfanning). Head commit for run: 7f6ce904237781421060b4d2d9a72ad7dc8e72aa / scala-steward-asf[bot] <147768647+scala-steward-asf[bot]@users.noreply.github.com> Update sbt,

Re: [D] Azure Blob Storage Connectors for Pekko [pekko-connectors]

2024-11-11 Thread via GitHub
GitHub user Susmit07 edited a comment on the discussion: Azure Blob Storage Connectors for Pekko the underlying logic for writing to different storage systems (S3, Azure Blob, etc.) is generally the same, with the main difference being how the SDKs for each platform are implemented. We alread

Re: [D] Azure Blob Storage Connectors for Pekko [pekko-connectors]

2024-11-11 Thread via GitHub
GitHub user Susmit07 added a comment to the discussion: Azure Blob Storage Connectors for Pekko the underlying logic for writing to different storage systems (S3, Azure Blob, etc.) is generally the same, with the main difference being how the SDKs for each platform are implemented. We already

[GH] (pekko): Workflow run "Publish nightly 1.0 snapshots" failed!

2024-11-11 Thread GitBox
The GitHub Actions job "Publish nightly 1.0 snapshots" on pekko.git has failed. Run started by GitHub user pjfanning (triggered by pjfanning). Head commit for run: 7f6ce904237781421060b4d2d9a72ad7dc8e72aa / scala-steward-asf[bot] <147768647+scala-steward-asf[bot]@users.noreply.github.com> Updat

Re: [D] Azure Blob Storage Connectors for Pekko [pekko-connectors]

2024-11-11 Thread via GitHub
GitHub user pjfanning added a comment to the discussion: Azure Blob Storage Connectors for Pekko If you have read the Alpakka PR, please don't submit any PR to us. You can create your own project and release it yourself. The ASF and the Pekko community cannot accept the risk of being accused

Re: [D] Azure Blob Storage Connectors for Pekko [pekko-connectors]

2024-11-11 Thread via GitHub
GitHub user Susmit07 added a comment to the discussion: Azure Blob Storage Connectors for Pekko I meant taking a reference from the PR its not a copy, actually it would have beem great if @asafali implemented but I will come up with my own like s3 GitHub link: https://github.com/apache/pekko

Re: [D] Azure Blob Storage Connectors for Pekko [pekko-connectors]

2024-11-11 Thread via GitHub
GitHub user pjfanning edited a comment on the discussion: Azure Blob Storage Connectors for Pekko That is not allowed. Work submitted to the ASF must be your own work. You cannot take someone else's work without their permission. And there is also the risk that the Lightbend team collaborated

Re: [D] Azure Blob Storage Connectors for Pekko [pekko-connectors]

2024-11-11 Thread via GitHub
GitHub user pjfanning edited a comment on the discussion: Azure Blob Storage Connectors for Pekko That is not allowed. Work submitted to the ASF must be your own work. You cannot take someone else's work without their permission. And there is also the risk that the Lightbend team collaborated

Re: [D] Azure Blob Storage Connectors for Pekko [pekko-connectors]

2024-11-11 Thread via GitHub
GitHub user pjfanning added a comment to the discussion: Azure Blob Storage Connectors for Pekko That is not allowed. Work submitted to the ASF must be your own work. You can take someone else's work without their permission. And there is also the risk that the Lightbend team collaborated on

Re: [D] Azure Blob Storage Connectors for Pekko [pekko-connectors]

2024-11-11 Thread via GitHub
GitHub user Susmit07 added a comment to the discussion: Azure Blob Storage Connectors for Pekko I checked the PR it looks fine by Syed Shall we fo ahead and implement the same in Pekko I can them work on creating a PR What do you guys suggest? GitHub link: https://github.com/apache/pekko

Re: [I] Incorrect import statements generated from GRPC plugin [pekko-grpc]

2024-11-11 Thread via GitHub
sfali23 closed issue #410: Incorrect import statements generated from GRPC plugin URL: https://github.com/apache/pekko-grpc/issues/410 -- 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 co

Re: [I] Incorrect import statements generated from GRPC plugin [pekko-grpc]

2024-11-11 Thread via GitHub
sfali23 commented on issue #410: URL: https://github.com/apache/pekko-grpc/issues/410#issuecomment-2468642546 Sorry my bad, I was having Pekko version mismatch and excluded all `org.apache.pekko` dependencies from grpc runtime and forgot to add individual dependencies. -- This is an auto

Re: [I] Incorrect import statements generated from GRPC plugin [pekko-grpc]

2024-11-11 Thread via GitHub
pjfanning commented on issue #410: URL: https://github.com/apache/pekko-grpc/issues/410#issuecomment-2468618877 If you get a compile issue, maybe you should report it to Scala3 team. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to Gi

Re: [I] Incorrect import statements generated from GRPC plugin [pekko-grpc]

2024-11-11 Thread via GitHub
pjfanning commented on issue #410: URL: https://github.com/apache/pekko-grpc/issues/410#issuecomment-2468616215 This is valid in Scala. You can import `org.apache.pekko` and then start later imports with just `pekko`. -- This is an automated message from the Apache Git Service. To respond

[I] Incorrect import statements generated from GRPC plugin [pekko-grpc]

2024-11-11 Thread via GitHub
sfali23 opened a new issue, #410: URL: https://github.com/apache/pekko-grpc/issues/410 It seems that GRPC plugin generated code has generated incorrect import statements, look at the following generated code `org.apache` is missing from the imports which is causing to fail at compile time.

Re: [PR] Update sbt-license-report to 1.7.0 [pekko-projection]

2024-11-11 Thread via GitHub
raboof closed pull request #226: Update sbt-license-report to 1.7.0 URL: https://github.com/apache/pekko-projection/pull/226 -- 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

Re: [PR] Update sbt-license-report to 1.7.0 [pekko-projection]

2024-11-11 Thread via GitHub
raboof commented on PR #226: URL: https://github.com/apache/pekko-projection/pull/226#issuecomment-2468572330 needs https://github.com/sbt/sbt-license-report/pull/145 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the

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

2024-11-11 Thread GitBox
The GitHub Actions job "CI" on pekko-connectors.git has failed. Run started by GitHub user raboof (triggered by raboof). Head commit for run: 4a175fef7644de2506a55df951b54e58b58dd8d6 / PJ Fanning remove TODO in workflow (#900) Report URL: https://github.com/apache/pekko-connectors/actions/run

Re: [PR] remove TODO in workflow [pekko-connectors]

2024-11-11 Thread via GitHub
raboof merged PR #900: URL: https://github.com/apache/pekko-connectors/pull/900 -- 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..

Re: [PR] ignore links in license report [pekko-http]

2024-11-11 Thread via GitHub
raboof merged PR #629: URL: https://github.com/apache/pekko-http/pull/629 -- 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] gRPC 1.1.1 release [pekko-site]

2024-11-11 Thread via GitHub
pjfanning merged PR #143: URL: https://github.com/apache/pekko-site/pull/143 -- 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...@p

[PR] remove TODO in workflow [pekko-connectors]

2024-11-11 Thread via GitHub
pjfanning opened a new pull request, #900: URL: https://github.com/apache/pekko-connectors/pull/900 we have [.github/workflows/link-validator.yml](https://github.com/apache/pekko-connectors/blob/bf5545d9b8d916e69c8f98c3c10cc72af364efdf/.github/workflows/link-validator.yml#L35) -- This i

Re: [PR] ignore links in license report [pekko-persistence-jdbc]

2024-11-11 Thread via GitHub
raboof merged PR #250: URL: https://github.com/apache/pekko-persistence-jdbc/pull/250 -- 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-unsu

[PR] ignore links in license report [pekko-persistence-jdbc]

2024-11-11 Thread via GitHub
pjfanning opened a new pull request, #250: URL: https://github.com/apache/pekko-persistence-jdbc/pull/250 see https://github.com/apache/pekko-management/pull/348 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL

[PR] ignore links in license report [pekko-http]

2024-11-11 Thread via GitHub
pjfanning opened a new pull request, #629: URL: https://github.com/apache/pekko-http/pull/629 see https://github.com/apache/pekko-management/pull/348 -- 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

Re: [I] plugin-tester-scala does not use specified version of protoc [pekko-grpc]

2024-11-11 Thread via GitHub
raboof closed issue #404: plugin-tester-scala does not use specified version of protoc URL: https://github.com/apache/pekko-grpc/issues/404 -- 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 specif

Re: [PR] plugin-tester-scala: set protoc version [pekko-grpc]

2024-11-11 Thread via GitHub
raboof merged PR #409: URL: https://github.com/apache/pekko-grpc/pull/409 -- 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] don't link validate license report [pekko-connectors]

2024-11-11 Thread via GitHub
raboof merged PR #899: URL: https://github.com/apache/pekko-connectors/pull/899 -- 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..

Re: [PR] ignore links in license report [pekko-projection]

2024-11-11 Thread via GitHub
raboof merged PR #232: URL: https://github.com/apache/pekko-projection/pull/232 -- 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..

Re: [PR] ignore broken links in license report [pekko-connectors-kafka]

2024-11-11 Thread via GitHub
raboof merged PR #259: URL: https://github.com/apache/pekko-connectors-kafka/pull/259 -- 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-unsu