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
Renamed to genesis.json, and placed in the config/ path of the node, the output of fetchd validate-genesis genesis.json should not list any errors. A new, fresh node should be able to start syncing from this genesis file.
Current Behavior
The output of `fetchd validate-genesis is:
Error: error validating genesis file genesis.json: unknown field "max_wasm_code_size" in types.Params
Usage:
fetchd validate-genesis [file] [flags]
Flags:
-h, --help help for validate-genesis
Global Flags:
--home string directory for config and data (default "/home/fetchd/.fetchd")
--log_format string The logging format (json|plain) (default "plain")
--log_level string The logging level (trace|debug|info|warn|error|fatal|panic) (default "info")
--trace print out full stack trace on errors
When starting the node, this check is also done, and the node crashes with panic message.
The panic does not occur on a node that already has chain data. The output of fetchd validate-genesis genesis.json does show the error there however.
To Reproduce
See above.
Context
Fetchd 0.10.5. In the above case the synced node is Ubuntu 20.04 and the fresh node is Ubuntu 22.04. I think it's unlikely that the OS version difference would cause this. I will manually get chain data to the fresh node and test whether the panic then still occurs and update this issue to confirm.
Failure Logs
No response
The text was updated successfully, but these errors were encountered:
Prerequisites
Expected Behavior
Using the latest genesis file: https://github.com/fetchai/genesis-fetchhub/blob/main/fetchhub-4/data/genesis_migrated_5300200.json
Renamed to
genesis.json
, and placed in theconfig/
path of the node, the output offetchd validate-genesis genesis.json
should not list any errors. A new, fresh node should be able to start syncing from this genesis file.Current Behavior
The output of `fetchd validate-genesis is:
When starting the node, this check is also done, and the node crashes with panic message.
Partial log showing the error:
The panic does not occur on a node that already has chain data. The output of
fetchd validate-genesis genesis.json
does show the error there however.To Reproduce
See above.
Context
Fetchd 0.10.5. In the above case the synced node is Ubuntu 20.04 and the fresh node is Ubuntu 22.04. I think it's unlikely that the OS version difference would cause this. I will manually get chain data to the fresh node and test whether the panic then still occurs and update this issue to confirm.
Failure Logs
No response
The text was updated successfully, but these errors were encountered: