-
Notifications
You must be signed in to change notification settings - Fork 6
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
Add startup binary management #40
Conversation
4ad3f97
to
32a968d
Compare
// TODO: better error message with troubleshooting tips here | ||
child: _initBinariesError != null | ||
? SailText.primary24('Ran into unrecoverable error on startup: $_initBinariesError') | ||
: loadingIndicator(), |
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.
@octobocto input appreciated. When this branch is triggered we're at a unrecoverable state, and most likely it's the programmer's fault. Shouldn't happen with the end user, but if it happens they should get a good error message
// TODO: correct? | ||
return '.ethereum'; |
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.
ping test this
You should really rebase on master before continuing work here… |
1. Tear out some unecesary OOP crazities 2. Rework the RPC clients such that they don't read RPC credentials on creation, but are passed them as a parameter. We need to construct the clients on startup after reading configuration files, while showing meaningful messages along the way
32a968d
to
355b8e2
Compare
On startup, we load the
drivechaind
binary from assets, and launch it. The loading spinner is shown until we get a successful connection. In the case of an error, we display a big and ugly error message that it's impossible to get through.TODO:
Load dynamic assets based on platform + architecture