ChatChoice finish_reason can be null

[ming08108]

finish_reason can sometimes be null in CreateChatCompletionResponse.

[64bit]

Hi @ming08108 , thank you for PR.

Is this always the case or its intermittent?

In my testing I did not observe that otherwise examples/chat would have crashed gotten deserialization error .

One exception is Chat API with SSE streaming, where I did notice it to be null, which is already an Option<String> here https://github.com/64bit/async-openai/blob/main/async-openai/src/types/types.rs#L803

[jonaro00]

@64bit I am also getting null on this field. In my case, the chance seems to be around 1 in 15.

[zurawiki]

+1 this is happening for me too

[ming08108]

Hi @ming08108 , thank you for PR.

Is this always the case or its intermittent?

In my testing I did not observe that otherwise examples/chat would have crashed gotten deserialization error .

One exception is Chat API with SSE streaming, where I did notice it to be null, which is already an Option<String> here https://github.com/64bit/async-openai/blob/main/async-openai/src/types/types.rs#L803

Seems to be intermittent/random.

Some other reports of it here:
openai-php/client#50
openai-php/client#52

[64bit]

aha, that's no good, lets ship this

[64bit]

Its released in 0.9.0. Thank you everyone