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

[BUG] BlobClient cannot read blobs with # characters in name #40925

Closed
jkdmyrs opened this issue Dec 29, 2023 · 4 comments
Closed

[BUG] BlobClient cannot read blobs with # characters in name #40925

jkdmyrs opened this issue Dec 29, 2023 · 4 comments
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

@jkdmyrs
Copy link

jkdmyrs commented Dec 29, 2023

Library name and version

Azure.Storage.Blobs 12.19.1

Describe the bug

The BlobClient incorrectly truncates blob file names if the name contains a # character.

Expected behavior

The following code should output:

example#test.json
example.json

Code:

using Azure.Identity;
using Azure.Storage.Blobs;

BlobClient blobClient1 = new(new Uri("https://example.blob.core.windows.net/example/exmple#test.json"), new DefaultAzureCredential());
Console.WriteLine(blobClient1.Name);

BlobClient blobClient2 = new(new Uri("https://example.blob.core.windows.net/example/exmple.json"), new DefaultAzureCredential());
Console.WriteLine(blobClient2.Name);

Actual behavior

The code outputs:
example
example.json

example#test.json is truncated at the # character.

Reproduction Steps

  • create a .net 8 console app
  • install Azure.Storage.Blobs (and Azure.Identity)
  • run this code:
using Azure.Identity;
using Azure.Storage.Blobs;

BlobClient blobClient1 = new(new Uri("https://example.blob.core.windows.net/example/example#test.json"), new DefaultAzureCredential());
Console.WriteLine(blobClient1.Name);

BlobClient blobClient2 = new(new Uri("https://example.blob.core.windows.net/example/example.json"), new DefaultAzureCredential());
Console.WriteLine(blobClient2.Name);

Environment

No response

@github-actions github-actions bot added 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-triage Workflow: This issue needs the team to triage. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Storage Storage Service (Queues, Blobs, Files) labels Dec 29, 2023
@jkdmyrs
Copy link
Author

jkdmyrs commented Dec 29, 2023

Seems like this was fixed previously... is this a regression?
#11602

@jsquire jsquire added Service Attention Workflow: This issue is responsible by Azure service team. needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team and removed needs-team-triage Workflow: This issue needs the team to triage. labels Dec 30, 2023
Copy link

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

@amnguye
Copy link
Member

amnguye commented Jul 15, 2024

Will be resolved by #44941

after it releases with v12.21.0 of Azure.Storage.Blobs

@jkdmyrs
Copy link
Author

jkdmyrs commented Jul 15, 2024

@amnguye thanks!

@jkdmyrs jkdmyrs closed this as completed Jul 15, 2024
@github-actions github-actions bot locked and limited conversation to collaborators Oct 13, 2024
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

No branches or pull requests

3 participants