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.
I have a setup of multi-node of 4 peers blockchain. Blockchain is running, few days before I deployed the smart contract and using it to save data on the blockchain. Now, I did some changes to the smart contract by changing the multi-index table name. Trying to compile and deploy this smart contract again. On the local machine, it gets compiled successfully. But on the server-side, the compilation is not getting finished with no error. It looks stuck (blinking cursor). What may be the reason? Let me know if anybody needs more information. Compilation command:
Smart contracts are in hpp files saved in /usr/opt/eosio.cdt/1.6.3/include/contracts/ and included in smart contract as header files. Smart contract is:
I've been having a similar error manifesting on github workflow runs, I'm developing a python pytest plugin and have CI setup, but when adding non trivial smart contracts, eosio-cpp just hangs.
I have a setup of multi-node of 4 peers blockchain. Blockchain is running, few days before I deployed the smart contract and using it to save data on the blockchain. Now, I did some changes to the smart contract by changing the multi-index table name. Trying to compile and deploy this smart contract again. On the local machine, it gets compiled successfully. But on the server-side, the compilation is not getting finished with no error. It looks stuck (blinking cursor). What may be the reason? Let me know if anybody needs more information. Compilation command:
And
Smart contracts are in hpp files saved in
/usr/opt/eosio.cdt/1.6.3/include/contracts/
and included in smart contract as header files. Smart contract is:Also when I tried multiple times, temporary
wasm
files get generated likecommoncontract.wasm.tmp3f5048b
. Please help.The text was updated successfully, but these errors were encountered: