bdmendes commented on issue #638:
URL: https://github.com/apache/pekko-http/issues/638#issuecomment-2553398021
> @bdmendes if you have the code you used to reproduce this can you share
it? Helps avoid having someone write the test case from scratch.
>
> I suspect that the Unirest clie
pjfanning commented on issue #638:
URL: https://github.com/apache/pekko-http/issues/638#issuecomment-255350
I've put a POC at
https://github.com/pjfanning/pekko-http-sample/tree/binding-terminate (a branch
of my pekko-http-sample project).
`sbt run` is enough to run the POC.
jrudolph commented on issue #638:
URL: https://github.com/apache/pekko-http/issues/638#issuecomment-2555642338
Thanks for putting that together @pjfanning. I only looked quickly into it,
it might be that the issue only happens during the uncommon non-tls Http 1.1 =>
Http 2 upgrade request.
The GitHub Actions job "Nightly Pekko 1.0 Builds" on pekko-connectors.git has
failed.
Run started by GitHub user pjfanning (triggered by pjfanning).
Head commit for run:
6981eaa8a855999c39eb9006671d26c4a7280c3c / scala-steward-asf[bot]
<147768647+scala-steward-asf[bot]@users.noreply.github.com
The GitHub Actions job "Publish nightly 1.1 snapshots" on pekko-http.git has
failed.
Run started by GitHub user pjfanning (triggered by pjfanning).
Head commit for run:
4554337dd2e96cb0dd14c5b30e2a572344e0cd0f / David Sheynkman
Optimized Uri.withQuery (#637)
* Optimized Uri.withQuery
* Impr
The GitHub Actions job "Nightly Integration Tests for JDBC (Pekko 1.0.x)" on
pekko-projection.git has failed.
Run started by GitHub user pjfanning (triggered by pjfanning).
Head commit for run:
dfac188506112a4c0ba71a7916e1144f901b94be / scala-steward-asf[bot]
<147768647+scala-steward-asf[bot]@
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:
ce514f76cc762be3075d76853347db1750c6ae09 / scala-steward-asf[bot]
<147768647+scala-steward-asf[bot]@users.noreply.github.c
The GitHub Actions job "Publish Nightly" on pekko-projection.git has failed.
Run started by GitHub user mdedetrich (triggered by mdedetrich).
Head commit for run:
dfac188506112a4c0ba71a7916e1144f901b94be / scala-steward-asf[bot]
<147768647+scala-steward-asf[bot]@users.noreply.github.com>
Update
The GitHub Actions job "github_actions in /. - Update #935831201" on pekko.git
has succeeded.
Run started by GitHub user dependabot[bot] (triggered by dependabot[bot]).
Head commit for run:
7184dadf4a1d57ac07cd4eb26b67b3f8b5ccf47d / He-Pin(kerr)
chore: Fix flaky test in unsafeOptionalDataVia (
The GitHub Actions job "Nightly Tests" on pekko-management.git has succeeded.
Run started by GitHub user pjfanning (triggered by pjfanning).
Head commit for run:
7ef5fd3d0547ce761fcea183c70ec9caf613019f / scala-steward-asf[bot]
<147768647+scala-steward-asf[bot]@users.noreply.github.com>
Update
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:
22d647333ecc7b29a31528bbdd19f098902e1fbe / scala-steward-asf[bot]
<147768647+scala-steward-asf[bot]@users.noreply.github
The GitHub Actions job "Nightly Builds" on pekko.git has failed.
Run started by GitHub user pjfanning (triggered by pjfanning).
Head commit for run:
7184dadf4a1d57ac07cd4eb26b67b3f8b5ccf47d / He-Pin(kerr)
chore: Fix flaky test in unsafeOptionalDataVia (#1611)
Report URL: https://github.com/apa
The GitHub Actions job "Nightly Builds" on pekko-http.git has failed.
Run started by GitHub user He-Pin (triggered by He-Pin).
Head commit for run:
4554337dd2e96cb0dd14c5b30e2a572344e0cd0f / David Sheynkman
Optimized Uri.withQuery (#637)
* Optimized Uri.withQuery
* Improved UriSpec percent e
The GitHub Actions job "Nightly Testing with Pekko 1.0" on
pekko-persistence-jdbc.git has failed.
Run started by GitHub user raboof (triggered by raboof).
Head commit for run:
41b1b1f966274171d6d0971b0324ba0c24ab38d9 / scala-steward-asf[bot]
<147768647+scala-steward-asf[bot]@users.noreply.gith
jrudolph commented on issue #638:
URL: https://github.com/apache/pekko-http/issues/638#issuecomment-2556455652
In some way, it's no wonder that this is not implemented as the h2c 101
upgrade flow is the most complicated of all the h2 server setups (and also not
supported on the client side)
jrudolph commented on issue #638:
URL: https://github.com/apache/pekko-http/issues/638#issuecomment-2556464031
My idea was to try to invert the flow using a joinable ServerTerminator
implementation like this:
```scala
private class JoinableServerTermination extends ServerTerminator
16 matches
Mail list logo