You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @ahmogit. I've not yet released because of this bug report I just filed with OpenAI. As a quick fix, I've found that s/3\.0\.0/3.1.0/ in the OpenAI spec fixes the issue, though it's not entirely clear why since the OpenAI spec uses a mixture of features from both versions.
@Ovid Thanks for the quick fix on that; can confirm it works for me as well (though I too am puzzled as to why it works, given the admixture of 3.0.0 and 3.1.0 constructs present in the yaml). Will be interesting to hear OpenAI 's response to your bug report.
Imo, they have been over-lax with their spec versioning, to put it politely. They don't even seem to be bumping their internal version in the "info" section consistently. The changes made in that latest commit were extensive, yet the version ID remained at 2.3.0. I dunno, perhaps there's a good reason for not bumping the version that I simply don't understand, but it sure seems like poor practice to me.
I've been doing battle with this issue -- yaml validation errors on that latest openapi.yaml -- all day. My assumption was that v0.22 worked with that latest openapi.yaml commit, but now I see (just as you said in the bug report) that v0.22 was failing its own chat completion test with openapi version set to 3.0.0, as it currently is.
Anyway, thanks for the quick response and the 3.0.0 -> 3.1.0 workaround, that gets me back on the air for what I was doing. Hopefully OpenAI properly addresses the spec issue soon.
CPAN still has 0.21.
Thanks!
The text was updated successfully, but these errors were encountered: