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
{{ message }}
This repository has been archived by the owner on Aug 1, 2024. It is now read-only.
Which service(blob, file, queue, table) does this issue concern?
blob
Which version of the SDK was used?
4.0.3 (seems to be present in 4.0.4)
Which platform are you using? (ex: .NET Core 2.1)
.NETStandard 2.0
What problem was encountered?
BlobReadStreamBase reports that it can be read from, even after the internalBuffer has been disposed of
How can we reproduce the problem in the simplest way?
Create a [Blob] Stream
Dispose it
check the value of CanRead
Have you found a mitigation/solution?
Obviously Not disposing it is a good solution here to make it actually work, but it would be nice if "CanRead" and "CanSeek" would reflect the internal invalidness something like this:
publicoverrideboolCanRead{
get
{returnthis.internalBuffer !=null;}}
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Which service(blob, file, queue, table) does this issue concern?
blob
Which version of the SDK was used?
4.0.3 (seems to be present in 4.0.4)
Which platform are you using? (ex: .NET Core 2.1)
.NETStandard 2.0
What problem was encountered?
BlobReadStreamBase reports that it can be read from, even after the internalBuffer has been disposed of
How can we reproduce the problem in the simplest way?
[Blob] Stream
CanRead
Have you found a mitigation/solution?
Obviously Not disposing it is a good solution here to make it actually work, but it would be nice if "CanRead" and "CanSeek" would reflect the internal invalidness something like this:
The text was updated successfully, but these errors were encountered: