Skip to content
This repository has been archived by the owner on Jan 14, 2022. It is now read-only.

Fail on failed blockchain download - Closes #32 #175

Merged
merged 3 commits into from
Oct 19, 2018
Merged

Conversation

Nazgolze
Copy link
Contributor

Closes #32

Well, this covers the example in the issue where it fails to download.
If psql fails, that should be caught. If gunzip fails, if psql somehow succeeds, that will still register as a success as pipefail isn't set

@fchavant
Copy link
Contributor

fchavant commented Oct 18, 2018

If gunzip fails, if psql somehow succeeds, that will still register as a success as pipefail isn't set.

We could set pipefail (for this part of the code)

packaged/lisk.sh Outdated
@@ -337,7 +339,7 @@ check_pid() {
}

lisk() {
node "$(pwd)/bin/lisk"
node "$PWD/bin/lisky"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Commander's binary is called lisk

  * Improve initial cd
  * Also s/[$](pwd)/$PWD/g

Pipefail around gunzip (lisk.sh isn't ready for anything resembling strict mode just yet)

Change checkmarks to +'s

Change $USER = root check to $UID = 0 check
@fchavant
Copy link
Contributor

fchavant commented Oct 19, 2018

The plus signs are a little confusing when using set -x. How about [+] instead? or [ok] at the end of a line?

Which presented the opportunity to make X -> [-]
@fchavant fchavant changed the title Fail on failed blockchain download Fail on failed blockchain download - Closes #32 Oct 19, 2018
@Nazgolze Nazgolze merged commit 7559899 into 0.3.8 Oct 19, 2018
@Nazgolze Nazgolze deleted the 32-restore-fail branch October 19, 2018 12:34
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants