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
This documentation example: https://min.io/docs/minio/linux/developers/dotnet/API.html#putObject
shows how to create PutObjectArgs instance and call PutObjectAsync(). The problem is that after such call the file on disk is blocked and cannot be modified by other processes until PutObjectArgs instance is garbage collected and finalized. That's because PutObjectArgs.ObjectStreamData property is assigned to the proper FileStream (used to read the file being uploaded), but this FileStream is never closed until PutObjectArgs instance is finalized. Making PutObjectArgs disposable could solve this problem. Or MinioClient could close the stream after it is done with PutObjectAsync() and reopen it if called again with the same PutObjectArgs .
The text was updated successfully, but these errors were encountered:
This documentation example:
https://min.io/docs/minio/linux/developers/dotnet/API.html#putObject
shows how to create PutObjectArgs instance and call PutObjectAsync(). The problem is that after such call the file on disk is blocked and cannot be modified by other processes until PutObjectArgs instance is garbage collected and finalized. That's because PutObjectArgs.ObjectStreamData property is assigned to the proper FileStream (used to read the file being uploaded), but this FileStream is never closed until PutObjectArgs instance is finalized. Making PutObjectArgs disposable could solve this problem. Or MinioClient could close the stream after it is done with PutObjectAsync() and reopen it if called again with the same PutObjectArgs .
The text was updated successfully, but these errors were encountered: