#1366 Buffer events from BoardListWatchResponse
#1379
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
Hopefully, the board reconnecting issue is fixed for the
teensy
portprotocol
.Change description
DetectedPort
'add'
/'remove'
events retrieved from theBoardListWatchResponse
es to calculate a correctAttachedBoardsChangeEvent
for the IDE2 frontend. If a board was detected to be removed and added in a short period, the discovery service would treat the events as a NOOP.InitRequest
) the gRPC core client after the library/platform index updates. This will ensure that already discovered boards/ports won't be re-discovered. The force stop/start guard can be removed as [breaking] daemon: Fix concurrency and streamline access to PackageManager arduino-cli#1828 solved it on the CLI side, so no external guard is required from IDE2.Other information
Closes #1366
Reviewer checklist