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

GH-40: MAX_PING_TIME_INTERVAL should be 24 hours, 24 not minutes #40

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

nkljajic
Copy link
Collaborator

@nkljajic nkljajic commented Apr 7, 2024

In ver_1.0.0 intended value was supposed to be 24 hours, as indicated by its comment. During refactoring this comment was lost, so value incorrectly remained 24 minutes. Interval of 24 minutes to ping failing device seems arbitrary and too short.

Copy link
Collaborator

@rzr rzr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM I will test it until approve

Feel free to also pick this change to trigger tests:

#42

nkljajic added a commit to nkljajic/UnifySDK that referenced this pull request Apr 24, 2024
@rzr
Copy link
Collaborator

rzr commented Apr 24, 2024

Please rebase you should see only one commit at:

https://github.com/SiliconLabs/UnifySDK/pull/40/commits

…inutes

In ver_1.0.0 intended value was supposed to be 24 hours, as indicated by its comment.
During refactoring this comment was lost, so value incorrectly remained 24 minutes.
Interval of 24 minutes to ping failing device seems arbitrary and too short.

Signed-off-by: Nenad Kljajic <nkljajic@control4.com>
@nkljajic nkljajic force-pushed the bugfix/GH-40-fix-failing-node-max-ping-interval branch from ea6217f to d04f193 Compare April 24, 2024 10:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants