Can not parse ChatCompletionChunk when using streamChatCompletion about jvm-openai

[StefanBratanov]

Thank you. Brings an interesting point because the Jackson scope in this library is implementation and not api so it is not classified as transitive dependency by Gradle and thus lower version of Jackson could be used. I may change this to api in next release to avoid this.

[StefanBratanov]

Hi, which version of the library do you use? I added a test to deserialize this json as part of 2308414 and it works.

[hntan]

Hi, which version of the library do you use? I added a test to deserialize this json as part of 2308414 and it works.

My application uses Jackson version 2.15.2

[StefanBratanov]

I tried downgrading to this version and it still works. Are you trying to deserialize it using your own ObjectMapper or just getting this error when using the library?

[hntan]

I tried downgrading to this version and it still works. Are you trying to deserialize it using your own ObjectMapper or just getting this error when using the library?

No, I'm not trying to use other custom ObjectMapper, I use the library directly in my application and got the error, it's kind of strange. (Of course our application has a custom ObjectMapper instance but the OpenAIClient uses it owns instance in ObjectMapperSingleton which uses PropertyNamingStrategies.SNAKE_CASE)

[StefanBratanov]

Hmm yes, it is strange. I can't seem to be able to reproduce with the json that you provided. Just to confirm which Java version and OS do you use?

[hntan]

Hmm yes, it is strange. I can't seem to be able to reproduce with the json that you provided. Just to confirm which Java version and OS do you use?

Hi @StefanBratanov , My spring boot application uses java 17 and I use MacOs

[StefanBratanov]

Thank you. Will look into it and update here.

[hntan]

Hi @StefanBratanov , thanks for your assistance! I suspect the issue stems from conflicting Jackson library versions in my project. It's possible that version 2.15.2 isn't being used, and 2.13.3 is interfering. I rely on several other com.fasterxml.jackson.* libraries, so I'll investigate this further.

[StefanBratanov]

Hi @hntan, I have decided to keep the implementation scope, since Jackson is only used internally and I wouldn't want the dependency to be transitively exposed to consumers in case they don't use Jackson. It is a trade-off essentially. Feel free to reopen the issue if you still have issues and I can think about a solution.

[StefanBratanov]

Hi @hntan as part of https://github.com/StefanBratanov/jvm-openai/releases/tag/v0.9.1 release, I added a workaround which should fix your record deserialization problems if you still face them.