max-mapper / max-mapper/websocket-stream
How to investigate firewall issues?
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 667
- Forks
- 110
- PR merge metrics
- No merged PRs in 30d
Description
If you look at https://github.com/mafintosh/duplexify/issues/4 I suspect there are firewall issues, breaking stream functionality maybe. Not sure. Maybe the problem has other causes?
But do you have any tricks or commands I could use to double check this?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked duplexify issue and the websocket-stream behavior described here; no repository file, test, or entry point is identified. Investigate whether firewall conditions reproduce the stream failure, using appropriate diagnostic commands, and document whether the firewall is the cause or whether another cause remains.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100