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

check for GWs going inactive, when connected to a stream. Reactivate if true #52

Merged
merged 1 commit into from
May 20, 2022

Conversation

andymck
Copy link
Contributor

@andymck andymck commented May 20, 2022

Adds support to reactive a GW which has gone inactive whilst connected to a stream. Prior to this change reactivation check would only occur during the initial connect to a stream, now if that connection stays up for a long time we will run periodic activity checks and keep the GW within the active window.

This is to address community reported issues where GWs which are in loosely populated hex are getting excluded from POC due to no active POC activity ( ie no beaconing or witness reports )

@andymck andymck force-pushed the andymck/handle-gws-going-inactive branch 3 times, most recently from 2706407 to 5fcd421 Compare May 20, 2022 17:41
@andymck andymck force-pushed the andymck/handle-gws-going-inactive branch from 5fcd421 to 200f580 Compare May 20, 2022 17:43
@andymck andymck marked this pull request as ready for review May 20, 2022 17:45
@madninja madninja merged commit 5ac56b3 into master May 20, 2022
@madninja madninja deleted the andymck/handle-gws-going-inactive branch May 20, 2022 22:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants