sapphire-dev: deposit test mnemonic, core-22.2.11, optionally use single compute note #413
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.
This makes 4 changes:
oasis-deposit
-test-mnemonic
flag tooasis-deposit
which uses thetest test test ... junk
mnemonic-to
flag working with a mnemonic via GitHub workflow (no combination of quoting or escaping would let me pass a quoted parameter with spaces in it!)sapphire-dev
(reduces CPU usage)Additionally there was some weirdness with PostgreSQL I had when building the
sapphire-dev
container that I didn't have early last week and was unable to find the root cause. After installing the postgresql package some of the permissions were wrong which prevented it from starting. Runningchown
wouldn't persist acrossRUN
statements, meaning I had to prefix the/etc/init.d/postgresql start
command withchown
, and then run it again instart.sh
upon startup. I'm using Docker20.10.25-0ubuntu1~22.04.1
.Re #411: using 1 compute node instead of 2 doesn't significantly affect startup time, but it does help battery life. Am still (slowly) investigating idle CPU usage and startup time (wait-node)
The startup process now looks like: