Correct swapped input/output and add error handling

[Virsacer]

Hi,
maxInputRate and maxOutputRate can be different so they should be used accordingly.
Also added some checks to prevent errors.

[codeautopilot]

PR summary

This Pull Request addresses a bug in the InterfaceSubsystem.pm file where the maxInputRate and maxOutputRate were incorrectly swapped in calculations. The changes ensure that the correct rate is used for input and output operations. Additionally, error handling has been improved by adding checks to prevent potential errors when maxInputRate or maxOutputRate are undefined or zero, ensuring robustness in performance data calculations.

Suggestion

Consider adding unit tests to verify that the changes correctly handle scenarios where maxInputRate or maxOutputRate are undefined or zero. This will help ensure that the error handling logic works as intended and prevent future regressions.

Disclaimer: This comment was entirely generated using AI. Be aware that the information provided may be incorrect.

Current plan usage: 0.73%

Have feedback or need help?
Discord
Documentation
[email protected]