fix(app): make shell remote check lazier to avoid spurious assertions #3895
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.
overview
In investigating @IanLondon's reports of a circular-dependency based assertion, I found that the root of the problem was an assertion firing for a missing remote during import (i.e. before the code was actually running).
I'm not 100% sure of the Electron and/or webpack mechanics that are allowing that assertion to be hit, but moving the assertion to property access time fixes the issue.
@IanLondon:
app/src/protocol/selectors.js
creates a logger (viaapp/src/protocol/protocol-data.js
), which relies on theremote
module to send logs over to the desktop shell to save to a file. Rebasing #3891 over this branch fixed the issues for me.changelog
review requests
AssertionError
s in the console in normal operationAssertionError
s in the console when feat(app): display custom labware on deckmap #3891 is layered over this branch