pjfanning opened a new pull request, #474:
URL: https://github.com/apache/incubator-pekko-http/pull/474
(no comment)
--
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 unsu
pjfanning merged PR #471:
URL: https://github.com/apache/incubator-pekko-http/pull/471
--
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-uns
pjfanning merged PR #472:
URL: https://github.com/apache/incubator-pekko-http/pull/472
--
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-uns
pjfanning merged PR #84:
URL: https://github.com/apache/incubator-pekko-site/pull/84
--
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-unsub
mdedetrich commented on PR #44:
URL:
https://github.com/apache/incubator-pekko-persistence-jdbc/pull/44#issuecomment-1935076874
Update to Slick 3.5.0-RC1
--
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 t
mdedetrich commented on PR #459:
URL:
https://github.com/apache/incubator-pekko-connectors/pull/459#issuecomment-1935018039
@raboof Feel free to merge the PR when you want
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and u
mdedetrich commented on PR #106:
URL:
https://github.com/apache/incubator-pekko-persistence-jdbc/pull/106#issuecomment-1934977314
@pjfanning I would set this for 1.1.x since its a behaviour change, wdyt?
--
This is an automated message from the Apache Git Service.
To respond to the messag
wjohnsonbynder commented on PR #106:
URL:
https://github.com/apache/incubator-pekko-persistence-jdbc/pull/106#issuecomment-1934908566
I think some dbs handle Orderby in a subquery by optimizing them out. Moved
the orderby to the main query.
--
This is an automated message from the Apache
pjfanning opened a new pull request, #227:
URL: https://github.com/apache/incubator-pekko-grpc/pull/227
(no comment)
--
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 unsu
pjfanning opened a new pull request, #461:
URL: https://github.com/apache/incubator-pekko-connectors/pull/461
(no comment)
--
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.
T
pjfanning opened a new pull request, #85:
URL: https://github.com/apache/incubator-pekko-site/pull/85
(no comment)
--
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 unsubs
pjfanning opened a new pull request, #84:
URL: https://github.com/apache/incubator-pekko-site/pull/84
(no comment)
--
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 unsubs
pjfanning commented on PR #471:
URL:
https://github.com/apache/incubator-pekko-http/pull/471#issuecomment-1934805154
Hi everyone - I'd like to get the docs published for v1.0.1 before
announcing the release.
--
This is an automated message from the Apache Git Service.
To respond to the m
pjfanning commented on PR #472:
URL:
https://github.com/apache/incubator-pekko-http/pull/472#issuecomment-1934804636
Hi everyone - I'd like to get the docs published for v1.0.1 before
announcing the release.
--
This is an automated message from the Apache Git Service.
To respond to the m
wjohnsonbynder commented on issue #105:
URL:
https://github.com/apache/incubator-pekko-persistence-jdbc/issues/105#issuecomment-1934521848
Not sure I understand.
This subquery currently has nothing on the where clause other than deleted =
false
select "deleted" as x4, "meta_se
Roiocam commented on issue #105:
URL:
https://github.com/apache/incubator-pekko-persistence-jdbc/issues/105#issuecomment-1934507227
> Should I go ahead and make a PR?
Thanks for those verifications again, the reason why join before the offset
windows, is because these queries always
pjfanning commented on issue #105:
URL:
https://github.com/apache/incubator-pekko-persistence-jdbc/issues/105#issuecomment-1934486708
Could you give us a PR with your changes? We don't necessarily need
performance tests. Someone else might be able to perf test.
--
This is an automated me
wjohnsonbynder commented on issue #105:
URL:
https://github.com/apache/incubator-pekko-persistence-jdbc/issues/105#issuecomment-1934416212
A bit out of my depth with for the project but I messed around with the
following test with both the existing code and my fix.
Run locally
https:
Roiocam commented on PR #105:
URL:
https://github.com/apache/incubator-pekko-projection/pull/105#issuecomment-1934414814
@raboof Could you please do a code review? Thanks.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and u
raboof commented on PR #460:
URL:
https://github.com/apache/incubator-pekko-connectors/pull/460#issuecomment-1934409696
(ran the tests a few times, they now succeeded each time, I think this
sufficiently suggests those two PRs fix the main flakiness)
--
This is an automated message from
raboof closed pull request #460: mqtt-streaming: test two fixes for flaky tests
URL: https://github.com/apache/incubator-pekko-connectors/pull/460
--
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
Roiocam commented on PR #105:
URL:
https://github.com/apache/incubator-pekko-projection/pull/105#issuecomment-1934409391
After four times CI checks(see:
https://github.com/apache/incubator-pekko-projection/actions/runs/7831923269),
this kind of test has been successfully passed, and we sho
Roiocam opened a new issue, #106:
URL: https://github.com/apache/incubator-pekko-projection/issues/106
This test appears to be flaky:
```
<-- [org.apache.pekko.projection.ProjectionBehaviorSpec: A
ProjectionBehavior must work with ProjectionManagement extension] End of log
message
Roiocam opened a new pull request, #105:
URL: https://github.com/apache/incubator-pekko-projection/pull/105
Trying to solve #103, I am very doubtful that KafakConsumer will not be
consumed evenly from two partitions.
--
This is an automated message from the Apache Git Service.
To respond
raboof closed pull request #455: Diagnose #454
URL: https://github.com/apache/incubator-pekko-connectors/pull/455
--
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
Roiocam commented on issue #105:
URL:
https://github.com/apache/incubator-pekko-persistence-jdbc/issues/105#issuecomment-1934285257
Thanks @wjohnsonbynder for the reporting. If you were interested in creating
a PR, you could start by adding a perf unit test on:
https://github.com/apache/in
pjfanning commented on issue #105:
URL:
https://github.com/apache/incubator-pekko-persistence-jdbc/issues/105#issuecomment-1934266800
Thanks @wjohnsonbynder for the detailed analysis.
Would you be interested in creating a PR? We have a fairly limited number of
regular contributors.
raboof opened a new pull request, #460:
URL: https://github.com/apache/incubator-pekko-connectors/pull/460
this PR combines #456 and #459 to see if CI agrees they are now fixed. Not
for merge, merge them both separately.
--
This is an automated message from the Apache Git Service.
To resp
raboof opened a new pull request, #459:
URL: https://github.com/apache/incubator-pekko-connectors/pull/459
Previously, in this test, the server sent a 'publish' concurrent to the
client sending the 'ack' for that publish. This fix makes sure the 'ack' is
sent only after observing the 'publi
wjohnsonbynder opened a new issue, #105:
URL: https://github.com/apache/incubator-pekko-persistence-jdbc/issues/105
The eventsByTag query is very slow because of a subquery and the incorrect
placement of the where clause.
Dumped from our logs
select x2.x3, x2.x4, x2.x5, x2.x6,
raboof opened a new issue, #458:
URL: https://github.com/apache/incubator-pekko-connectors/issues/458
Seems flaky:
```
[info] MqttSessionSpec:
[info] MQTT client connector
[info] - should flow through a client session (56 milliseconds)
[info] - should Connect and carry thro
raboof opened a new pull request, #456:
URL: https://github.com/apache/incubator-pekko-connectors/pull/456
It appears the flakiness was caused by the two connections using the same
connection id for different connections in the same session. I'm not intimately
familiar with this codebase, b
mdedetrich commented on issue #454:
URL:
https://github.com/apache/incubator-pekko-connectors/issues/454#issuecomment-1933822777
> We've reached a point where this test hardly ever passes in CI build
Indeed, it used by ~1 in 30 would pass but I think its closer to 1 in 100
(if that)
pjfanning merged PR #440:
URL: https://github.com/apache/incubator-pekko-connectors/pull/440
--
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: notificatio
mdedetrich commented on PR #224:
URL:
https://github.com/apache/incubator-pekko-grpc/pull/224#issuecomment-1933784371
> Do we expect this to be an exceptional situation or something that happens
regularly? If the former, we should add an issue to remind us to remove the
workaround after th
pjfanning opened a new pull request, #226:
URL: https://github.com/apache/incubator-pekko-grpc/pull/226
(no comment)
--
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 unsu
pjfanning commented on PR #190:
URL:
https://github.com/apache/incubator-pekko-grpc/pull/190#issuecomment-1933772173
superceded by #222
--
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 speci
pjfanning closed pull request #190: [DRAFT] io.grpc 1.59
URL: https://github.com/apache/incubator-pekko-grpc/pull/190
--
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 unsubsc
raboof opened a new pull request, #455:
URL: https://github.com/apache/incubator-pekko-connectors/pull/455
Not for merge, but to diagnose the failure as it does not fail for me
locally yet
--
This is an automated message from the Apache Git Service.
To respond to the message, please log o
pjfanning merged PR #361:
URL: https://github.com/apache/incubator-pekko-connectors/pull/361
--
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: notificatio
pjfanning commented on PR #361:
URL:
https://github.com/apache/incubator-pekko-connectors/pull/361#issuecomment-1933693564
Release Note: OrientDB lib upgrade works with OrientDB 3.2 servers but
appears to cause issues when testing with OrientDB 3.1 servers. Users should
stick pekko-connect
pjfanning commented on issue #454:
URL:
https://github.com/apache/incubator-pekko-connectors/issues/454#issuecomment-1933671789
We've reached a point where this test hardly ever passes in CI build
--
This is an automated message from the Apache Git Service.
To respond to the message, plea
pjfanning merged PR #452:
URL: https://github.com/apache/incubator-pekko-connectors/pull/452
--
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: notificatio
raboof commented on PR #453:
URL:
https://github.com/apache/incubator-pekko-connectors/pull/453#issuecomment-1933667328
failure is #454 again, rerunning
--
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
raboof commented on PR #452:
URL:
https://github.com/apache/incubator-pekko-connectors/pull/452#issuecomment-1933661385
Failure was unrelated (#454), rerunning
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL a
raboof opened a new issue, #454:
URL: https://github.com/apache/incubator-pekko-connectors/issues/454
Appears to be flaky:
```
[info] MQTT server connector
[info] - should flow through a server session (68 milliseconds)
[info] - should receive two subscriptions for the same to
pjfanning merged PR #225:
URL: https://github.com/apache/incubator-pekko-grpc/pull/225
--
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-uns
pjfanning merged PR #102:
URL: https://github.com/apache/incubator-pekko-projection/pull/102
--
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: notificatio
pjfanning merged PR #82:
URL: https://github.com/apache/incubator-pekko-persistence-r2dbc/pull/82
--
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: notifi
pjfanning merged PR #104:
URL: https://github.com/apache/incubator-pekko-persistence-jdbc/pull/104
--
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: notif
pjfanning merged PR #1104:
URL: https://github.com/apache/incubator-pekko/pull/1104
--
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-unsubs
pjfanning merged PR #473:
URL: https://github.com/apache/incubator-pekko-http/pull/473
--
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-uns
pjfanning merged PR #138:
URL: https://github.com/apache/incubator-pekko-connectors-kafka/pull/138
--
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: notif
pjfanning merged PR #224:
URL: https://github.com/apache/incubator-pekko-grpc/pull/224
--
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-uns
pjfanning commented on PR #224:
URL:
https://github.com/apache/incubator-pekko-grpc/pull/224#issuecomment-1933638374
I raised https://github.com/sbt/sbt-dynver/issues/283
In theory, we could submit such a fix ourselves and if it isn't merged, we
can add it to one of our own sbt plugi
raboof commented on PR #102:
URL:
https://github.com/apache/incubator-pekko-projection/pull/102#issuecomment-1933618338
Re-running the failed test as the failures aren't related to this change,
filed #103 and #104
--
This is an automated message from the Apache Git Service.
To respond to
raboof opened a new issue, #104:
URL: https://github.com/apache/incubator-pekko-projection/issues/104
This test appears to be flaky:
```
--> [org.apache.pekko.projection.jdbc.JdbcProjectionTest:
atLeastOnceShouldRestartFromPreviousOffset] Start of log messages of test that
failed
raboof opened a new issue, #103:
URL: https://github.com/apache/incubator-pekko-projection/issues/103
This test appears to be flaky:
```
--> [org.apache.pekko.projection.kafka.internal.KafkaSourceProviderImplSpec:
The KafkaSourceProviderImpl must successfully verify offsets from as
58 matches
Mail list logo
