akka/akka-http issues and pull requests

#4204 - ci: permit checks write for test reporting

Pull Request - State: closed - Opened by ennru over 1 year ago

#4204 - ci: permit checks write for test reporting

Pull Request - State: closed - Opened by ennru over 1 year ago

#4204 - ci: permit checks write for test reporting

Pull Request - State: closed - Opened by ennru over 1 year ago

#4204 - ci: permit checks write for test reporting

Pull Request - State: closed - Opened by ennru over 1 year ago

#4204 - ci: permit checks write for test reporting

Pull Request - State: closed - Opened by ennru over 1 year ago

#4203 - build: update scala3-library from 3.1.3 to 3.2.1

Pull Request - State: closed - Opened by scala-steward over 1 year ago - 4 comments

#4203 - build: update scala3-library from 3.1.3 to 3.2.1

Pull Request - State: closed - Opened by scala-steward over 1 year ago - 4 comments

#4203 - build: update scala3-library from 3.1.3 to 3.2.1

Pull Request - State: closed - Opened by scala-steward over 1 year ago - 4 comments

#4203 - build: update scala3-library from 3.1.3 to 3.2.1

Pull Request - State: closed - Opened by scala-steward over 1 year ago - 4 comments

#4203 - build: update scala3-library from 3.1.3 to 3.2.1

Pull Request - State: closed - Opened by scala-steward over 1 year ago - 4 comments

#4203 - build: update scala3-library from 3.1.3 to 3.2.1

Pull Request - State: closed - Opened by scala-steward over 1 year ago - 4 comments

#4203 - build: update scala3-library from 3.1.3 to 3.2.1

Pull Request - State: closed - Opened by scala-steward over 1 year ago - 4 comments

#4203 - build: update scala3-library from 3.1.3 to 3.2.1

Pull Request - State: closed - Opened by scala-steward over 1 year ago - 4 comments

#4203 - build: update scala3-library from 3.1.3 to 3.2.1

Pull Request - State: closed - Opened by scala-steward over 1 year ago - 4 comments

#4203 - build: update scala3-library from 3.1.3 to 3.2.1

Pull Request - State: closed - Opened by scala-steward over 1 year ago - 4 comments

#4202 - build: update sbt-header from 5.8.0 to 5.9.0

Pull Request - State: closed - Opened by scala-steward over 1 year ago

#4202 - build: update sbt-header from 5.8.0 to 5.9.0

Pull Request - State: closed - Opened by scala-steward over 1 year ago

#4202 - build: update sbt-header from 5.8.0 to 5.9.0

Pull Request - State: closed - Opened by scala-steward over 1 year ago

#4202 - build: update sbt-header from 5.8.0 to 5.9.0

Pull Request - State: closed - Opened by scala-steward over 1 year ago

#4202 - build: update sbt-header from 5.8.0 to 5.9.0

Pull Request - State: closed - Opened by scala-steward over 1 year ago

#4202 - build: update sbt-header from 5.8.0 to 5.9.0

Pull Request - State: closed - Opened by scala-steward over 1 year ago

#4202 - build: update sbt-header from 5.8.0 to 5.9.0

Pull Request - State: closed - Opened by scala-steward over 1 year ago

#4197 - Revert parboiled upper/lowercase changes for performance

Pull Request - State: closed - Opened by johanandren over 1 year ago

#4197 - Revert parboiled upper/lowercase changes for performance

Pull Request - State: closed - Opened by johanandren over 1 year ago

#4197 - Revert parboiled upper/lowercase changes for performance

Pull Request - State: closed - Opened by johanandren over 1 year ago

#4197 - Revert parboiled upper/lowercase changes for performance

Pull Request - State: closed - Opened by johanandren over 1 year ago

#4197 - Revert parboiled upper/lowercase changes for performance

Pull Request - State: closed - Opened by johanandren over 1 year ago

#4197 - Revert parboiled upper/lowercase changes for performance

Pull Request - State: closed - Opened by johanandren over 1 year ago

#4197 - Revert parboiled upper/lowercase changes for performance

Pull Request - State: closed - Opened by johanandren over 1 year ago

#4197 - Revert parboiled upper/lowercase changes for performance

Pull Request - State: closed - Opened by johanandren over 1 year ago

#4190 - chore: pass jvmopts in publish workflow

Pull Request - State: closed - Opened by ennru over 1 year ago

#4190 - chore: pass jvmopts in publish workflow

Pull Request - State: closed - Opened by ennru over 1 year ago

#4190 - chore: pass jvmopts in publish workflow

Pull Request - State: closed - Opened by ennru over 1 year ago

#4190 - chore: pass jvmopts in publish workflow

Pull Request - State: closed - Opened by ennru over 1 year ago

#4190 - chore: pass jvmopts in publish workflow

Pull Request - State: closed - Opened by ennru over 1 year ago

