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

Bits/sec rate fails to compute correct throughput after editing existing streams. #240

Closed
zeus10000 opened this issue Jan 11, 2018 · 0 comments

Comments

@zeus10000
Copy link

commented Jan 11, 2018

Steps to reproduce the issue:

  • Create a new traffic stream with 1000 packet/sec. (Note: enter the packets/sec value without commas).
  • Save the traffic stream.
  • Edit the same traffic stream by increasing the packets/sec rate by adding a 0 to the trailing end (Note, this time the packets/sec value displays with comma).

You should see that the bits/sec rate displays as 0 rather than showing the correct traffic rate. Removing the comma resolves the issue and correct bits/sec value is displayed.

@pstavirs pstavirs added the bug label Jan 13, 2018

@pstavirs pstavirs closed this in c673141 Sep 14, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.