jooby-project / jooby-project/jooby
server: call server.init after setting the server options (not before)
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.8k
- Forks
- 202
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 6
Description
Calling server.init too early causes a leak between the final server options and what the application saves in the service registry.
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 tracing the server initialization entry point and the code that applies server options before registering the application in the service registry. Confirm where server.init currently runs relative to option setup, then verify that initialization uses the final options without leaking earlier state; the issue names no files or tests, so locate the relevant coverage before changing behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, kotlin
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100