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
When running the export command wasm contracts are not found and the process panics. The whole export process fails at this point. This is due to the home path of wasm keeper not being set correctly during the export setup.
Summary of Bug
When running the
export
command wasm contracts are not found and the process panics. The whole export process fails at this point. This is due to the home path of wasm keeper not being set correctly during the export setup.provenance/cmd/provenanced/cmd/root.go
Line 296 in 1e0747d
We are setting the home directory to
""
in the code above.The correct home path should match how the wasmd keeper is being setup in the app.go
provenance/app/app.go
Line 422 in 463e4e1
Proposed fix would be to setup the wasm home path from command parameter or default to
""
Version
v1.5.0
Steps to Reproduce
With a chain that has wasm contracts loaded.
1.)
provenanced export -t --home <homedir>
Produces:
panic: Error calling the VM: Cache error: Error opening Wasm file for reading: No such file or directory (os error 2)
For Admin Use
The text was updated successfully, but these errors were encountered: