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

LazyLoadingReadOnlyStream.Position setter not implemented while Seek is #16055

Closed
twsouthwick opened this issue Oct 16, 2020 · 4 comments · Fixed by #16083
Closed

LazyLoadingReadOnlyStream.Position setter not implemented while Seek is #16055

twsouthwick opened this issue Oct 16, 2020 · 4 comments · Fixed by #16083
Labels
Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention Workflow: This issue is responsible by Azure service team. Storage Storage Service (Queues, Blobs, Files)

Comments

@twsouthwick
Copy link

twsouthwick commented Oct 16, 2020

Describe the bug
I often use the Stream.Position property to set position on seekable streams. With the recent changes to enable seekability (#15032), we can now call Stream.Seek(..., SeekOrigin), but .Position fails.

Expected behavior
I would expect calls to .Position = x to work similarly to .Seek(x, SeekOrigin.Begin) as they do on other streams.

Actual behavior (include Exception or Stack Trace)
Throws NotSupportedException

To Reproduce
Steps to reproduce the behavior (include a code snippet, screenshot, or any additional information that might help us reproduce the issue)

var client = _container.GetBlobClient(plateName);
var stream = client.OpenRead();
stream.Position = 0;

Environment:

  • Name and version of the Library package used: Azure.Storage.Blobs 12.7.0-alpha.20201016.1
  • Hosting platform or OS and .NET runtime version (dotnet --info output for .NET Core projects): .NET Framework 4.8
  • IDE and version : Visual Studio 16.7.5
@ghost ghost added needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. customer-reported Issues that are reported by GitHub users external to the Azure organization. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Oct 16, 2020
@twsouthwick
Copy link
Author

@seanmcc-msft

@jsquire jsquire added Client This issue points to a problem in the data-plane of the library. needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team Service Attention Workflow: This issue is responsible by Azure service team. Storage Storage Service (Queues, Blobs, Files) labels Oct 17, 2020
@ghost ghost removed the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Oct 17, 2020
@jsquire
Copy link
Member

jsquire commented Oct 17, 2020

Thank you for your feedback. Tagging and routing to the team best able to assist.

@ghost
Copy link

ghost commented Oct 17, 2020

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @xgithubtriage.

@seanmcc-msft
Copy link
Member

@twsouthwick I can reproduce this issue, and we will have a fix out soon.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention Workflow: This issue is responsible by Azure service team. Storage Storage Service (Queues, Blobs, Files)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants