pjfanning commented on issue #1798:
URL: https://github.com/apache/pekko/issues/1798#issuecomment-2734674395
@ptrdom Would you be able to provide a little more detail on which parts of
the 194 PR that you think should be copied into this repo?
--
This is an automated message from the Apac
pjfanning commented on PR #1756:
URL: https://github.com/apache/pekko/pull/1756#issuecomment-2733154487
@mkurz as an example, we would intend not to release a version of pekko-http
that requires pekko 1.2. The idea is that pekko 1.2 is very compatible with
pekko 1.1 but has a few new featur
mkurz commented on PR #1756:
URL: https://github.com/apache/pekko/pull/1756#issuecomment-2733134690
> Unless you are waiting on a particular fix, then best to stick with 1.1.
Is there a particular feature of 1.2 that you need?
No, just asking, because I plan to push for a new Play rel
jypma opened a new pull request, #1802:
URL: https://github.com/apache/pekko/pull/1802
This commit introduces Task, a data structure that represents a recipe, or
program, for producing a value of type T (or failing with an exception). It is
similar in semantics to RunnableGraph[T], but inte
mkurz commented on PR #1756:
URL: https://github.com/apache/pekko/pull/1756#issuecomment-2733063842
Is there an ETA for 1.2 final?
--
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
pjfanning commented on PR #1756:
URL: https://github.com/apache/pekko/pull/1756#issuecomment-2733105946
> Is there an ETA for 1.2 final?
Unless you are waiting on a particular fix, then best to stick with 1.1. Is
there a particular feature of 1.2 that you need?
--
This is an automa
mkurz commented on PR #1756:
URL: https://github.com/apache/pekko/pull/1756#issuecomment-2733197203
I am not pressuring, just wanted to know what the status quo of 1.2 is.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and us
mkurz commented on PR #1756:
URL: https://github.com/apache/pekko/pull/1756#issuecomment-2733193954
> Is there any interest in dealing with the Jackson upgrade in play-json and
play?
It's on the roadmap btw: https://github.com/orgs/playframework/projects/3
--
This is an automated m
jypma commented on issue #1801:
URL: https://github.com/apache/pekko/issues/1801#issuecomment-2732643320
First shot at a direction is in https://github.com/apache/pekko/pull/1802 .
The cancellation of schedulers might not be that relevant (yet). The callbacks
for `Task` should really run di
mkurz commented on PR #1756:
URL: https://github.com/apache/pekko/pull/1756#issuecomment-2733189625
> Is there any interest in dealing with the Jackson upgrade in play-json and
play?
Yes, Jackson will be upgraded to latest 2.18.x in the next days/weeks. I am
fully aware of the open p
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:
d416b2b5bd19842a61b7815663e11f081dfb0f84 / scala-steward-asf[bot]
<147768647+scala-steward-asf[bot]@users.noreply.git
pjfanning commented on code in PR #1802:
URL: https://github.com/apache/pekko/pull/1802#discussion_r2000741625
##
stream/src/main/java/org/apache/pekko/task/javadsl/Fiber.java:
##
@@ -0,0 +1,22 @@
+package org.apache.pekko.task.javadsl;
Review Comment:
new source files need
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:
d416b2b5bd19842a61b7815663e11f081dfb0f84 / scala-steward-asf[bot]
<147768647+scala-steward-asf[bot]@users.noreply.github
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>
ptrdom commented on issue #1798:
URL: https://github.com/apache/pekko/issues/1798#issuecomment-2734697540
I think nothing will need to be copied into this repo from 194 PR, just that
once this repo implements necessary changes for plugin interface then users
will be able to use the plugin i
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
dependabot[bot] commented on PR #1789:
URL: https://github.com/apache/pekko/pull/1789#issuecomment-2735038842
Superseded by #1803.
--
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
dependabot[bot] opened a new pull request, #1803:
URL: https://github.com/apache/pekko/pull/1803
Bumps
[VirtusLab/scala-cli-setup](https://github.com/virtuslab/scala-cli-setup) from
1.5.4 to 1.7.1.
Release notes
Sourced from https://github.com/virtuslab/scala-cli-setup/releases";>
dependabot[bot] closed pull request #1789: chore(deps): bump
VirtusLab/scala-cli-setup from 1.5.4 to 1.7.0
URL: https://github.com/apache/pekko/pull/1789
--
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
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:
9b1f82319d830d1ecbc96bd7e8fdf3dda198681b / scala-steward-asf[bot]
<147768647+scala-steward-asf[bot]@users.noreply.github.com>
Update junit-j
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.
21 matches
Mail list logo
