recover gracefully from a malformed config file (on startup and HUP)
Open
Nobody has claimed this yet.
bug
- Dominant language
- Ruby
- Stars
- 456
- Forks
- 149
- Avg merge
- 9d 7h
- Merged PRs (30d)
- 3
Description
report malformed config in procline and on web interface
on startup: just startup with no workers configured
on HUP: just keep current config
Contributor guide
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
Trace the Ruby startup and HUP configuration handling, including where malformed configuration is reported in procline and the web interface. Verify the behavior for a malformed file: startup runs with no workers configured, while HUP preserves the current configuration and reports the error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100