palantir / palantir/conjure-java-runtime
Placeholders missing from log messages
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 95
- Forks
- 96
- Avg merge
- 3h 38m
- Merged PRs (30d)
- 33
Description
What happened?
I'm using several components from conjure-java-runtime in my Gradle plugin where I don't have enough control over the logging framework to configure SLS logging.
As such, I don't get any arguments in any of the log messages from CJR.
What did you want to happen?
Conjure Java Runtime uses SLF4J, it shouldn't make assumptions about how SLF4J is configured or the context in which its jars are used.
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 reproducing the missing-arguments behavior in the conjure-java-runtime components used from a Gradle plugin, then inspect their SLF4J logging calls. The issue does not name files or tests, so first locate the affected log messages and determine how logging is configured in this context. Done means log messages include their arguments without assuming SLS configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100