-
Notifications
You must be signed in to change notification settings - Fork 111
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
[RSDK-9655] skip reflection for discovery service and add fake discovery #4697
Conversation
module/module_test.go
Outdated
// discoveryConf := &v1.ComponentConfig{ | ||
// Name: "mydis1", | ||
// Api: "rdk:service:discovery", | ||
// Model: "acme:demo:mydiscovery", | ||
// } |
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.
delete?
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.
o whoops
} | ||
// due to how tagger is setup in the api we cannot use reflection on the discovery service currently | ||
// for now we will skip the reflection step for discovery until the issue is resolved. | ||
if api != discovery.API { |
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.
did you check that the test would fail if this block is not in?
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.
yep we get theSymbol Not Found
error
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.
Should we add a ticket and a TODO?
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.
ya that would be ideal
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.
added a ticket+TODO comment https://viam.atlassian.net/browse/RSDK-9718
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.
All my comments are nits, LGTM dont have much to say about the module logic
} | ||
// due to how tagger is setup in the api we cannot use reflection on the discovery service currently | ||
// for now we will skip the reflection step for discovery until the issue is resolved. | ||
if api != discovery.API { |
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.
Should we add a ticket and a TODO?
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.
LGTM!
Co-authored-by: martha-johnston <[email protected]> Co-authored-by: randhid <[email protected]>
https://viam.atlassian.net/browse/RSDK-9655
in order to get around the tagger/proto reflection issue we saw when using the discovery service with modules, we are now skipping the reflection step for discovery apis, and relying on the builtin fake discovery service to register the proto definition.
tested with a module that implements a discover service and some client code