nile setup fails

Hello team. I am trying to setup a private key alias as described in the README. but I get an error.

I am on a working installation of Nile on macOS (I followed the macOS specific installations) and I am able to compile and deploy. I created the venv, installed cairo-nile with pip, inited the project. I also create a .env file in the root directory with the YOLO=123 key.

> nile setup YOLO    

Traceback (most recent call last):
  File "/opt/homebrew/bin/nile", line 8, in <module>
    sys.exit(cli())
  File "/opt/homebrew/lib/python3.9/site-packages/click/core.py", line 1128, in __call__
    return self.main(*args, **kwargs)
  File "/opt/homebrew/lib/python3.9/site-packages/click/core.py", line 1053, in main
    rv = self.invoke(ctx)
  File "/opt/homebrew/lib/python3.9/site-packages/click/core.py", line 1659, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/opt/homebrew/lib/python3.9/site-packages/click/core.py", line 1395, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/opt/homebrew/lib/python3.9/site-packages/click/core.py", line 754, in invoke
    return __callback(*args, **kwargs)
  File "/opt/homebrew/lib/python3.9/site-packages/nile/cli.py", line 84, in setup
    Account(signer, network)
  File "/opt/homebrew/lib/python3.9/site-packages/nile/core/account.py", line 20, in __init__
    self.signer = Signer(int(os.environ[signer]))
  File "/opt/homebrew/Cellar/python@3.9/3.9.10/Frameworks/Python.framework/Versions/3.9/lib/python3.9/os.py", line 679, in __getitem__
    raise KeyError(key) from None
KeyError: 'YOLO'

I have no idea what is going wrong

[tserg]

I ran into the same issue using miniconda as my virtualenv on Linux. I was running nile from the root directory of the project folder (created from nile init) with the .env file in the root directory of the project folder.

I got around this by setting the key in console directly, eg. export KEY=1234.

[clacladev]

I am not sure exactly what it is. I had the same problem a while ago with a setup of nodejs and nextjs. A friend told me about this issue brut I me we investigated the actual why.

Claudio

On 8 Mar 2022, at 01:13, Andrew Fleming @.***> wrote:

But I understood what the issue is. On newer versions of macOS, I think they switched to IPv6 by default, from IPv4. This make processes fail to reach localhost but continue to work fine with 127.0.0.1. So simply changing to the gateway address fixes the issue.

@ccarnino great call with switching to 127.0.0.1. I did, however, test out your hypothesis and shut off IPv6 in favor of IPv4 on my Mac. Interestingly, localhost still returned BadRequest, so I’m not exactly sure why it’s behaving in such a way.

— Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android. You are receiving this because you were mentioned.