shakeeb-upstart commented on code in PR #313:
URL: https://github.com/apache/pekko-management/pull/313#discussion_r1776671278
##
discovery-kubernetes-api/src/main/scala/org/apache/pekko/discovery/kubernetes/KubernetesApiServiceDiscovery.scala:
##
@@ -96,13 +96,14 @@ object Kuber
shakeeb-upstart commented on code in PR #313:
URL: https://github.com/apache/pekko-management/pull/313#discussion_r1776671278
##
discovery-kubernetes-api/src/main/scala/org/apache/pekko/discovery/kubernetes/KubernetesApiServiceDiscovery.scala:
##
@@ -96,13 +96,14 @@ object Kuber
jtjeferreira commented on code in PR #832:
URL: https://github.com/apache/pekko-connectors/pull/832#discussion_r1776730932
##
.github/workflows/nightly-builds.yaml:
##
@@ -56,12 +57,14 @@ jobs:
- name: Cache Coursier cache
uses: coursier/cache-action@v6
-
The GitHub Actions job "Nightly Builds" on pekko-connectors.git has failed.
Run started by GitHub user pjfanning (triggered by pjfanning).
Head commit for run:
2622799d0da8ba172909d43869725950ceb7b5ce / PJ Fanning
temp enable run for related PR to test in CI
Report URL: https://github.com/apa
jtjeferreira commented on PR #832:
URL: https://github.com/apache/pekko-connectors/pull/832#issuecomment-2376493432
@pjfanning thanks for running the workflows. For some reason the secret is
not being properly propagated.
If I look into
https://github.com/apache/pekko-connectors/act
The GitHub Actions job "Nightly Builds" on pekko-connectors.git has failed.
Run started by GitHub user jtjeferreira (triggered by pjfanning).
Head commit for run:
3f8341641dfe17f7603902f03d7f026b115de072 / João Ferreira
Update .github/workflows/nightly-builds.yaml
Report URL: https://github.c
GitHub user raboof added a comment to the discussion: Recommendations for Pekko
Connectors Deployment
AFAIK we don't have any particular recommendations for deploying Pekko-based
applications.
The simplest solution is to deploy as a single node: that way you don't have to
worry about cluster
pjfanning commented on PR #832:
URL: https://github.com/apache/pekko-connectors/pull/832#issuecomment-2376540120
It looks like there are possibly some restrictions set up so that the access
key secret can not be used as an env variable. I'll raise an issue with the ASF
Infra team to see if
The GitHub Actions job "Nightly Builds" on pekko-connectors.git has failed.
Run started by GitHub user pjfanning (triggered by pjfanning).
Head commit for run:
e881f6091f54fd68b6cfd0167eec43a57d0b1535 / PJ Fanning
try AWS_SECRET_ACCESS_KEY
Report URL: https://github.com/apache/pekko-connector
pjfanning commented on code in PR #827:
URL: https://github.com/apache/pekko-connectors/pull/827#discussion_r1776812652
##
aws-spi-pekko-http/src/main/scala/org/apache/pekko/stream/connectors/awsspi/PekkoHttpClient.scala:
##
@@ -179,6 +201,12 @@ object PekkoHttpClient {
c
jtjeferreira commented on PR #832:
URL: https://github.com/apache/pekko-connectors/pull/832#issuecomment-2376599546
@pjfanning I reverted all my changes to make sure the secrets can be
accessed in a PR. If it works, I will progress from there...
--
This is an automated message from the Ap
pjfanning commented on PR #832:
URL: https://github.com/apache/pekko-connectors/pull/832#issuecomment-2376634698
The ASF Infra team answered and said that GitHub forks of the main project
don't have access to the secrets.
In theory, I could create a branch on the main project and crea
jtjeferreira commented on PR #832:
URL: https://github.com/apache/pekko-connectors/pull/832#issuecomment-2376625275
> @pjfanning I reverted all my changes to make sure the secrets can be
accessed in a PR. If it works, I will progress from there...
As I suspected [the secrets cannot be
pjfanning commented on PR #832:
URL: https://github.com/apache/pekko-connectors/pull/832#issuecomment-2376625706
@jtjeferreira looks like you were right - the secrets seem not to work when
you are building for a CI
Do you want to remove all the changes and add back the env vars? I can
pjfanning opened a new pull request, #833:
URL: https://github.com/apache/pekko-connectors/pull/833
see #832
not yet for merge - contains some build hacks to test the changes in a PR
--
This is an automated message from the Apache Git Service.
To respond to the message, please log
pjfanning commented on PR #314:
URL: https://github.com/apache/pekko-management/pull/314#issuecomment-2377307038
I'll merge the original change that just doubles the time on the patience
config in this test class.
--
This is an automated message from the Apache Git Service.
To respond to
pjfanning merged PR #314:
URL: https://github.com/apache/pekko-management/pull/314
--
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-unsubsc
ner.DefaultV4RequestSigner --
AWS4 String to sign: AWS4-HMAC-SHA256
20240926T111905Z
20240926/eu-west-1/dynamodb/aws4_request
00eb4abdc6c6fa63da2629838508f91450af660b2c64c86842af93179d6611b6
11:19:05.882 [pool-6-thread-5-ScalaTest-running-SQSITTest] DEBUG
software.amazon.awssdk.http.auth.a
raboof commented on PR #313:
URL: https://github.com/apache/pekko-management/pull/313#issuecomment-2376878236
@Roiocam did you want to do a re-review or are we OK to (Squash and) merge?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to
pjfanning opened a new pull request, #314:
URL: https://github.com/apache/pekko-management/pull/314
see #216
--
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
pjfanning merged PR #827:
URL: https://github.com/apache/pekko-connectors/pull/827
--
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-unsubsc
pjfanning commented on PR #829:
URL: https://github.com/apache/pekko-connectors/pull/829#issuecomment-2376896085
@jtjeferreira I merged #827 - can you rebase this and get it ready for
merging?
--
This is an automated message from the Apache Git Service.
To respond to the message, please l
The GitHub Actions job "Unit Tests" on pekko-management.git has failed.
Run started by GitHub user pjfanning (triggered by pjfanning).
Head commit for run:
b1c94aabc34c2d549930ab266c010f541d2262a4 / PJ Fanning
add pekko.test.timefactor
Report URL: https://github.com/apache/pekko-management/ac
The GitHub Actions job "Unit Tests" on pekko-management.git has failed.
Run started by GitHub user pjfanning (triggered by pjfanning).
Head commit for run:
635dba8623bf825ef4aba79a5eb1d0209a943675 / PJ Fanning
try to fix workflows
Report URL: https://github.com/apache/pekko-management/actions
pjfanning commented on PR #314:
URL: https://github.com/apache/pekko-management/pull/314#issuecomment-2377000933
The same flaky test failed even with the timefactor=2 - but the timefactor
didn't seem to increase the timeout - it still looks like the same same short
1.5 second timeout.
raboof commented on PR #314:
URL: https://github.com/apache/pekko-management/pull/314#issuecomment-2377010048
hmm, maybe because this test *explicitly* sets it to
`testKitSettings.DefaultTimeout.duration`? What happens when we remove that?
sorry for leading you down this rabbit hole :/
--
mdedetrich commented on issue #655:
URL:
https://github.com/apache/pekko-connectors/issues/655#issuecomment-2377069861
Need to work with ASF infra to give the necessary permissions to do these
tests.
They also will not work on PR's, instead the tests will only work on a
GitHub branc
pjfanning commented on issue #655:
URL:
https://github.com/apache/pekko-connectors/issues/655#issuecomment-2377090745
I think we will need to consider making changes to the tests so that the
created resources are more deterministic (name wise) and that the tests clean
up after themselves i
pjfanning commented on PR #314:
URL: https://github.com/apache/pekko-management/pull/314#issuecomment-2377103761
Without the explicit patience config, things get far worse. All the
individual scenarios timeout in 150ms.
--
This is an automated message from the Apache Git Service.
To respo
shakeeb-upstart commented on code in PR #313:
URL: https://github.com/apache/pekko-management/pull/313#discussion_r1776980888
##
discovery-kubernetes-api/src/main/scala/org/apache/pekko/discovery/kubernetes/KubernetesApiServiceDiscovery.scala:
##
@@ -96,13 +96,14 @@ object Kuber
pjfanning commented on PR #833:
URL: https://github.com/apache/pekko-connectors/pull/833#issuecomment-2376826818
> > The KinesisITTest fails because we don't have the specific AWS
permissions to create the Kinesis resources needed for that test.
>
> Can you take care of that?
I
pjfanning commented on PR #313:
URL: https://github.com/apache/pekko-management/pull/313#issuecomment-2376842429
I'm ok with merging this if other reviewers are happy to proceed.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub
The GitHub Actions job "Unit Tests" on pekko-management.git has failed.
Run started by GitHub user shakeeb-upstart (triggered by pjfanning).
Head commit for run:
d3c83f0046cfb7aceed69ab1493a34c91aff9f5a / HP
- refactored code
Report URL: https://github.com/apache/pekko-management/actions/runs
jtjeferreira commented on PR #830:
URL: https://github.com/apache/pekko-connectors/pull/830#issuecomment-2377141976
By comparing the logs of `list streams` test with `list streams in
parallel`, I noticed these log lines:
✅
```
[org.apache.pekko.stream.Log(pekko://aws-pekko-http
pjfanning commented on PR #830:
URL: https://github.com/apache/pekko-connectors/pull/830#issuecomment-2377170776
Is it possible to also support HTTP 1.1? It might be a nice option to be
able to use a HTTP 1.1 client if there are issues with the HTTP/2 one.
--
This is an automated message
raboof commented on code in PR #313:
URL: https://github.com/apache/pekko-management/pull/313#discussion_r1776874701
##
discovery-kubernetes-api/src/main/scala/org/apache/pekko/discovery/kubernetes/KubernetesApiServiceDiscovery.scala:
##
@@ -96,13 +96,14 @@ object KubernetesApiS
pjfanning commented on code in PR #313:
URL: https://github.com/apache/pekko-management/pull/313#discussion_r1776880456
##
discovery-kubernetes-api/src/main/scala/org/apache/pekko/discovery/kubernetes/KubernetesApiServiceDiscovery.scala:
##
@@ -96,13 +96,14 @@ object KubernetesA
The GitHub Actions job "Nightly Builds" on pekko-connectors.git has failed.
Run started by GitHub user pjfanning (triggered by pjfanning).
Head commit for run:
91b17feb6f692db700894d17bcf7e26f6f7b6b44 / PJ Fanning
use env variables for AWS creds
Report URL: https://github.com/apache/pekko-con
pjfanning commented on code in PR #313:
URL: https://github.com/apache/pekko-management/pull/313#discussion_r1776880456
##
discovery-kubernetes-api/src/main/scala/org/apache/pekko/discovery/kubernetes/KubernetesApiServiceDiscovery.scala:
##
@@ -96,13 +96,14 @@ object KubernetesA
pjfanning commented on PR #833:
URL: https://github.com/apache/pekko-connectors/pull/833#issuecomment-2376667876
@jtjeferreira the tests have access to the the AWS creds in this PR
The KinesisITTest fails because we don't have the specific AWS permissions
to create the Kinesis resourc
jtjeferreira commented on PR #833:
URL: https://github.com/apache/pekko-connectors/pull/833#issuecomment-2376781848
> The KinesisITTest fails because we don't have the specific AWS permissions
to create the Kinesis resources needed for that test.
Can you take care of that?
-
raboof commented on PR #313:
URL: https://github.com/apache/pekko-management/pull/313#issuecomment-2376854245
(failure is #216 again)
--
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
The GitHub Actions job "Unit Tests" on pekko-management.git has succeeded.
Run started by GitHub user shakeeb-upstart (triggered by pjfanning).
Head commit for run:
d3c83f0046cfb7aceed69ab1493a34c91aff9f5a / HP
- refactored code
Report URL: https://github.com/apache/pekko-management/actions/r
jtjeferreira commented on PR #833:
URL: https://github.com/apache/pekko-connectors/pull/833#issuecomment-2377029832
> Is there any chance that we could start with using localstack or something
like that to test with an AWS-like setup for our Kinesis related testing?
I was gonna say th
jtjeferreira commented on PR #827:
URL: https://github.com/apache/pekko-connectors/pull/827#issuecomment-2377034077
> I'll take a look at this when I get back from vacation on Sunday
I think @mdedetrich wanted to do a review. Feel free to comment here, and I
can create a PR to address
The GitHub Actions job "Unit Tests" on pekko-management.git has failed.
Run started by GitHub user pjfanning (triggered by pjfanning).
Head commit for run:
b28ac0e1de65a91c31db773dd11f6d002d401869 / PJ Fanning
remove explicit PatienceConfig
Report URL: https://github.com/apache/pekko-manageme
jtjeferreira commented on issue #655:
URL:
https://github.com/apache/pekko-connectors/issues/655#issuecomment-2377062959
The important bits are `User:
arn:aws:iam::534396592182:user/pekko-connectors is not authorized to perform:
XXX on resource: YYY`:
* `dynamodb:CreateTable` on resourc
The GitHub Actions job "Unit Tests" on pekko-management.git has succeeded.
Run started by GitHub user pjfanning (triggered by pjfanning).
Head commit for run:
66bccd8295d963919c37b37308797bd88d7768cd / PJ Fanning
double timeout on flaky test
Report URL: https://github.com/apache/pekko-managem
jtjeferreira commented on PR #830:
URL: https://github.com/apache/pekko-connectors/pull/830#issuecomment-2377269498
> Is it possible to also support HTTP 1.1? It might be a nice option to be
able to use a HTTP 1.1 client if there are issues with the HTTP/2 one.
Yes, HTTP 1.1 is suppor
The GitHub Actions job "Nightly Builds" on pekko-connectors.git has succeeded.
Run started by GitHub user He-Pin (triggered by He-Pin).
Head commit for run:
3cb1ed8c479405cc94a758bee3edd694fb8ec45b / João Ferreira
Allow using SdkHttpConfigurationOption over default pekko-http connection
setti
The GitHub Actions job "Publish" on pekko-persistence-cassandra.git has
succeeded.
Run started by GitHub user nvollmar (triggered by nvollmar).
Head commit for run:
550c10d709b5634cb829d8831ebcc60f068d4910 / PJ Fanning
sbt 1.10.2 (#229)
Report URL:
https://github.com/apache/pekko-persistenc
The GitHub Actions job "Publish 1.0 Nightly" on pekko-persistence-jdbc.git has
succeeded.
Run started by GitHub user pjfanning (triggered by pjfanning).
Head commit for run:
cafc1e915bd1f7fb6da961ea48443496af2ebb4e / PJ Fanning
Sbt 1.10.2 (#232)
* sbt 1.10.2
* Update build.properties
Repor
The GitHub Actions job "Publish nightly 1.0 snapshots" on pekko.git has
succeeded.
Run started by GitHub user pjfanning (triggered by pjfanning).
Head commit for run:
f24e43687b4e88e43d19e031e87eba3e700b5182 / PJ Fanning
mark stop() method as noinline (#1485)
* mark stop() method as noinline
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:
971f007e436031e6c20c3dc845efbc5a748d3aeb / PJ Fanning
Update protoc to 3.25.5
Report URL: https://github.com/apache/pekko-projection/acti
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:
971f007e436031e6c20c3dc845efbc5a748d3aeb / PJ Fanning
Update protoc to 3.25.5
Report URL: https://github.com/apache/pekko-projection/a
pjfanning opened a new pull request, #210:
URL: https://github.com/apache/pekko-projection/pull/210
We have updated to protobuf-java 3.25.5 - seems useful to keep protoc in
sync.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHu
The GitHub Actions job "Run Tests with Pekko 1.0.x builds" on
pekko-persistence-cassandra.git has failed.
Run started by GitHub user pjfanning (triggered by pjfanning).
Head commit for run:
550c10d709b5634cb829d8831ebcc60f068d4910 / PJ Fanning
sbt 1.10.2 (#229)
Report URL:
https://github.co
The GitHub Actions job "Unit Tests" on pekko-persistence-cassandra.git has
succeeded.
Run started by GitHub user mdedetrich (triggered by mdedetrich).
Head commit for run:
550c10d709b5634cb829d8831ebcc60f068d4910 / PJ Fanning
sbt 1.10.2 (#229)
Report URL:
https://github.com/apache/pekko-per
58 matches
Mail list logo
