Yeah, we don’t know how to handle/if we should handle the case where None is returned. Previously its just set to put anything other than “stop” to fail, but the summary quality of None seems fine…
Yeah, the verbiage makes me think it’s temporary. Might add it into your whitelist, though, if it’s giving good completions… maybe with an extra warning to users?
I always specify a stop (normally ####) and have only seen completions end for 1 of 2 reasons:
‘stop’
‘length’
Honest, I have never experienced any “None” reason for a finished completion and like you I mostly use the text-davinci-003 model.
If you have any specific prompt you have experienced issues with, please post the prompt (all your API completion parameters) and I will test it for you.
Please note that I can reproduce the “None” completion reason by including the stop in the prompt; so I recommend you only send the stop parameter to the API and do not include the stop in the actual prompt.