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

[storage] retry on 500 OperatationTimedout is not safe #32865

Open
jeremymeng opened this issue Feb 4, 2025 · 1 comment
Open

[storage] retry on 500 OperatationTimedout is not safe #32865

jeremymeng opened this issue Feb 4, 2025 · 1 comment
Assignees
Labels
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)

Comments

@jeremymeng
Copy link
Member

jeremymeng commented Feb 4, 2025

See related Go issue: Azure/azure-sdk-for-go#24027 (comment)

current code:

if (statusCode === 503 || statusCode === 500) {

@jeremymeng jeremymeng added Client This issue points to a problem in the data-plane of the library. Storage Storage Service (Queues, Blobs, Files) labels Feb 4, 2025
@jeremymeng jeremymeng assigned eatkimchee and EmmaZhu and unassigned eatkimchee Feb 4, 2025
@github-actions github-actions bot added 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. labels Feb 4, 2025
Copy link

github-actions bot commented Feb 4, 2025

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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)
Projects
None yet
Development

No branches or pull requests

3 participants