Eos: 4.2.0 i can't get actions

Created on 30 May 2018  路  8Comments  路  Source: EOSIO/eos

[btb@wallet-3 cleos]$ ./cleos transfer user tester "10 EOS" "a32"
executed transaction: 48e9df29d2f3132bac2b054e54322938e22f2bb5d650b35c1bdeaf1636ed8bb5 128 bytes 995 us

eosio.token <= eosio.token::transfer {"from":"user","to":"tester","quantity":"10.0000 EOS","memo":"a32"}

user <= eosio.token::transfer {"from":"user","to":"tester","quantity":"10.0000 EOS","memo":"a32"}

tester <= eosio.token::transfer {"from":"user","to":"tester","quantity":"10.0000 EOS","memo":"a32"}

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

# seq when contract::action => receiver trx id... args

[btb@wallet-3 cleos]$

Support

Most helpful comment

Hi @mlawand , you can start nodeos with the --contracts-console option to cause printed debug output to be sent to the console.

All 8 comments

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?

Was this page helpful?
0 / 5 - 0 ratings

Related issues

williamleecn picture williamleecn  路  3Comments

zxf969175364 picture zxf969175364  路  3Comments

sim31 picture sim31  路  3Comments

congnghebitcoin picture congnghebitcoin  路  3Comments

yashbhavsar007 picture yashbhavsar007  路  3Comments