-
Notifications
You must be signed in to change notification settings - Fork 178
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
refactor(modules): return has update for unexpected module fw filename #14712
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## edge #14712 +/- ##
=======================================
Coverage 67.20% 67.20%
=======================================
Files 2495 2495
Lines 71595 71593 -2
Branches 9076 9076
=======================================
- Hits 48114 48113 -1
+ Misses 21336 21335 -1
Partials 2145 2145
Flags with carried forward coverage won't be shown. Click here to find out more.
|
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.
Looks good to me!
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, thanks!
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!
Overview
When we flash local firmware changes to a module using an ST-Link, the file produced will have the usual firmware filename for the module, except with a commit hash amended in the middle of it.
Currently, having the filename altered like this causes the robot server not to recognize that a module is present at all. Instead, this change allows the app to reflect that the module is there and offer an available update.
Changelog
InvalidVersion
error for both current and available device versions