You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 2, 2022. It is now read-only.
When running nodeos --version or nodeos --help, the process exits with a non-zero exit status (-1 in C++, 255 in BASH). Conventionally, this means the program has encountered an error. This will cause shell environments or scripts with -e set to exit with a failure.
This is happening because main() calls app:initialize() which prints the requested information. It returns false because nodeos was not initialized, but main() takes this as an initialization failure.
Looking at this with arhag, we also believe the FIXED_REVERSIBLE and EXTRACTED_GENESIS cases should return EXIT_SUCCESS.
When running
nodeos --version
ornodeos --help
, the process exits with a non-zero exit status (-1 in C++, 255 in BASH). Conventionally, this means the program has encountered an error. This will cause shell environments or scripts with-e
set to exit with a failure.This is happening because
main()
callsapp:initialize()
which prints the requested information. It returnsfalse
because nodeos was not initialized, butmain()
takes this as an initialization failure.Looking at this with arhag, we also believe the
FIXED_REVERSIBLE
andEXTRACTED_GENESIS
cases should returnEXIT_SUCCESS
.Steps to Reproduce the Issue
In BASH:
Note that all supported versions of nodeos are effected at the time this issue was created.
Recommended Solution
Return
EXIT_SUCCESS
in these four cases, which is equal to zero.The text was updated successfully, but these errors were encountered: