Hacktoberfest 2026:維護者為十月標記出來的 issue,仍然開放、適合新手。 瀏覽 Hacktoberfest issue

Make n-t-tcp fully asynchronous... Maybe..

未關閉
#428 2 則留言 0 個 reaction 已指派 6 人 在 GitHub 檢視

@dcoutts 已經在處理了。

開始於 2018年11月23日。

評估

這個 Issue 還沒有評估資料。

描述

network-transport-tcp

Folks whom I've assigned this to - I'm just looking for feedback and suggestions as to where I can look in the code to potentially fix this issue. I know you're all off doing other things!

Perhaps an issue for network-transport to discuss initially!?

There are a number of fundamental issues that make things a struggle in Cloud Haskell land...

In distributed-process, the node controller can block when remote nodes are unavailable, which is less than ideal. This is the first issue that needs to be solved, since the NC blocking on network calls is a massive bottleneck for CH.

I am very aware that we do not wish to introduce unbounded buffers into the pipeline. It's a design point I completely agree with.

How can go about removing this potential bottleneck, and what other implementations out there ought I to be looking at?

主要語言
Haskell
星號
753
分支
101
平均合併
1 天 3 小時
30 天內合併 PR
4

環境準備

  • 沒有 Dockerfile 或 Docker Compose 檔案
  • 沒有 Pull Request 範本
  • 閱讀貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

haskell-distributed/distributed-process 的其他 Issue

查看 haskell-distributed/distributed-process 的全部 Issue

相似的 Issue

更多 Haskell Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。