Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
".venv36" not existed on vagrant VM
See original GitHub issue[Issue symptom] Today I cloned the repo and tried the vagrant VM with vagrant up followed by vagrant ssh.
When logged into the VM, there’s an error line printed out with regard to non-existent .venv36 directory:
-bash: .venv36/bin/activate: No such file or directory
[Quick analysis] In the Vagrantfile there’s one line that attempts to put the virtual env activation command into .bashrc file. However the virtual env was not actually created as part of the Vagrantfile.
[Env] Though the issue feels like platform-independent, just in case it matters I spinned up the vagrant VM under a macOS 10.15.7 environment.
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@jorisroovers thanks for making the changes. I tried to spin up a Ubuntu 20.04 VM using the latest Vagrantfile, and it worked perfectly. I’m going to close this issue.
Should be fixed on
mainbranch now. I took the opportunity to upgrade the Vagrant Box to 20.04 at the same time. Appreciate if you can let me know if you end up trying this out, will otherwise close this issue soon.