Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Downloadable response file remains in OpenAI storage #369

Open
dhoegerlETM opened this issue Jun 16, 2024 · 1 comment
Open

Downloadable response file remains in OpenAI storage #369

dhoegerlETM opened this issue Jun 16, 2024 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@dhoegerlETM
Copy link

Describe the bug
We have a pro-account and tested the feature of file-upload and download of a generated response. In our connected OpenAI account we found out that the uploaded files are cleaned afterwards correctly but the generated response files (with purpose type "assistants_output") remain in the file storage, which we consider a leak and therefore a bug.

To Reproduce
Steps to reproduce the behavior:

  1. Activate file upload in your chat bot.
  2. Start a chat
  3. Ask a question to generate some output file, e.g. an Excel table.
  4. Await the response, download the result.
  5. Go to your OpenAI account and check the storage area "files" for the generated file
    => a) it is still there and b) is contains the whole linux-path as name instead only the part after the last slash.

Expected behavior
Output-files from OpenAI should be cleanly removed after the response as well.

@marcolivierbouch marcolivierbouch self-assigned this Jun 17, 2024
@marcolivierbouch
Copy link
Collaborator

I added to my backlog a feature to clean OpenAI account after X days.

It will remove files added after X days.

@marcolivierbouch marcolivierbouch added the enhancement New feature or request label Jun 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants