stefanzarembinski

I guess that you need to have eosio system contracts installed in order to be able to refer to the `eosio.code` permission. Within several days I will workout the issue.

Sorry, I see that my previous comment is stupid. Nevertheless, I will solve the issue.

Evidently, EOSIO does not like giving permissins to itself. Change `str(alice)` to `carol`. You do not need to convert account object to string in the `actor` field. The conversion is...

Today, we are going to publish a new edition of EOSFactory. There is there a folder `archive`, see the `arbitration` contract example. In the `tests` folder, you can find the...

I use the `eosio.code` permission there. Please, try to compare our case with yours one. I will help you, if comparison does not solve the issue.

There means https://github.com/tokenika/eosfactory/tree/master/archive/arbitration

Let us consider the command: ``` alice.set_account_permission( Permission.ACTIVE, { "threshold": 1, "keys": [], "accounts": [ { "permission": { "actor": alice, "permission": "active" }, "weight": 1 }, { "permission": { "actor":...

This is your case but `hello_world` is replaced with `eosio_token`. ``` import sys, os import eosfactory.core.config as config from eosfactory.eosf import * verbosity([Verbosity.INFO, Verbosity.OUT, Verbosity.DEBUG]) #CONTRACT_WORKSPACE = os.path.join(config.eosf_dir(), "contracts/hello_world") CONTRACT_WORKSPACE...

See the previous two comments. Here comes the third one. You say: >>BTW, when using cleos, if the permission (alice@active is presented) is correct and key is presented The main...

I am glad to see good news from you. Thank you for your persistance. I will accept your advice. Please, elaborate it more: now I am overworked so much...