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

Rate limit prevents download #7994

Closed
3 tasks done
ScottOfford opened this issue Jun 10, 2024 · 1 comment
Closed
3 tasks done

Rate limit prevents download #7994

ScottOfford opened this issue Jun 10, 2024 · 1 comment
Labels
❔ external Root cause of this issue is in another component, product, or service

Comments

@ScottOfford
Copy link

Preflight Checklist

Storage Explorer Version

1.34.0

Regression From

No response

Architecture

x64

Storage Explorer Build Number

20240523.2

Platform

Windows

OS Version

Windows 10

Bug Description

When enabling a download speed cap, the download fails to start

Steps to Reproduce

  1. Launch Storage Explorer
  2. Navigate to Edit > Settings
  3. Click on Transfers and scroll down to Maximum Transfer Rate
  4. Set this to any value (in my case, 25Mbps)
  5. Connect to a file share storage account
  6. Trigger a download

Actual Experience

Transfer immediately fails
image

"request size greater than pacer target. When Enqueueing chunk." is listed in the AzCopy Log File

Expected Experience

File is downloaded, adhering to the transfer limit defined in the settings.

Additional Context

I have seen this mentioned in the issue: Azure/azure-storage-azcopy#2380

@craxal craxal added the ❔ external Root cause of this issue is in another component, product, or service label Jun 10, 2024
@craxal
Copy link
Contributor

craxal commented Jun 10, 2024

@ScottOfford Yeah, this is a known issue in AzCopy, and they plan on fixing this in a future version. In the meantime, can you bump up the rate limit to a value that works?

@craxal craxal closed this as not planned Won't fix, can't repro, duplicate, stale Jun 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
❔ external Root cause of this issue is in another component, product, or service
Projects
None yet
Development

No branches or pull requests

2 participants