#4190 - chore: pass jvmopts in publish workflow

Pull Request - State: closed - Opened by ennru over 1 year ago

#4190 - chore: pass jvmopts in publish workflow

Pull Request - State: closed - Opened by ennru over 1 year ago

#4189 - chore: renovate GH workflows

Pull Request - State: closed - Opened by ennru over 1 year ago

#4189 - chore: renovate GH workflows

Pull Request - State: closed - Opened by ennru over 1 year ago

#4189 - chore: renovate GH workflows

Pull Request - State: closed - Opened by ennru over 1 year ago

#4189 - chore: renovate GH workflows

Pull Request - State: closed - Opened by ennru over 1 year ago

#4189 - chore: renovate GH workflows

Pull Request - State: closed - Opened by ennru over 1 year ago

#4156 - akka-http 10.2.10 seems to have changed the semantics of the max-open-requests host connection pool configuration

Issue - State: open - Opened by jphelp32 almost 2 years ago - 3 comments
Labels: t:docs, 1 - triaged

#4156 - akka-http 10.2.10 seems to have changed the semantics of the max-open-requests host connection pool configuration

Issue - State: open - Opened by jphelp32 almost 2 years ago - 3 comments
Labels: t:docs, 1 - triaged

#4156 - akka-http 10.2.10 seems to have changed the semantics of the max-open-requests host connection pool configuration

Issue - State: open - Opened by jphelp32 almost 2 years ago - 3 comments
Labels: t:docs, 1 - triaged

#4156 - akka-http 10.2.10 seems to have changed the semantics of the max-open-requests host connection pool configuration

Issue - State: open - Opened by jphelp32 almost 2 years ago - 3 comments
Labels: t:docs, 1 - triaged

#4156 - akka-http 10.2.10 seems to have changed the semantics of the max-open-requests host connection pool configuration

Issue - State: open - Opened by jphelp32 almost 2 years ago - 3 comments
Labels: t:docs, 1 - triaged

#4156 - akka-http 10.2.10 seems to have changed the semantics of the max-open-requests host connection pool configuration

Issue - State: open - Opened by jphelp32 almost 2 years ago - 3 comments
Labels: t:docs, 1 - triaged

#4153 - Failed: MethodDirectivesSpec

Issue - State: closed - Opened by johanandren almost 2 years ago
Labels: failed

#4153 - Failed: MethodDirectivesSpec

Issue - State: closed - Opened by johanandren almost 2 years ago
Labels: failed

#4153 - Failed: MethodDirectivesSpec

Issue - State: closed - Opened by johanandren almost 2 years ago
Labels: failed

#4153 - Failed: MethodDirectivesSpec

Issue - State: closed - Opened by johanandren almost 2 years ago
Labels: failed

#4153 - Failed: MethodDirectivesSpec

Issue - State: closed - Opened by johanandren almost 2 years ago
Labels: failed

#4142 - Now that Route.asyncHandler is deprecated, there is now no way to avoid the default ExceptionHandler

Issue - State: closed - Opened by blast-hardcheese almost 2 years ago - 4 comments
Labels: 3 - in progress, t:testing

#4142 - Now that Route.asyncHandler is deprecated, there is now no way to avoid the default ExceptionHandler

Issue - State: closed - Opened by blast-hardcheese almost 2 years ago - 4 comments
Labels: 3 - in progress, t:testing

#4142 - Now that Route.asyncHandler is deprecated, there is now no way to avoid the default ExceptionHandler

Issue - State: closed - Opened by blast-hardcheese almost 2 years ago - 4 comments
Labels: 3 - in progress, t:testing

#4142 - Now that Route.asyncHandler is deprecated, there is now no way to avoid the default ExceptionHandler

Issue - State: closed - Opened by blast-hardcheese almost 2 years ago - 4 comments
Labels: 3 - in progress, t:testing

#4142 - Now that Route.asyncHandler is deprecated, there is now no way to avoid the default ExceptionHandler

Issue - State: closed - Opened by blast-hardcheese almost 2 years ago - 4 comments
Labels: 3 - in progress, t:testing

#4142 - Now that Route.asyncHandler is deprecated, there is now no way to avoid the default ExceptionHandler

Issue - State: closed - Opened by blast-hardcheese almost 2 years ago - 4 comments
Labels: 3 - in progress, t:testing

#4142 - Now that Route.asyncHandler is deprecated, there is now no way to avoid the default ExceptionHandler

Issue - State: closed - Opened by blast-hardcheese almost 2 years ago - 4 comments
Labels: 3 - in progress, t:testing

#4142 - Now that Route.asyncHandler is deprecated, there is now no way to avoid the default ExceptionHandler

Issue - State: closed - Opened by blast-hardcheese almost 2 years ago - 4 comments
Labels: 3 - in progress, t:testing

