spring-cloud / spring-cloud/spring-cloud-consul
print more details when catching consul-api's OperationException
Open
Nobody has claimed this yet.
enhancement
help wanted
- Dominant language
- Java
- Stars
- 822
- Forks
- 539
- Avg merge
- 9h 31m
- Merged PRs (30d)
- 7
Description
when consul-api throws a OperationException，some methods like ConsulCatalogWatch.catalogServicesWatch() catch it with an Exception, then log the stacktrace.
But the OperationException's attrs are lost.
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 locating ConsulCatalogWatch.catalogServicesWatch() and the other methods that catch OperationException as Exception. Inspect how the exception is logged and ensure the OperationException attrs are retained in the logged details; done means those attributes appear when the exception is caught.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100