FileResponse.Size should be nullable

[chadcts]

Bug Report

Overview

When dealing with GPT generated images (ContentType.ImageFile), the Json return Null for "bytes" which causes a Json deserialization exception.

{
  "object": "file",
  "id": "file-iPkbfqILMiBDCeGe5g7aevPg",
  "purpose": "assistants_output",
  "filename": "de65da7b-686d-4826-a7eb-6461dfb956e8",
  "bytes": null, // <- missing?
  "created_at": 1701920681,
  "status": "processed",
  "status_details": null
}

To Reproduce

Steps to reproduce the behavior:

1. Ask OpenAI to draw you an image using the Assistants endpoint.
2. Try to get the file info of the image content from FilesEndpoint.GetFileInfoAsync()

Additional context

OpenAI-DotNet/OpenAI-DotNet/Files/FileResponse.cs

Lines 42 to 44 in 0138115

	[JsonInclude]
	[JsonPropertyName("bytes")]
	public int Size { get; private set; }

Simple fix:

        [JsonInclude]
        [JsonPropertyName("bytes")]
        public int? Size { get; private set; }

[StephenHodgson]

So it didn't have a size?
Seems kinda strange why the bytes would be nul

[StephenHodgson]

Did it not actually generate an image?

[chadcts]

Yes. That is the response I am getting whenever I ask the Assistant to draw me an image. "bytes" are set to null. Filename is a UUID also which is odd. But I implemented the change I mentioned and was able to download a valid image file. Could be a bug with OpenAI's API, but it causes an exception in this SDK.

…

On Wed, Dec 6, 2023 at 10:15 PM Stephen Hodgson ***@***.***> wrote: Did it not actually generate an image? — Reply to this email directly, view it on GitHub <#203 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AURARKXBGH7Z5JQI3RGTHLDYIE7HJAVCNFSM6AAAAABAKMVE5SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNBUGI4TGOBUGU> . You are receiving this because you authored the thread.Message ID: ***@***.***>

-- Chad Lowe US Team Leader M: (630) 363-6036 E: ***@***.*** ***@***.***> W: www.Plus500.com <https://www.google.com/url?q=https://www.plus500.com/&source=gmail-html&ust=1673381853064000&usg=AOvVaw1L-T2Yk0oYq_oKYdIkG2eh>

[StephenHodgson]

Also curious about what the expected encoding would even be