spring-cloud / spring-cloud/spring-cloud-bus
Add a test for no dispatcher problem in #137
Open
Nobody has claimed this yet.
task
- Dominant language
- Java
- Stars
- 445
- Forks
- 246
- Avg merge
- 16h 25m
- Merged PRs (30d)
- 5
Description
This may need to go in the standalone tests project. https://github.com/spring-cloud/spring-cloud-core-tests
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
Start by reading issue #137, then inspect the standalone tests project at spring-cloud/spring-cloud-core-tests to determine where this regression belongs. Add a test covering the no-dispatcher problem described by #137; done means the test reproduces the reported behavior and passes with the fix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring, spring-boot
- Domain
- backend, testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100