400 error on connect assistent files

API Bugs
,
21

I think the supported file extensions are case sensitive. Might that explain your situation? It did for me.

When using the Python SDK to upload a file with extension PDF to a vector store, it failed with this error:

Exception has occurred: BadRequestError
Error code: 400 - {‘error’: {‘message’: ‘Files with extensions [.PDF] are not supported for retrieval. See https://platform.openai.com/docs/assistants/tools/file-search/supported-files’, ‘type’: ‘invalid_request_error’, ‘param’: ‘file_ids’, ‘code’: ‘unsupported_file’}}

However, when I changed the file extension to pdf, it worked without any errors.

I wonder if OpenAI intended this behavior or if it’s a bug.

22

Thanks. Via the support chat I got a response that this was something their engineering team was looking into (but i have a feeling this was auto-generated…)

I think it’s just a simple hard coded list of extension types they accept and indeed it may even be case sensitive.

It’s unfortunate that the code used is not able to properly account for additional parameters in the file url… with the filetype not being at the end.

Hope they will create some additional efficient code that analyzes the entire path to find the filename/type…

23

I was encountering this issue on my local dev, using Koa and the node SDK. The Koa-Body defaults for location and filenames need to be adjusted in order to avoid bad naming default issues.

// Enable Koa body w/ configuration
app.use(koaBody({
    multipart: true,
    formidable: {
		keepExtensions: true, // keep file extension
        maxFileSize: parseInt(process.env.MYLIFE_EMBEDDING_SERVER_FILESIZE_LIMIT_ADMIN) || 10485760, // 10MB in bytes
		uploadDir: uploadDir,
		onFileBegin: (name, file) => {
			const { filepath,  mimetype, newFilename, originalFilename, size, } = file
			let extension = path.extname(originalFilename).toLowerCase()
			if(!extension)
				extension = mimeTypesToExtensions[mimetype]?.[0]
			/* validate mimetypes */
			const validFileType = mimeTypesToExtensions[mimetype]?.includes(extension)
			if(!validFileType)
				throw new Error('Invalid mime type')
			/* mutate newFilename && filepath */
			const { name: filename, } = path.parse(originalFilename)
			const safeName = filename.replace(/[^a-z0-9.]/gi, '_').replace(/\s/g, '-').toLowerCase() + extension
			/* @stub - create temp user sub-dir? */
			file.newFilename = safeName
			file.filepath = path.join(uploadDir, safeName)
			console.log(chalk.bgBlue('file-upload', chalk.yellowBright(file.filepath)))
        }
    },
}))

I’m doing a bit more than perhaps required just to allow myself a few points of intercession where I can run checks… I’m referencing here a number of internal variables so this code won’t run out of the box.
Anyhow the important part is to swap out the path and newFilename for whatever extension-filled lifestyle you choose to lead.

24

The following code works; if you handle file streams this way, there won’t be any issues.
for key in file_keys:
obj = s3_client.get_object(Bucket=AWS_STORAGE_BUCKET_NAME, Key=key
file_stream = BytesIO(obj[“Body”].read())
file_stream.name = key.split(“/”)[-1]
file_streams.append(file_stream)

file_batch = client.beta.vector_stores.file_batches.upload_and_poll(
vector_store_id=self.collection.id,
files=file_streams,
)

25

Finally managed to get this working… i.e. using the create upload API.

  1. create upload (estabish the filename)
  2. add upload part (via the s3 pre-signed URL)
  3. finish the upload (capture the file_id)
  4. connect to relevant vector store…

Quite a workaround but gets the job done…

26

Do you mind sharing the code you used here? I’m trying to use the examples above but it’s not working for me.

27

Hi

First step:
see: https://platform.openai.com/docs/api-reference/uploads/create

Here you can create your filename; make sure you capture the filesize expressed in bytes

Second step:
https://platform.openai.com/docs/api-reference/uploads/add-part

(i.e. transfer the file into the upload)

Third step:
https://platform.openai.com/docs/api-reference/uploads/complete

This will give access to your file for whatever purpose needed (e.g. tying it to a vector store, message or thread).

Hope this helps