Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[chat example] How to simulate slow connection?

Open
#542 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
go
Domain
networking

Research direction

Start with internal/examples/chat/chat.go around lines 120-127 and trace the closeSlow callback through the chat example's subscriber behavior. Run the chat example while examining how messages reach the subscriber, then document a reproducible way to trigger the slow-connection condition and what result to expect.

Written by the indexing model from the issue text.

Description

I want to observe in what scenario closeSlow is called, How to simulate slow connection mentioned in websocket/internal/examples/chat/chat.go?:

s := &subscriber{
	msgs: make(chan []byte, cs.subscriberMessageBuffer),
	closeSlow: func() {
		mu.Lock()
		defer mu.Unlock()
		closed = true
		if c != nil {
			c.Close(websocket.StatusPolicyViolation, "connection too slow to keep up with messages")
		}
	},
}
Dominant language
Go
Stars
5.5k
Forks
377
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from coder/websocket

All issues in coder/websocket

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.