Raised during an image captioning process.
#peer closed connection without sending complete message body (incomplete chunked read)
jade jewel
ebon wharf
Do you have a screenshot?
jade jewel
Hi, thanks for replying, you mean of the error?
ebon wharf
Hi, thanks for replying, you mean of the error?
For Sure
jade jewel
I'm trying now to see if i can get more but that line is the one raised. I've seen other people asking about this in openAi forum actually
the process involved a pretty long file 273 images
ebon wharf
I'm trying now to see if i can get more but that line is the one raised. I've se...
Have you already tried zipping it?
jade jewel
Nope, i'm doing that in my application, the process is converting pages in images and captioning them, so i would still need to unzip. it crashes during the captioning thread exectution
ebon wharf
Nope, i'm doing that in my application, the process is converting pages in image...
Have you checked for a file path?
jade jewel
what you mean sorry?
ebon wharf
The path to your files, the folder and the tree structure where it is located, and this path is transmitted to the code if you are using code.
jade jewel
ah ok, i pass them as base64
using the format data:image/...;base64,...
to the llm i mean
ebon wharf
ah ok, i pass them as base64
On the API, you have an image limit per request. You cannot send 273 at once.
If you have a large API quota, you can send them several times in the same chat to continue the same discussion with all the images.
ebon wharf
in sequence
I advise you to put as many images as possible per call because 273 calls can saturate and slow down, I think.
Maximum of 10 images per API call