-
Notifications
You must be signed in to change notification settings - Fork 21
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
Modeled Coverage - Phase 1 #578
Conversation
Co-authored-by: Jeff Grunewald <jeff.grunewald@gmail.com>
Co-authored-by: Jeff Grunewald <jeff.grunewald@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
only questions left are about comments still in the code; assuming that's stuff intended to be uncommented in phase 3 please ignore/resolve
@@ -13,7 +13,7 @@ use futures::{ | |||
stream::{Stream, StreamExt, TryStreamExt}, | |||
TryFutureExt, | |||
}; | |||
use h3o::LatLng; | |||
// use h3o::LatLng; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
// use h3o::LatLng; |
not needed or will this come into play in phase 3?
@@ -459,6 +465,7 @@ async fn validate_heartbeat( | |||
if coverage.max_distance_km(latlng) > max_distance { | |||
return Ok((cell_type, proto::HeartbeatValidity::TooFarFromCoverage)); | |||
} | |||
*/ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
you said "removed" did you mean more specifically that we should be invalidating these in phase 3 so this is only temporarily commented out or was this intended to be deleted once it successfully compiled or something?
No description provided.