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

eosio.system got fatal error! #287

Closed
dawnFromDark opened this issue Jul 13, 2019 · 5 comments
Closed

eosio.system got fatal error! #287

dawnFromDark opened this issue Jul 13, 2019 · 5 comments

Comments

@dawnFromDark
Copy link

the master branch got a fatal error ,it can not be deployed on chain ,the error message is following:

root@ubuntu:/home/time/eosio.contracts/build/contracts# cleos set contract eosio eosio.system/
Reading WASM from /home/time/eosio.contracts/build/contracts/eosio.system/eosio.system.wasm...
Publishing contract...
Error 3070000: WASM Exception
Error Details:
env.is_feature_activated unresolveable

my nodeos version is 1.8.1 and eosio.cdt is 1.6.1, may you tell me what happend about this contract?

@dawnFromDark
Copy link
Author

dawnFromDark commented Jul 13, 2019

the contract which got error is eosio.system, may you fix it?

@dawnFromDark
Copy link
Author

do you have any body to solve this issue ?

@lsf1001
Copy link

lsf1001 commented Aug 27, 2019

I also met this problem. How did you solve it ,eosio v1.8.1 eosio.contracts v1.7.0-rc1

@lsf1001
Copy link

lsf1001 commented Aug 27, 2019

@dawnFromDark

@MrToph
Copy link

MrToph commented Aug 28, 2019

@lsf1001 Running the step described here in the Preactivate feature
section
solved the issue for me.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants