Require explicit port in blaze server startup
Open
bug
server
- Dominant language
- Python
- Stars
- 3.2k
- Forks
- 389
- PR merge metrics
- No merged PRs in 30d
Description
Currently blaze server clobbers an existing server if both are fired up on the same port. This would make it more explicit. Additionally we'd want to not clobber an existing server process.
Contributor guide
No contributing guide indexed for this repository
Research direction
No file or test is named; start by locating the blaze server startup entry point and reproducing two servers launched on the same port. Done means startup requires an explicit port and refuses to clobber an existing server process.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100