search

aragon / aragon-cli

CLI for creating and publishing Aragon apps
GNU General Public License v3.0
91 stars 79 forks source link

"dao acl grant" fails with "not a dao" #1825

Open TripleSpeeder opened 3 years ago

TripleSpeeder commented 3 years ago

🐛 Bug Report

I want to add publish permission for a new account to an APM repo.

I'm running this command: aragon --environment aragon:mainnet --use-frame dao acl grant 0x0f3b8ec182deee2381a9041e30f65f10098a3b91 0x4b214A2601D103FAbAA8e94f06E924960Bf4daeB 0x0000000000000000000000000000000000000000000000000000000000000001 0x7099b4d99876480fcc0ac46d7809b7287a946050

The command fails with this output:

  ✖ Executing grantPermission on 0x0f3b8ec182deee2381a9041e30f65f10098a3b91
    → Provided daoAddress is not a DAO
✖ Provided daoAddress is not a DAO

Have you read the Contributing Guidelines on issues?

To Reproduce

  1. Make sure frame is running
  2. Execute aragon --environment aragon:mainnet --use-frame dao acl grant 0x0f3b8ec182deee2381a9041e30f65f10098a3b91 0x4b214A2601D103FAbAA8e94f06E924960Bf4daeB 0x0000000000000000000000000000000000000000000000000000000000000001 0x7099b4d99876480fcc0ac46d7809b7287a946050
  3. See error

Context

Note that the repository was created using the dappnodesdk (dappnodesdk publish), so it seems to have some differences to repos created directly with aragon tooling.

There are other commands that work: aragon apm versions brightid-node.public.dappnode.eth --environment aragon:mainnet --use-frame or aragon apm info brightid-node.public.dappnode.eth 1.0.0 --environment aragon:mainnet --use-frame produce the expected output.

Mainnet or testnet?

Everything on Mainnet

Environment

Arch linux aragon cli version 7.1.6

welcome[bot] commented 3 years ago

Thanks for opening your first issue in aragonCLI! Someone will circle back soon ⚡

codynhat commented 3 years ago

I ran into a similar issue. I believe this is happening because the default Aragon ETH endpoint is having issues (wss://mainnet.eth.aragon.network/ws)

I was able to solve this by using my own endpoint. For example, using Frame and adding --ws-rpc ws://localhost:1248. Or using your own Infura endpoint would work.