Yaffle/EventSource

Possible connection leak? A new SSE connection is opened on every onerror status=undefined

Open

#144 opened on 2020年2月3日

GitHub で見る
 (10 comments) (1 reaction) (0 assignees)JavaScript (1,873 stars) (320 forks)batch import
help wanted

説明

Hi @Yaffle need your help in figuring this out. I see a pattern where a new connection is opened on every onerror and the status for the on error is status=undefined. The client does not get any data through SSE connection and after few seconds onerror with status=undefined is invoked again and a new connection is made to the backend. All these connections kept open till the browser/session is closed and all the connections are closed together. Could you please help in figuring this out and understand why this is happening and help in fixing it?

コントリビューターガイド

技術スタック
javascript
領域
frontend
Issue 種別
bug
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
3
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
1-3 hours
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
stale
明確さ期待される変更、受け入れ条件、次の手順がどれだけ明確かを示します。
needs investigation
前提条件
Basic understanding of EventSourceJavaScript debugging skills
初心者向け度初回貢献者にどれだけ取り組みやすいかを 1-100 で推定したスコアです。
30
調査方針
Investigate the reconnection logic in the EventSource polyfill, specifically the onerror handler. Check for any conditions where status is undefined and why it triggers a new connection. Look at the closed PRs or issues for similar problems. Test with a simple server that sends events and observe the network behavior.