- 
          
- 
                Notifications
    You must be signed in to change notification settings 
- Fork 431
fix: discovery cleanup and watchers continuity upon core install #2062
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
Conversation
2df98f1    to
    6074df3      
    Compare
  
    | Codecov ReportPatch coverage:  
 Additional details and impacted files@@            Coverage Diff             @@
##           master    #2062      +/-   ##
==========================================
+ Coverage   36.57%   36.70%   +0.12%     
==========================================
  Files         229      229              
  Lines       19630    19646      +16     
==========================================
+ Hits         7180     7211      +31     
+ Misses      11605    11592      -13     
+ Partials      845      843       -2     
 Flags with carried forward coverage won't be shown. Click here to find out more. 
 ... and 1 file with indirect coverage changes Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report in Codecov by Sentry. | 
7e6f932    to
    02f6d35      
    Compare
  
    43cdaff    to
    e79909b      
    Compare
  
    Co-authored-by: Cristian Maglie <c.maglie@arduino.cc>
Co-authored-by: Cristian Maglie <c.maglie@arduino.cc>
262904c    to
    61ac16a      
    Compare
  
    …uino#2062) Co-authored-by: Cristian Maglie <c.maglie@arduino.cc>
Please check if the PR fulfills these requirements
See how to contribute
before creating one)
our contributing guidelines
UPGRADING.mdhas been updated with a migration guide (for breaking changes)What kind of change does this PR introduce?
It introduces a teardown of the running discovery processes when installing a new core, restarting them after to keep the watchers receiving events.
What is the current behavior?
When a new core is installed the running discovery processes are not terminated. Alive watchers freeze and don't receive any new events.
What is the new behavior?
When a new core is installed all running discovery processes are terminated, also those not interested by the update. They are restarted after the installation completed and watchers are reconnected to the new stream of events.
Connected boards face first a "remove" and then an "add" event.
Does this PR introduce a breaking change, and is titled accordingly?
Other information
Fixes #1960
Fixes #1588