PrismarineJS / PrismarineJS/node-minecraft-protocol
use port 0 for test
Open
Nobody has claimed this yet.
refactoring
test
- Dominant language
- JavaScript
- Stars
- 1.4k
- Forks
- 290
- Avg merge
- 4d 8h
- Merged PRs (30d)
- 7
Description
much better than trying a random port
see https://github.com/PrismarineJS/flying-squid/pull/333/commits/754ec4bced7ddc221566f652083b8aea9d987100
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 by reviewing the test setup and the referenced flying-squid commit at https://github.com/PrismarineJS/flying-squid/pull/333/commits/754ec4bced7ddc221566f652083b8aea9d987100. Identify where tests choose a random port, switch that setup to port 0, and confirm the test suite still passes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- networking, testing
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100