-
-
Notifications
You must be signed in to change notification settings - Fork 102
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
AdaptiveTransferSpeed is not adaptive #122
Comments
Thanks for the extensive bug report and the fix! It seems to work great, I'll try to get a new release out within a few days |
And the new release is online :) You can try 3.30.2 |
Something seems to have gone wrong with the pull request (#123) that fixes this issue. The change is not visible in master or develop. |
I also came to report the same bug and the same fix. |
This issue has been fixed before but apparently it's broken again somehow. For some reason the previously added tests didn't cover this so I'll add more tests to make sure it won't happen again. It seems like #207 is a duplicate of this. I'll get it working again as soon as possible :) |
@martinprikryl did you run into the issue of #207 as well or is it broken for you in a different case? When I run |
No, I do not get that problem. For me all widgets work. It's just that If I apply his fix to the module, everything works as I need. |
I could swear I've re-added this code before... either way, it's back again :) Now the hard part... creating a test for this case ;) |
I've finally been able to write a test that consistently works across all testing platforms so I'll create a new release now :) |
Description
AdaptiveTransferSpeed shows the same values as TransferSpeed, it does not calculate the values over the last X samples.
The example code below shows when finished:
the expected Adaptive Transfer Speed with
sleep(0.1)
for the last 100 iterations would be10.0 B/s
The reason is
FileTransferSpeed
is used to print Adaptive Transfer Speed but calculated and passed parameters value and total_seconds_elapsed are ignored because the keys exist in data.Proposed Fix
Change the code in
FileTransferSpeed.__call__
toor to be have the same code as in
ETA.__call__
to:Code
Copied from examples and added FileTransferSpeed widget
Versions
The text was updated successfully, but these errors were encountered: