mdedetrich commented on issue #656:
URL:
https://github.com/apache/pekko-connectors/issues/656#issuecomment-2792072885
So I actually ran the test suite against a proper GCS account and I can
confirm that the current tests actually don't work, they seem to have either
been improperly implem
mdedetrich commented on PR #1033:
URL:
https://github.com/apache/pekko-connectors/pull/1033#issuecomment-2792217763
> > I have a few more bug fixes for 1.1.x so shall we merge this after those
bug fixes land?
>
> maybe - all the same, I'd be as happy to just get everything into a 1.2
mdedetrich commented on PR #1021:
URL:
https://github.com/apache/pekko-connectors/pull/1021#issuecomment-279703
Im putting this into draft mode as there is actually a legitimate use for an
auth method that is just project-id+token, its just that calling this
authentication method `none
pjfanning commented on PR #1033:
URL:
https://github.com/apache/pekko-connectors/pull/1033#issuecomment-2792233405
I'm not sure that a big refactor of the repo and splitting it into sub-repos
is a 1.x.y task - seems more like a major release task.
--
This is an automated message from the
mdedetrich commented on PR #1033:
URL:
https://github.com/apache/pekko-connectors/pull/1033#issuecomment-2792175651
I have a few more bug fixes for 1.1.x so shall we merge this after those
bug fixes land?
--
This is an automated message from the Apache Git Service.
To respond to the mes
pjfanning commented on code in PR #1033:
URL: https://github.com/apache/pekko-connectors/pull/1033#discussion_r2036954909
##
.github/workflows/nightly-builds.yaml:
##
@@ -28,22 +28,6 @@ jobs:
test-compile:
name: Compile
runs-on: ubuntu-22.04
-# Licensed to the A
mdedetrich commented on PR #1033:
URL:
https://github.com/apache/pekko-connectors/pull/1033#issuecomment-2792250567
> I'm not sure that a big refactor of the repo and splitting it into
sub-repos is a 1.x.y task - seems more like a major release task.
I made a discussion for this at
GitHub user mdedetrich edited a discussion: Split out google connectors into
its own repo
So due to the fact that I have started working on google cloud storage and
there will be feature/behaviour changes which asks for a 1.2.x release I was
wondering whether it makes sense to start our journ
mdedetrich opened a new pull request, #1032:
URL: https://github.com/apache/pekko-connectors/pull/1032
This as as per instructions at
https://github.com/apache/pekko-connectors/blob/7b5878e46ee76b39619b92b1175e1af40af0eccf/google-cloud-storage/src/test/scala/org/apache/pekko/stream/connector
mdedetrich merged PR #1032:
URL: https://github.com/apache/pekko-connectors/pull/1032
--
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
GitHub user raboof added a comment to the discussion: Split out google
connectors into its own repo
I'm not opposed to this change. One consideration is that this means these
components will have their own release/vote cycle, right? That might be
challenging as it's already sometimes difficul
GitHub user mdedetrich added a comment to the discussion: Split out google
connectors into its own repo
> I'm not opposed to this change. One consideration is that this means these
> components will have their own release/vote cycle, right?
Yes that is the main point actually, I want to avoid
The GitHub Actions job "Publish 1.0 Nightly" on pekko-persistence-jdbc.git/main
has succeeded.
Run started by GitHub user pjfanning (triggered by pjfanning).
Head commit for run:
1cc5c27dd55f5d2c7b820e67634a830b6bde66c3 / Patrick Stadler
fix: postgres durable state schemaName change leads to
pjfanning commented on PR #1033:
URL:
https://github.com/apache/pekko-connectors/pull/1033#issuecomment-2792182560
> I have a few more bug fixes for 1.1.x so shall we merge this after those
bug fixes land?
maybe - all the same, I'd be as happy to just get everything into a 1.2.0
rel
The GitHub Actions job "Nightly Builds" on pekko-http.git/main has failed.
Run started by GitHub user He-Pin (triggered by He-Pin).
Head commit for run:
d1bedc7168c75c3727dc1a1573a5b3b7d2ce7dfe / scala-steward-asf[bot]
<147768647+scala-steward-asf[bot]@users.noreply.github.com>
Update sbt, scri
The GitHub Actions job "Scalafmt" on pekko.git/jyp-task has failed.
Run started by GitHub user jypma (triggered by pjfanning).
Head commit for run:
c0d45846c7b58f41d62145a8cbbb6daffc834ebe / Jan Ypma
Introduce Task monad
This commit introduces Task, a data structure that represents a
recipe, o
The GitHub Actions job "Pull Requests" on pekko.git/jyp-task has failed.
Run started by GitHub user jypma (triggered by pjfanning).
Head commit for run:
c0d45846c7b58f41d62145a8cbbb6daffc834ebe / Jan Ypma
Introduce Task monad
This commit introduces Task, a data structure that represents a
reci
pjfanning commented on PR #1795:
URL: https://github.com/apache/pekko/pull/1795#issuecomment-2794752578
> > I checked
https://github.com/grpc/grpc-java/blob/master/examples/pom.xml, I think we
should keep using protobuf 3.x in 1.2.0
>
> This is covered in [#1795
(comment)](https://g
The GitHub Actions job "Nightly Aeron Tests" on pekko.git/main has failed.
Run started by GitHub user jrudolph (triggered by jrudolph).
Head commit for run:
3d4893137b389f6521565b50bc3c793738afdcc5 / scala-steward-asf[bot]
<147768647+scala-steward-asf[bot]@users.noreply.github.com>
Update docke
The GitHub Actions job "Nightly Builds (1.1)" on pekko.git/main has succeeded.
Run started by GitHub user pjfanning (triggered by pjfanning).
Head commit for run:
3d4893137b389f6521565b50bc3c793738afdcc5 / scala-steward-asf[bot]
<147768647+scala-steward-asf[bot]@users.noreply.github.com>
Update
The GitHub Actions job "Nightly Builds" on pekko.git/main has succeeded.
Run started by GitHub user pjfanning (triggered by pjfanning).
Head commit for run:
3d4893137b389f6521565b50bc3c793738afdcc5 / scala-steward-asf[bot]
<147768647+scala-steward-asf[bot]@users.noreply.github.com>
Update docke
The GitHub Actions job "Nightly Tests (Pekko 1.0.x)" on
pekko-persistence-r2dbc.git/main has failed.
Run started by GitHub user pjfanning (triggered by pjfanning).
Head commit for run:
7e8129410c8fc4106020bab0e23de93d1ed71348 / scala-steward-asf[bot]
<147768647+scala-steward-asf[bot]@users.nor
The GitHub Actions job "Unit Tests" on pekko-persistence-cassandra.git/main has
succeeded.
Run started by GitHub user mdedetrich (triggered by mdedetrich).
Head commit for run:
76736ff8553903d3d3b592d4fd7b29892d47d2d5 / scala-steward-asf[bot]
<147768647+scala-steward-asf[bot]@users.noreply.git
The GitHub Actions job "Nightly Tests" on pekko-management.git/main has
succeeded.
Run started by GitHub user pjfanning (triggered by pjfanning).
Head commit for run:
53281f9c5d608bc3225658f804b8df41a238629a / scala-steward-asf[bot]
<147768647+scala-steward-asf[bot]@users.noreply.github.com>
U
pjfanning opened a new pull request, #1033:
URL: https://github.com/apache/pekko-connectors/pull/1033
relates to discussion about 1.2.0 release in #1021
--
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
The GitHub Actions job "Nightly Build and Test" on
pekko-connectors-kafka.git/main has failed.
Run started by GitHub user pjfanning (triggered by pjfanning).
Head commit for run:
6ee7684055961d4c5ae3808102361f8c44cb2baf / PJ Fanning
add testcontainers ref to license (#302)
Report URL:
https
The GitHub Actions job "Run Tests with Pekko 1.0.x builds" on
pekko-persistence-cassandra.git/main has succeeded.
Run started by GitHub user pjfanning (triggered by pjfanning).
Head commit for run:
76736ff8553903d3d3b592d4fd7b29892d47d2d5 / scala-steward-asf[bot]
<147768647+scala-steward-asf[b
27 matches
Mail list logo
