All issues
Issue creation is restricted in this repository
- #3411 · seanmonstar opened
on Nov 15, 2023 6 - #3214 · seanmonstar opened
on Apr 28, 2023 1
问题
is:issue state:open
is:issue state:open
搜索 results
HTTP/1 client connection is never closed or pooled when a response completes while the request body is still unsent ((Reading::KeepAlive, Writing::Body) is a terminal state)
C-bugCategory: bug. Something is wrong. This is bad!Category: bug. Something is wrong. This is bad!Status: Open.#4176 In hyperium/hyper;Change graceful_shutdown function behaviorPR can cause tonic servers to hangserve_with_incoming_shutdownin two different casesA-http2Area: HTTP/2 specific.Area: HTTP/2 specific.C-bugCategory: bug. Something is wrong. This is bad!Category: bug. Something is wrong. This is bad!Status: Open.#4170 In hyperium/hyper;Client never observes TCP EOF after
serve_connection_with_upgradesfuture resolves successfully (hyper-utilauto::Builder)C-bugCategory: bug. Something is wrong. This is bad!Category: bug. Something is wrong. This is bad!S-waiting-on-authorStatus: waiting on the author to provide more info, or make changes.Status: waiting on the author to provide more info, or make changes.Status: Open.#4159 In hyperium/hyper;Body dropped too late when an h1 handshake hits an error
C-bugCategory: bug. Something is wrong. This is bad!Category: bug. Something is wrong. This is bad!Status: Open.#4122 In hyperium/hyper;hyper-util: legacy client pool IdleTask spins every pool_idle_timeout when pool is empty
A-clientArea: client.Area: client.C-bugCategory: bug. Something is wrong. This is bad!Category: bug. Something is wrong. This is bad!E-mediumEffort: medium. Some knowledge of how hyper internal works would be useful.Effort: medium. Some knowledge of how hyper internal works would be useful.E-pr-welcomeEffort: a pull request is welcome.Effort: a pull request is welcome.K-hyper-utilCrate: hyper-utilCrate: hyper-utilStatus: Open.#4100 In hyperium/hyper;Remove unnecessary static lifetime constraint on body
A-serverArea: server.Area: server.B-breaking-changeBlocked: this is an "API breaking change".Blocked: this is an "API breaking change".C-featureCategory: feature. This is adding a new feature.Category: feature. This is adding a new feature.Status: Open.#4096 In hyperium/hyper;HTTP CONNECT proxy tunnel has lax response parsing and loses early data
A-clientArea: client.Area: client.C-bugCategory: bug. Something is wrong. This is bad!Category: bug. Something is wrong. This is bad!E-pr-welcomeEffort: a pull request is welcome.Effort: a pull request is welcome.K-hyper-utilCrate: hyper-utilCrate: hyper-utilStatus: Open.#4095 In hyperium/hyper;Add a strict clippy config
C-refactorCategory: refactor. This would improve the clarity of internal code.Category: refactor. This would improve the clarity of internal code.E-easyEffort: easy. A task that would be a great starting point for a new contributor.Effort: easy. A task that would be a great starting point for a new contributor.E-pr-welcomeEffort: a pull request is welcome.Effort: a pull request is welcome.Status: Open.#4071 In hyperium/hyper;Windows system proxy: per-scheme ProxyServer format (e.g. socks=127.0.0.1:1080) not parsed
A-clientArea: client.Area: client.C-bugCategory: bug. Something is wrong. This is bad!Category: bug. Something is wrong. This is bad!E-easyEffort: easy. A task that would be a great starting point for a new contributor.Effort: easy. A task that would be a great starting point for a new contributor.K-hyper-utilCrate: hyper-utilCrate: hyper-utilStatus: Open.#4067 In hyperium/hyper;Parsed
Bytesin headers can pin large IO buffers in memoryB-rfcBlocked: More comments would be useful in determine next steps.Blocked: More comments would be useful in determine next steps.C-performanceCategory: performance. This is making existing behavior go faster.Category: performance. This is making existing behavior go faster.Status: Open.#4060 In hyperium/hyper;hyper-util pool: unnamable types are hard to work with
E-hardEffort: hard. Likely requires a deeper understanding of how hyper's internals work.Effort: hard. Likely requires a deeper understanding of how hyper's internals work.K-hyper-utilCrate: hyper-utilCrate: hyper-utilS-waiting-on-reviewStatus: waiting on review.Status: waiting on review.Status: Open.#4059 In hyperium/hyper;Excessive per-connection memory cause by channel
A-clientArea: client.Area: client.B-upstreamBlocked: needs a change in a dependency or the compiler.Blocked: needs a change in a dependency or the compiler.C-performanceCategory: performance. This is making existing behavior go faster.Category: performance. This is making existing behavior go faster.S-blockedStatus: blocked on something else.Status: blocked on something else.Status: Open.#4057 In hyperium/hyper;