The GitHub Actions job "Nightly Testing with Pekko 1.0" on
pekko-persistence-jdbc.git has succeeded.
Run started by GitHub user raboof (triggered by raboof).
Head commit for run:
2c97844e3a3afe39c4c8898ff4acbf19592c8567 / PJ Fanning
release 1.1.0 (#223)
* release 1.1.0
* Update publish-1.1-
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:
67b53e452bc8dd8b2e7650702c37bd77fa0131b7 / PJ Fanning
allow check-build-test to run for 1.0.x branch (#228)
Report URL
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:
269be3beec562aeec81bace3566c1613b5b44fa9 / PJ Fanning
copy PekkoCoreDependency from main branch and anything neede
The GitHub Actions job "MySQL Integration Tests" on pekko-persistence-jdbc.git
has failed.
Run started by GitHub user pjfanning (triggered by pjfanning).
Head commit for run:
269be3beec562aeec81bace3566c1613b5b44fa9 / PJ Fanning
copy PekkoCoreDependency from main branch and anything needed to
The GitHub Actions job "Oracle Integration Tests" on pekko-persistence-jdbc.git
has failed.
Run started by GitHub user pjfanning (triggered by pjfanning).
Head commit for run:
269be3beec562aeec81bace3566c1613b5b44fa9 / PJ Fanning
copy PekkoCoreDependency from main branch and anything needed t
The GitHub Actions job "Postgres Integration Tests" on
pekko-persistence-jdbc.git has failed.
Run started by GitHub user pjfanning (triggered by pjfanning).
Head commit for run:
269be3beec562aeec81bace3566c1613b5b44fa9 / PJ Fanning
copy PekkoCoreDependency from main branch and anything needed
The GitHub Actions job "Oracle Integration Tests" on pekko-persistence-jdbc.git
has failed.
Run started by GitHub user pjfanning (triggered by pjfanning).
Head commit for run:
f93ae91cb5e33105e5898ce75dc43ec44bfdee14 / PJ Fanning
redirect current to versioned docs (#227)
* redirect current t
The GitHub Actions job "MySQL Integration Tests" on pekko-persistence-jdbc.git
has failed.
Run started by GitHub user pjfanning (triggered by pjfanning).
Head commit for run:
f93ae91cb5e33105e5898ce75dc43ec44bfdee14 / PJ Fanning
redirect current to versioned docs (#227)
* redirect current to
The GitHub Actions job "Postgres Integration Tests" on
pekko-persistence-jdbc.git has failed.
Run started by GitHub user pjfanning (triggered by pjfanning).
Head commit for run:
f93ae91cb5e33105e5898ce75dc43ec44bfdee14 / PJ Fanning
redirect current to versioned docs (#227)
* redirect current
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:
f93ae91cb5e33105e5898ce75dc43ec44bfdee14 / PJ Fanning
redirect current to versioned docs (#227)
* redirect curren
GitHub user Roiocam added a comment to the discussion: Azure SQL support?
seems like Azure SQL is based on SQL Server(Aka MSSQL), did you try SQLServer
driver for the AzureSQL connecting?
GitHub link:
https://github.com/apache/pekko-persistence-jdbc/discussions/228#discussioncomment-10676303
Roiocam commented on code in PR #1485:
URL: https://github.com/apache/pekko/pull/1485#discussion_r1764275206
##
actor/src/main/scala/org/apache/pekko/actor/dungeon/Dispatch.scala:
##
@@ -159,7 +159,7 @@ private[pekko] trait Dispatch { this: ActorCell =>
catch handleExceptio
Roiocam commented on issue #1484:
URL: https://github.com/apache/pekko/issues/1484#issuecomment-2357309689
I agree with _"One option might be to mark some of the functions that Kamon
relies on instrumenting as @noinline."_
Creating an un-instrumentation library is not what we want, bu
The GitHub Actions job "Nightly Builds" on pekko.git has failed.
Run started by GitHub user pjfanning (triggered by pjfanning).
Head commit for run:
22a738511375baa23c5b84c87d44a065c0401e0e / PJ Fanning
simplify scala 3 build in CI (#1486)
* simplify scala 3 build in CI
* Update scala3-build
The GitHub Actions job "Nightly Builds (1.0)" on pekko.git has failed.
Run started by GitHub user pjfanning (triggered by pjfanning).
Head commit for run:
22a738511375baa23c5b84c87d44a065c0401e0e / PJ Fanning
simplify scala 3 build in CI (#1486)
* simplify scala 3 build in CI
* Update scala3
pjfanning merged PR #131:
URL: https://github.com/apache/pekko-site/pull/131
--
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
pjfanning merged PR #1486:
URL: https://github.com/apache/pekko/pull/1486
--
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
pjfanning opened a new pull request, #131:
URL: https://github.com/apache/pekko-site/pull/131
release vote has passed
--
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 uns
The GitHub Actions job "H2 Unit Tests" on pekko-persistence-jdbc.git has
succeeded.
Run started by GitHub user pjfanning (triggered by pjfanning).
Head commit for run:
269be3beec562aeec81bace3566c1613b5b44fa9 / PJ Fanning
copy PekkoCoreDependency from main branch and anything needed to build
The GitHub Actions job "Link Validator" on pekko-persistence-jdbc.git has
succeeded.
Run started by GitHub user pjfanning (triggered by pjfanning).
Head commit for run:
269be3beec562aeec81bace3566c1613b5b44fa9 / PJ Fanning
copy PekkoCoreDependency from main branch and anything needed to build
The GitHub Actions job "Basic checks" on pekko-persistence-jdbc.git has
succeeded.
Run started by GitHub user pjfanning (triggered by pjfanning).
Head commit for run:
269be3beec562aeec81bace3566c1613b5b44fa9 / PJ Fanning
copy PekkoCoreDependency from main branch and anything needed to build i
The GitHub Actions job "Headers" on pekko-persistence-jdbc.git has succeeded.
Run started by GitHub user pjfanning (triggered by pjfanning).
Head commit for run:
269be3beec562aeec81bace3566c1613b5b44fa9 / PJ Fanning
copy PekkoCoreDependency from main branch and anything needed to build it
Rep
The GitHub Actions job "Link Validator" on pekko-persistence-jdbc.git has
failed.
Run started by GitHub user pjfanning (triggered by pjfanning).
Head commit for run:
f93ae91cb5e33105e5898ce75dc43ec44bfdee14 / PJ Fanning
redirect current to versioned docs (#227)
* redirect current to versione
The GitHub Actions job "H2 Unit Tests" on pekko-persistence-jdbc.git has failed.
Run started by GitHub user pjfanning (triggered by pjfanning).
Head commit for run:
f93ae91cb5e33105e5898ce75dc43ec44bfdee14 / PJ Fanning
redirect current to versioned docs (#227)
* redirect current to versioned
The GitHub Actions job "Headers" on pekko-persistence-jdbc.git has failed.
Run started by GitHub user pjfanning (triggered by pjfanning).
Head commit for run:
f93ae91cb5e33105e5898ce75dc43ec44bfdee14 / PJ Fanning
redirect current to versioned docs (#227)
* redirect current to versioned docs
The GitHub Actions job "Basic checks" on pekko-persistence-jdbc.git has failed.
Run started by GitHub user pjfanning (triggered by pjfanning).
Head commit for run:
f93ae91cb5e33105e5898ce75dc43ec44bfdee14 / PJ Fanning
redirect current to versioned docs (#227)
* redirect current to versioned d
pjfanning opened a new pull request, #229:
URL: https://github.com/apache/pekko-persistence-jdbc/pull/229
* redirect current to versioned docs
* Update build.sbt
* cherry pick 88acd7b48fab72145368eb23e2425fa3cc488631 #227
--
This is an automated message from the Apache Git Service.
T
pjfanning merged PR #223:
URL: https://github.com/apache/pekko-persistence-jdbc/pull/223
--
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-u
pjfanning commented on code in PR #223:
URL:
https://github.com/apache/pekko-persistence-jdbc/pull/223#discussion_r1763873382
##
docs/src/main/paradox/release-notes/releases-1.1.md:
##
@@ -1,9 +1,8 @@
# Release Notes (1.1.x)
-## 1.1.0-M1
+## 1.1.0
-Release notes for Apache
pjfanning merged PR #227:
URL: https://github.com/apache/pekko-persistence-jdbc/pull/227
--
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-u
lrytz commented on issue #1484:
URL: https://github.com/apache/pekko/issues/1484#issuecomment-2356733980
yes, the answer is yes :)
--
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 com
The GitHub Actions job "Unit Tests" on pekko-projection.git has succeeded.
Run started by GitHub user pjfanning (triggered by pjfanning).
Head commit for run:
3c0d4b513ba7eb18cf760f07f22eff74708e85a8 / PJ Fanning
pekkoPersistenceJdbc = "1.1.0"
Report URL: https://github.com/apache/pekko-proje
mdedetrich commented on issue #1484:
URL: https://github.com/apache/pekko/issues/1484#issuecomment-2356509251
> It seems like the Scala 2 compiler can inline any functions that are
marked as `final`. Does anyone know what happens if a class is marked as
`final`, does that mean all of its fu
The GitHub Actions job "Integration Tests for Kafka" on pekko-projection.git
has succeeded.
Run started by GitHub user pjfanning (triggered by pjfanning).
Head commit for run:
3c0d4b513ba7eb18cf760f07f22eff74708e85a8 / PJ Fanning
pekkoPersistenceJdbc = "1.1.0"
Report URL: https://github.com/
raboof commented on code in PR #223:
URL:
https://github.com/apache/pekko-persistence-jdbc/pull/223#discussion_r1763624270
##
docs/src/main/paradox/release-notes/releases-1.1.md:
##
@@ -1,9 +1,8 @@
# Release Notes (1.1.x)
-## 1.1.0-M1
+## 1.1.0
-Release notes for Apache Pe
pjfanning commented on issue #1484:
URL: https://github.com/apache/pekko/issues/1484#issuecomment-2356390453
It seems like the Scala 2 compiler can inline any functions that are marked
as `final`. Does anyone know what happens if a class is marked as `final`, does
that mean all of its funct
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:
82991a5b2128270adbde1f2ed1e335443c596465 / PJ Fanning
mark stop() method as noinline
Report URL: https://github.com/apache/pekko/actions/
The GitHub Actions job "Binary Compatibility" on pekko.git has succeeded.
Run started by GitHub user pjfanning (triggered by pjfanning).
Head commit for run:
82991a5b2128270adbde1f2ed1e335443c596465 / PJ Fanning
mark stop() method as noinline
Report URL: https://github.com/apache/pekko/action
mdedetrich commented on issue #1484:
URL: https://github.com/apache/pekko/issues/1484#issuecomment-2355866077
To me this is acceptable as long as the number of methods we have to mark as
`@noinline` is reasonable (as a rough ballback I would say < 10) and that ontop
of this we also have a p
pjfanning opened a new pull request, #1486:
URL: https://github.com/apache/pekko/pull/1486
The complicated CI for Scala 3 which runs many separate compile and test
subjobs - while Scala 2 build is not like this at all - I think this might have
been useful when Scala 3 support was being adde
pjfanning opened a new pull request, #1485:
URL: https://github.com/apache/pekko/pull/1485
relates to #1484
I have similar issues in https://github.com/pjfanning/micrometer-pekko and
this change fixes the broken test I ran into there when upgrading to Pekko 1.1.
More changes w
The GitHub Actions job "Unit Tests" on pekko-projection.git has failed.
Run started by GitHub user pjfanning (triggered by pjfanning).
Head commit for run:
5327f9c7eaeda825e56dba9006bfada7cbfcbed2 / PJ Fanning
Update Dependencies.scala
Report URL: https://github.com/apache/pekko-projection/ac
The GitHub Actions job "Integration Tests for Kafka" on pekko-projection.git
has failed.
Run started by GitHub user pjfanning (triggered by pjfanning).
Head commit for run:
5327f9c7eaeda825e56dba9006bfada7cbfcbed2 / PJ Fanning
Update Dependencies.scala
Report URL: https://github.com/apache/p
The GitHub Actions job "Scalafmt" on pekko-projection.git has succeeded.
Run started by GitHub user pjfanning (triggered by pjfanning).
Head commit for run:
5327f9c7eaeda825e56dba9006bfada7cbfcbed2 / PJ Fanning
Update Dependencies.scala
Report URL: https://github.com/apache/pekko-projection/a
pjfanning closed pull request #203: Update pekko-actor-testkit-typed, ... to
1.1.0
URL: https://github.com/apache/pekko-projection/pull/203
--
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
The GitHub Actions job "Unit Tests" on pekko-projection.git has failed.
Run started by GitHub user pjfanning (triggered by pjfanning).
Head commit for run:
a20b1c191559767b6858acae214a37d8bf1ad439 / PJ Fanning
Update Dependencies.scala
Report URL: https://github.com/apache/pekko-projection/ac
The GitHub Actions job "Integration Tests for Kafka" on pekko-projection.git
has failed.
Run started by GitHub user pjfanning (triggered by pjfanning).
Head commit for run:
a20b1c191559767b6858acae214a37d8bf1ad439 / PJ Fanning
Update Dependencies.scala
Report URL: https://github.com/apache/p
The GitHub Actions job "Scalafmt" on pekko-projection.git has failed.
Run started by GitHub user pjfanning (triggered by pjfanning).
Head commit for run:
a20b1c191559767b6858acae214a37d8bf1ad439 / PJ Fanning
Update Dependencies.scala
Report URL: https://github.com/apache/pekko-projection/acti
GitHub user mdedetrich edited a comment on the discussion: Should we allow
'mixed versioning'?
> > By definition of semver patch bump's shouldn't add new functionality, only
> > fix anything thats currently there so on surface level this seems okay
>
> I don't know how strictly we plan to fol
GitHub user pjfanning added a comment to the discussion: Should we allow 'mixed
versioning'?
sbt plugin - https://github.com/heremaps/here-sbt-bom
GitHub link:
https://github.com/apache/pekko/discussions/1483#discussioncomment-10669383
This is an automatically sent email for notificatio
The GitHub Actions job "Unit Tests" on pekko-projection.git has failed.
Run started by GitHub user pjfanning (triggered by pjfanning).
Head commit for run:
f0c97965f0cd96b9136e15b45f64fdd549a20a25 / PJ Fanning
test with RC versions of connectors-kafka and persistence-jdbc
Report URL: https://
The GitHub Actions job "Integration Tests for Kafka" on pekko-projection.git
has failed.
Run started by GitHub user pjfanning (triggered by pjfanning).
Head commit for run:
f0c97965f0cd96b9136e15b45f64fdd549a20a25 / PJ Fanning
test with RC versions of connectors-kafka and persistence-jdbc
Re
GitHub user mdedetrich added a comment to the discussion: Should we allow
'mixed versioning'?
> > By definition of semver patch bump's shouldn't add new functionality, only
> > fix anything thats currently there so on surface level this seems okay
>
> I don't know how strictly we plan to foll
GitHub user pjfanning added a comment to the discussion: Seeking Information on
Enterprise Adoption of Pekko
I'll leave the discussion open for users to comment on their experience of
using Apache Pekko.
Many of our jars get 6 figure downloads per month - the totals across all jars
are well i
GitHub user raboof added a comment to the discussion: Should we allow 'mixed
versioning'?
> By definition of semver patch bump's shouldn't add new functionality, only
> fix anything thats currently there so on surface level this seems okay
I don't know how strictly we plan to follow semver. F
GitHub user raboof added a comment to the discussion: Should we allow 'mixed
versioning'?
> We have a config to disable the check. `pekko.fail-mixed-versions=off`
> I think Akka and existing Pekko users are used to check so I would prefer to
> keep some form of check - especially since it can
GitHub user mdedetrich edited a comment on the discussion: Should we allow
'mixed versioning'?
So firstly I would like to apologize for the chaos created, at work we are
currently using a snapshot version and then it suddenly stopped working when it
was bumped to the latest snapshot version a
GitHub user mdedetrich added a comment to the discussion: Should we allow
'mixed versioning'?
> We could also consider only comparing the major and minor parts the x.y.z
> version number but allow flexibility with the patch part of the version
> number ('z' in x.y.z).
By definition of semver
GitHub user mdedetrich added a comment to the discussion: Should we allow
'mixed versioning'?
So firstly I would like to apologize for the chaos created, at work we are
currently using a snapshot version and then it suddenly stopped working when it
was bumped to the latest version and so my i
GitHub user pjfanning edited a comment on the discussion: Should we allow
'mixed versioning'?
We have a config to disable the check. `pekko.fail-mixed-versions=off`
I think Akka and existing Pekko users are used to check so I would prefer to
keep some form of check - especially since it can be
GitHub user pjfanning added a comment to the discussion: Should we allow 'mixed
versioning'?
We have a config to disable the check. `pekko.fail-mixed-versions=off`
I think Akka and existing Pekko users are used to check so I would prefer to
keep some form of check - especially since it can be
GitHub user raboof edited a discussion: Should we allow 'mixed versioning'?
Currently, Pekko does not allow 'mixed versioning' - please read
https://pekko.apache.org/docs/pekko/current/common/binary-compatibility-rules.html#mixed-versioning-is-not-allowed
to get the background.
This is causin
raboof commented on PR #809:
URL: https://github.com/apache/pekko-connectors/pull/809#issuecomment-2355048788
> I won't release anything until we find the root cause of the version check
issues. I'll leave the votes open but will cancel them if we find that we need
big changes.
That
mdedetrich closed pull request #809: Set current version to latest 1.0.3
URL: https://github.com/apache/pekko-connectors/pull/809
--
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.
mdedetrich commented on PR #809:
URL: https://github.com/apache/pekko-connectors/pull/809#issuecomment-2355030315
Closing this PR, I will also cancel my -1 vote in the releases
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub a
pjfanning commented on PR #809:
URL: https://github.com/apache/pekko-connectors/pull/809#issuecomment-2355026373
> So this is the exact error that is being thrown in my project
>
> ```
> 2024-09-17 11:21:59.865 [Test worker] ERROR - Actor System error
> java.lang.IllegalStateExc
mdedetrich commented on PR #809:
URL: https://github.com/apache/pekko-connectors/pull/809#issuecomment-2355017515
So this is the exact error that is being thrown in my project
```
2024-09-17 11:21:59.865 [Test worker] ERROR - Actor System error
java.lang.IllegalStateException: Y
The GitHub Actions job "CI" on pekko-connectors.git has failed.
Run started by GitHub user mdedetrich (triggered by mdedetrich).
Head commit for run:
421f994e45d80138687d6fcb3dcd4fd7c772a623 / Matthew de Detrich
Set current version to latest 1.0.3
Report URL: https://github.com/apache/pekko-c
pjfanning commented on PR #809:
URL: https://github.com/apache/pekko-connectors/pull/809#issuecomment-2355002355
> I think @pjfanning is right in that we probably need to update the check.
We do need to cancel the current `-RC`'s for now since the jar's seem to be
broken
I won't rele
mdedetrich commented on PR #809:
URL: https://github.com/apache/pekko-connectors/pull/809#issuecomment-2354991006
> I'm OK with keeping the minimum pekko version in pekko-connectors on
1.0.3, but I thought we wanted pekko-connectors 1.1.x to require pekko 1.1.x to
get the benefits of inlini
mdedetrich commented on PR #809:
URL: https://github.com/apache/pekko-connectors/pull/809#issuecomment-2354987032
I think @pjfanning is right in that we probably need to update the check. We
do need to cancel the current `-RC`'s for now since the jar's seem to be broken
--
This is an auto
raboof commented on PR #809:
URL: https://github.com/apache/pekko-connectors/pull/809#issuecomment-2354983545
> If we use one of the "non working" versions such as
1.1.0-M1+65-53ed673e-SNAPSHOT but bump pekkVersion to 1.1.1 then it works
again, but the whole point is we are meant to be usin
mdedetrich commented on PR #809:
URL: https://github.com/apache/pekko-connectors/pull/809#issuecomment-2354980994
What specifically fails is `ActorSystem.create()` which throws an
`java.lang.IllegalStateException`, I think this is the relevant code
https://github.com/apache/pekko/blob/c839a
pjfanning commented on PR #809:
URL: https://github.com/apache/pekko-connectors/pull/809#issuecomment-2354973279
We are trying to do releases. And one aspect of the release is that Scala 2
inlining is enabled. This requires that we build with 1.1 jars from our various
modules.
I have
raboof commented on PR #809:
URL: https://github.com/apache/pekko-connectors/pull/809#issuecomment-2354969227
> In my work project I have this
>
> ```kotlin
> val pekkoVersion = "1.1.0"
> val pekkoConnectorsVersion = "1.1.0-M1+65-53ed673e-SNAPSHOT"
> ```
>
> where pekko
mdedetrich commented on PR #809:
URL: https://github.com/apache/pekko-connectors/pull/809#issuecomment-2354943489
> > then it would fail with class not found errors.
> > This is because Pekko is doing a check on the major/minor version
>
> I'm confused: is it failing with class not
raboof commented on PR #809:
URL: https://github.com/apache/pekko-connectors/pull/809#issuecomment-2354934164
> then it would fail with class not found errors.
> This is because Pekko is doing a check on the major/minor version
I'm confused: is it failing with class not found errors
mdedetrich opened a new pull request, #809:
URL: https://github.com/apache/pekko-connectors/pull/809
Currently the Pekko artifacts/snapshots are broken, here are the stats from
today
```
latest = 1.1.0-M1+65-53ed673e-SNAPSHOT (not working)
2 days = 1.1.0-M1+64-600516f4-SNAPSHOT
lrytz commented on PR #1474:
URL: https://github.com/apache/pekko/pull/1474#issuecomment-2354777352
👍 sorry I missed the scala3 ticket
--
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 specifi
79 matches
Mail list logo
