-
-
Notifications
You must be signed in to change notification settings - Fork 15
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
Refine S3 bucket usage #61
Comments
Enkidu93
added a commit
that referenced
this issue
Sep 7, 2023
…); fixes Refine S3 bucket usage #61 Also removed synchronous write; fixes S3 remove sync write (async only) #64 Note: Dispose has async calls/logic because "await using" on the StreamWriters in ClearMLNMTBuildJob calls DisposeAsync on the StreamWriters but Dispose on the BaseStream. This is the only way I could find to circumvent this - other solutions are welcome given there's a workaround I'm missing. --ECL
Merged
johnml1135
pushed a commit
that referenced
this issue
Sep 8, 2023
…); fixes Refine S3 bucket usage #61 Also removed synchronous write; fixes S3 remove sync write (async only) #64 Note: Dispose has async calls/logic because "await using" on the StreamWriters in ClearMLNMTBuildJob calls DisposeAsync on the StreamWriters but Dispose on the BaseStream. This is the only way I could find to circumvent this - other solutions are welcome given there's a workaround I'm missing.
johnml1135
pushed a commit
that referenced
this issue
Sep 8, 2023
…); fixes Refine S3 bucket usage #61 Also removed synchronous write; fixes S3 remove sync write (async only) #64 Note: Dispose has async calls/logic because "await using" on the StreamWriters in ClearMLNMTBuildJob calls DisposeAsync on the StreamWriters but Dispose on the BaseStream. This is the only way I could find to circumvent this - other solutions are welcome given there's a workaround I'm missing.
Fixed in #80 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
A collection of comments
The text was updated successfully, but these errors were encountered: