Note: There are bugs within the graceful shutdown process of many HTTP server backends that can cause the process to hang.

[czy-29]

备注：有很多HTTP服务器后端的“优雅停机”过程都存在会使进程卡死的bug。

---

This issue will list the associated issues or PRs for each buggy backend one by one. They may have been solved and released, or solved but not yet released, or not yet resolved. The main purpose of this issue is to serve as a reminder.

For backends with unfixed or unreleased bugs, we will provide temporary workarounds (through tokio::task::AbortHandle::abort()). But when the bug is finally fixed and released, the workaround should be removed and updated to the official implementation.

This issue will be closed when all backend hang bugs are fixed and released.

Summary of current status:

1. The warp backend is waiting for fix[1] and cannot work properly, and there is no perfect workaround solution, so the backend is temporarily removed[2] (it will be restored after the upstream fix).
2. The axum and viz backends have been fixed and are waiting for release. They can work normally after cargo update. The version number will be updated after the release.
3. The remaining backends (salvo, poem, actix-web, rocket, ntex) may or may not have had bugs in the past, but in short they are currently working fine.

---

本issue将逐一列举每个存在bug的后端的关联issue或pr，它们可能是已解决并发布的，或已解决但尚未发布的，或尚未解决的。本issue的主要目的是备忘。

对于存在未修复或未发布的bug的后端，我们会对其提供临时性的workaround（通过tokio::task::AbortHandle::abort()）。但是当最终bug被修复并发布后，workaround应当被移除并更新为正式的实现。

当所有后端的hang bug都修复并发布后，这个issue将会被关闭。

当前状态总结：

1. warp后端正在等待修复[1]，无法正常工作，且没有完美Workaround方案，因此暂时移除了该后端[2]（等上游修复后恢复）。
2. axum和viz后端已修复正在等待发版，cargo update 后可以正常工作，待发版后更新版本号。
3. 其余后端（salvo，poem，actix-web，rocket，ntex）可能曾经有bug，可能一直没有，但总之它们目前工作正常。

[czy-29]

salvo (fixed and released in v0.67.2 - 已修复并发布于v0.67.2):
issue: salvo-rs/salvo#764
pr: salvo-rs/salvo#765

[czy-29]

poem (fixed and released in v3.0.0 - 已修复并发布于v3.0.0):
issue: poem-web/poem#661
pr: poem-web/poem#780

[czy-29]

actix-web does not have this bug.
actix-web不存在此bug。

[czy-29]

axum (fixed but not released):
issue: tokio-rs/axum#2611

This is actually a lower-level hyper bug:
issue: hyperium/hyper#3576
pr: hyperium/hyper-util#101

The following bug has been fixed (24.05.09), and the patch has been returned to the current HEAD version:
But in fact, currently (24.05.08) the HEAD commit of hyper-util is still buggy, so our workaround cannot simply patch hyper-util to the git address, but needs to lock it to a commit without bugs (see: f43236e). For details about this bug, see the following PR comment: hyperium/hyper-util#102 (comment)
And issue: hyperium/hyper#3662

When both axum and hyper-util release updates containing these fixes, we should update the version number of axum and revert the commits: 6f86013 , 3852e4c , f43236e , and aa6fd33

---

axum（已修复但未发布）：
issue: tokio-rs/axum#2611

这个其实是更底层的hyper的bug：
issue: hyperium/hyper#3576
pr: hyperium/hyper-util#101

以下bug已修复（24.05.09），patch已回到当前的HEAD版本上：
但实际上目前（24.05.08）hyper-util的HEAD提交依然是有bug的，因此我们的workaround不能简单地将hyper-util patch到git地址上，而是需要锁定到一个没有bug的提交上（见：f43236e ）。对于这个bug的详情，见以下pr评论：hyperium/hyper-util#102 (comment)
以及issue：hyperium/hyper#3662

当axum和hyper-util都发布了包含这些修复的更新之后，我们应当更新axum的版本号，并撤回提交：6f86013 ，3852e4c ，f43236e ，和 aa6fd33

[czy-29]

rocket does not have this bug.
rocket不存在此bug。

[czy-29]

warp (not fixed):
issue: seanmonstar/warp#1100

This is very similar to the Axum bug above, but the solution using the patch hyper-util provided by Axum is invalid. We need to wait for the warp author to reply and fix it.
Because there is no working workaround solution, the backend is temporarily removed until the upstream fix: d4af016
After the fix, we should first patch warp, then test the fix results, and then undo the above commit.
Then when warp is released, we should revert the patch and update the version number of warp.

---

warp（未修复）：
issue：seanmonstar/warp#1100

这个跟上面Axum的bug非常像，但用Axum提供的patch hyper-util的解决方案无效，需等待warp作者回复并修复。
因为没有可以正常工作的workaround方案，因此上游修复前，该后端被暂时移除：d4af016
修复后，我们应当先patch warp，然后测试修复结果，然后撤回上述提交。
然后当warp发版后，我们应当撤回patch，然后更新warp的版本号。

[czy-29]

viz (fixed but not released):
issue: viz-rs/viz#138

This bug is almost 100% the same as the above-mentioned axum bug, so I won’t go into details again and wait for the release.

---

viz（已修复但未发布）：
issue：viz-rs/viz#138

这个bug跟上述axum的bug几乎100%一样，因此不再赘述，等待发版。

[czy-29]

ntex does not have this bug.
ntex不存在此bug。