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

2025-03-20 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: c5ccfde67165af748b64b9179210ba1277ce6f96 / PJ Fanning java 24 Report URL: https://github.com/apache/pekko/actions/runs/13979953445 With regar

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

2025-03-20 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: c5ccfde67165af748b64b9179210ba1277ce6f96 / PJ Fanning java 24 Report URL: https://github.com/apache/pekko/actions/runs/13979953457 With

Re: [PR] fix: postgres durable state schemaName change leads to write errors (#275) [pekko-persistence-jdbc]

2025-03-20 Thread via GitHub
pjfanning commented on code in PR #276: URL: https://github.com/apache/pekko-persistence-jdbc/pull/276#discussion_r2006393568 ## integration-test/src/test/scala/org/apache/pekko/persistence/jdbc/integration/AllPersistenceIdsTest.scala: ## @@ -9,13 +9,7 @@ package org.apache.

[GH] (pekko-persistence-jdbc): Workflow run "SqlServer Integration Tests" failed!

2025-03-20 Thread GitBox
The GitHub Actions job "SqlServer Integration Tests" on pekko-persistence-jdbc.git has failed. Run started by GitHub user pjfanning (triggered by pjfanning). Head commit for run: a76b3afdf8a38136ce0dcaddb42e30912b55db89 / PJ Fanning use ubuntu 22 in CI Report URL: https://github.com/apache/

[PR] use ubuntu 22 in CI [pekko-persistence-jdbc]

2025-03-20 Thread via GitHub
pjfanning opened a new pull request, #277: URL: https://github.com/apache/pekko-persistence-jdbc/pull/277 brownout warnings for ubuntu 20 https://github.blog/changelog/2025-01-15-github-actions-ubuntu-20-runner-image-brownout-dates-and-other-breaking-changes/ -- This is an auto

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

2025-03-20 Thread GitBox
The GitHub Actions job "Scalafmt" on pekko.git has succeeded. Run started by GitHub user pjfanning (triggered by pjfanning). Head commit for run: c5ccfde67165af748b64b9179210ba1277ce6f96 / PJ Fanning java 24 Report URL: https://github.com/apache/pekko/actions/runs/13979953449 With regards, G

Re: [PR] fix: postgres durable state schemaName change leads to write errors (#275) [pekko-persistence-jdbc]

2025-03-20 Thread via GitHub
pjfanning commented on code in PR #276: URL: https://github.com/apache/pekko-persistence-jdbc/pull/276#discussion_r2005379523 ## core/src/main/scala/org/apache/pekko/persistence/jdbc/config/PekkoPersistenceConfig.scala: ## @@ -221,7 +221,10 @@ class DurableStateTableConfigurati

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

2025-03-20 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: 9b1f82319d830d1ecbc96bd7e8fdf3dda198681b / scala-steward-asf[bot] <147768647+scala-steward-asf[bot]@users.noreply.github.com> Update junit-jupi

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

2025-03-20 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: 9b1f82319d830d1ecbc96bd7e8fdf3dda198681b / scala-steward-asf[bot] <147768647+scala-steward-asf[bot]@users.noreply.github.com> Update junit-jupiter

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

2025-03-20 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: c5ccfde67165af748b64b9179210ba1277ce6f96 / PJ Fanning java 24 Report URL: https://github.com/apache/pekko/actions/runs/13979953469 Wit

[GH] (pekko): Workflow run "Build and test Pekko with Scala 3" failed!

2025-03-20 Thread GitBox
The GitHub Actions job "Build and test Pekko with Scala 3" on pekko.git has failed. Run started by GitHub user pjfanning (triggered by pjfanning). Head commit for run: c5ccfde67165af748b64b9179210ba1277ce6f96 / PJ Fanning java 24 Report URL: https://github.com/apache/pekko/actions/runs/13979

[GH] (pekko): Workflow run "Pull Requests" failed!

2025-03-20 Thread GitBox
The GitHub Actions job "Pull Requests" on pekko.git has failed. Run started by GitHub user jypma (triggered by He-Pin). Head commit for run: e24af06e38ef3b33ce33889fb687db06b82317aa / Jan Ypma Introduce Task monad This commit introduces Task, a data structure that represents a recipe, or progr

[GH] (pekko): Workflow run "Build and test Pekko with Scala 3" failed!

2025-03-20 Thread GitBox
The GitHub Actions job "Build and test Pekko with Scala 3" on pekko.git has failed. Run started by GitHub user jypma (triggered by He-Pin). Head commit for run: e24af06e38ef3b33ce33889fb687db06b82317aa / Jan Ypma Introduce Task monad This commit introduces Task, a data structure that represen

Re: [PR] fix: postgres durable state schemaName change leads to write errors (#275) [pekko-persistence-jdbc]

2025-03-20 Thread via GitHub
pjfanning commented on code in PR #276: URL: https://github.com/apache/pekko-persistence-jdbc/pull/276#discussion_r2005420700 ## integration-test/src/test/scala/org/apache/pekko/persistence/jdbc/integration/JdbcJournalSpec.scala: ## @@ -11,10 +11,11 @@ package org.apache.pekko.

Re: [I] jdbc-durable-state-store for postgres schemaName is ignored / leads to errors [pekko-persistence-jdbc]

2025-03-20 Thread via GitHub
pjfanning commented on issue #275: URL: https://github.com/apache/pekko-persistence-jdbc/issues/275#issuecomment-2740081425 This is the reference.conf ``` durable_state { ## The table and column names are not always read and used in SQL statements. If you change

Re: [I] jdbc-durable-state-store for postgres schemaName is ignored / leads to errors [pekko-persistence-jdbc]

2025-03-20 Thread via GitHub
pjfanning commented on issue #275: URL: https://github.com/apache/pekko-persistence-jdbc/issues/275#issuecomment-2740425435 @patsta32 Hear me out. I'm not trying to shoot down #276 and I'm willing to collaborate on that PR. But: Since we are already in a bit of a mess here with schema su

Re: [I] jdbc-durable-state-store for postgres schemaName is ignored / leads to errors [pekko-persistence-jdbc]

2025-03-20 Thread via GitHub
pjfanning commented on issue #275: URL: https://github.com/apache/pekko-persistence-jdbc/issues/275#issuecomment-2740453992 The thing about the scripts, they are really more designed for use to set up test runs and to act as an editable template for people who want to set up a production e

Re: [I] jdbc-durable-state-store for postgres schemaName is ignored / leads to errors [pekko-persistence-jdbc]

2025-03-20 Thread via GitHub
pjfanning commented on issue #275: URL: https://github.com/apache/pekko-persistence-jdbc/issues/275#issuecomment-2740033533 is this only an issue for postgres users or does it affect other db users? -- This is an automated message from the Apache Git Service. To respond to the message, pl

Re: [PR] fix: postgres durable state schemaName change leads to write errors (#275) [pekko-persistence-jdbc]

2025-03-20 Thread via GitHub
pjfanning commented on code in PR #276: URL: https://github.com/apache/pekko-persistence-jdbc/pull/276#discussion_r2005380919 ## core/src/main/scala/org/apache/pekko/persistence/jdbc/config/PekkoPersistenceConfig.scala: ## @@ -221,7 +221,10 @@ class DurableStateTableConfigurati

Re: [I] jdbc-durable-state-store for postgres schemaName is ignored / leads to errors [pekko-persistence-jdbc]

2025-03-20 Thread via GitHub
patsta32 commented on issue #275: URL: https://github.com/apache/pekko-persistence-jdbc/issues/275#issuecomment-2740776000 @pjfanning Hey, i am sorry and i think there is a miscommunication on my side, thanks for your patience with the PR. So i like your idea to make things clear fir

Re: [I] jdbc-durable-state-store for postgres schemaName is ignored / leads to errors [pekko-persistence-jdbc]

2025-03-20 Thread via GitHub
pjfanning commented on issue #275: URL: https://github.com/apache/pekko-persistence-jdbc/issues/275#issuecomment-2740798622 Can you remove the sql changes and have a unit test with its own setup that creates a schema called `pekko` and installs the tables in that schema? I don't mind dupli

Re: [PR] Configuring persistence plugins at runtime [pekko-persistence-r2dbc]

2025-03-20 Thread via GitHub
ptrdom commented on PR #194: URL: https://github.com/apache/pekko-persistence-r2dbc/pull/194#issuecomment-2740970260 All good, I will try to make the old configs work, and if I will face any problems that need discussing I will raise them. -- This is an automated message from the Apache