palantir / palantir/conjure-java-runtime
Unexpected null body when deserializing empty optional serialized by conjure-undertow
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 95
- Forks
- 96
- Avg merge
- 3h 38m
- Merged PRs (30d)
- 33
Description
What happened?
com.palantir.logsafe.exceptions.SafeNullPointerException: Unexpected null body is thrown when calling a conjure-undertow server endpoint via conjure-retrofit.
Repro steps:
- conjure an endpoint with return type any
- have the conjure-undertow server return
Optional.empty() - use the conjure-retrofit client to call the endpoint
What did you want to happen?
The conjure-retrofit client should understand the conjure-undertow server when an Optional.empty() is serialized and deserialized.
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 how conjure-retrofit deserializes an empty Optional returned by conjure-undertow, then compare the client and server handling of an empty serialized body. Add a regression test covering an endpoint returning Optional.empty() and verify that the client no longer throws Unexpected null body.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100