#4142 - Now that Route.asyncHandler is deprecated, there is now no way to avoid the default ExceptionHandler

Issue - State: closed - Opened by blast-hardcheese almost 2 years ago - 4 comments
Labels: 3 - in progress, t:testing

#4142 - Now that Route.asyncHandler is deprecated, there is now no way to avoid the default ExceptionHandler

Issue - State: closed - Opened by blast-hardcheese almost 2 years ago - 4 comments
Labels: 3 - in progress, t:testing

#4142 - Now that Route.asyncHandler is deprecated, there is now no way to avoid the default ExceptionHandler

Issue - State: closed - Opened by blast-hardcheese almost 2 years ago - 4 comments
Labels: 3 - in progress, t:testing

#4142 - Now that Route.asyncHandler is deprecated, there is now no way to avoid the default ExceptionHandler

Issue - State: closed - Opened by blast-hardcheese almost 2 years ago - 4 comments
Labels: 3 - in progress, t:testing

#4122 - Wrong TLS session after ssl handshake completed over TLSv1.3 protocol

Issue - State: closed - Opened by adibaranga about 2 years ago - 17 comments
Labels: 3 - in progress

#4122 - Wrong TLS session after ssl handshake completed over TLSv1.3 protocol

Issue - State: closed - Opened by adibaranga about 2 years ago - 17 comments
Labels: 3 - in progress

#4122 - Wrong TLS session after ssl handshake completed over TLSv1.3 protocol

Issue - State: closed - Opened by adibaranga about 2 years ago - 17 comments
Labels: 3 - in progress

#4122 - Wrong TLS session after ssl handshake completed over TLSv1.3 protocol

Issue - State: closed - Opened by adibaranga about 2 years ago - 17 comments
Labels: 3 - in progress

#4122 - Wrong TLS session after ssl handshake completed over TLSv1.3 protocol

Issue - State: closed - Opened by adibaranga about 2 years ago - 17 comments
Labels: 3 - in progress

#4104 - Failed: HTTP 2 managed persistent connection (tls = true) should transparently reconnect when connection is closed (with backoff: false) should when the first connection fails to materialize

Issue - State: open - Opened by jrudolph about 2 years ago - 1 comment
Labels: failed, 1 - triaged, t:http2

#4082 - The request's encoding is corrupt: Parsing failed in step ReadHeaders

Issue - State: closed - Opened by yelamarthi over 2 years ago - 1 comment
Labels: 0 - new

#4082 - The request's encoding is corrupt: Parsing failed in step ReadHeaders

Issue - State: closed - Opened by yelamarthi over 2 years ago - 1 comment
Labels: 0 - new

#4082 - The request's encoding is corrupt: Parsing failed in step ReadHeaders

Issue - State: closed - Opened by yelamarthi over 2 years ago - 1 comment
Labels: 0 - new

#4082 - The request's encoding is corrupt: Parsing failed in step ReadHeaders

Issue - State: closed - Opened by yelamarthi over 2 years ago - 1 comment
Labels: 0 - new

#4082 - The request's encoding is corrupt: Parsing failed in step ReadHeaders

Issue - State: closed - Opened by yelamarthi over 2 years ago - 1 comment
Labels: 0 - new

#4082 - The request's encoding is corrupt: Parsing failed in step ReadHeaders

Issue - State: closed - Opened by yelamarthi over 2 years ago - 1 comment
Labels: 0 - new

#4049 - Failed: akka.http.scaladsl.ClientServerHttp2EnabledSpec ► The low-level HTTP infrastructure should timeouts should support client timeouts should avoid client vs. server race-condition for persistent connections with keep-alive-timeout

Issue - State: open - Opened by jrudolph over 2 years ago - 3 comments
Labels: failed, t:core

#4049 - Failed: akka.http.scaladsl.ClientServerHttp2EnabledSpec ► The low-level HTTP infrastructure should timeouts should support client timeouts should avoid client vs. server race-condition for persistent connections with keep-alive-timeout

Issue - State: open - Opened by jrudolph over 2 years ago - 3 comments
Labels: failed, t:core

#4049 - Failed: akka.http.scaladsl.ClientServerHttp2EnabledSpec ► The low-level HTTP infrastructure should timeouts should support client timeouts should avoid client vs. server race-condition for persistent connections with keep-alive-timeout

Issue - State: open - Opened by jrudolph over 2 years ago - 3 comments
Labels: failed, t:core

#4049 - Failed: akka.http.scaladsl.ClientServerHttp2EnabledSpec ► The low-level HTTP infrastructure should timeouts should support client timeouts should avoid client vs. server race-condition for persistent connections with keep-alive-timeout

Issue - State: open - Opened by jrudolph over 2 years ago - 3 comments
Labels: failed, t:core

GitHub / akka/akka-http issues and pull requests