palantir / palantir/conjure-java-runtime-api
Safe Loggable QoSExceptions
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 6
- Forks
- 33
- Avg merge
- 15h 50m
- Merged PRs (30d)
- 12
Description
Other than the retry URL, all messages within QoSExceptions are static. As such it would be nice if they implemented SafeLoggable so that messages were preserved. Alternatively, they could directly extend https://github.com/palantir/safe-logging/blob/develop/preconditions/src/main/java/com/palantir/logsafe/exceptions/SafeRuntimeException.java.
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
Locate the QoSExceptions definitions and inspect the referenced SafeRuntimeException in the safe-logging preconditions module. Determine which approach fits the existing exception structure, then verify that the static exception messages are preserved safely while the retry URL behavior remains unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100