[btb@wallet-3 cleos]$ ./cleos transfer user tester "10 EOS" "a32"
executed transaction: 48e9df29d2f3132bac2b054e54322938e22f2bb5d650b35c1bdeaf1636ed8bb5 128 bytes 995 us
warning: transaction executed locally, but may not be confirmed by the network yet
[btb@wallet-3 cleos]$
[btb@wallet-3 cleos]$
[btb@wallet-3 cleos]$ ./cleos get actions user
[btb@wallet-3 cleos]$
Now, by default, a filter is for actions, this is necessary to save RAM BP. To see the actions, you need to restart the node with the -f option.
-f [ --filter-on ] arg Track actions which match
receiver:action:actor. Actor may be
blank to include all. Receiver and
Action may not be blank
For example:
./nodeos --plugin eosio::chain_api_plugin --producer-name eosio --config-dir c --data-dir d --delete -e --plugin eosio::history_api_plugin --filter-on "*"
i have the same issue, even with the filter its not working i am getting the same error message
warning: transaction executed locally, but may not be confirmed by the network yet
warning: transaction executed locally, but may not be confirmed by the network yet
@mlawand , this means success.
@spartucus i am not getting any response when i push an action through cleos
The response how to perform after an action is in your contract. In a some situations, there're no output prints.
@spartucus i have included in my contract the print functionality to see an output, is there should always be an output. but it is not showing
Hi @mlawand , you can start nodeos with the --contracts-console option to cause printed debug output to be sent to the console.
Is this issue solved?
Most helpful comment
Hi @mlawand , you can start nodeos with the
--contracts-consoleoption to cause printed debug output to be sent to the console.