Genie Discord forum
I am trying to start and build a new project on Vscode, unfortunately, the starting process seems to be stuck in a loop.
Would you like to attempt again? Terminate the Julia/VSCode process from the activity monitor/task manager. What is the version of Julia? What is the version of GenieBuilder?
Hi, I am experiencing exctly this same issue.
In my case, it appears that Genie Builder does not know where to look for julia
julia: command not found
I am using linux and have added julia to the $PATH variable
Can anyone tell me where GB expects to find Julia?? I can add a static link to my julia bin
😳 admittedly, I am very new to Julia.. I have used it for a couple of hours throughout the past two weeks... so maybe I did something out-of-the-ordinary during my installation (like install julia in a folder in my home drive, rather than /usr or /etc ... or somewhere "more special")
I have no problem running other julia in VScode... so I doubt it's a problem 🥺
... yes, I have done the basic troubleshooting like restart VS Code after installation of the extension.... and yes, I removed the extension and reinstalled it.
This snippet shows that VSCode has the correct path... so I'm not sure if it is a simple configuration issue, or something else 😞
@GenerallyClueless what OS are you on? It appears that Julia is not in your PATH variable, hence why it is not found when Genie Builder runs the startup command. To confirm that this is the issue, type "julia" in a terminal
If you're on Linux or Mac, you'll have to add your Julia install to the path by editing your profile config (.bashrc or .zshrc)
Yup @Pere I had not correctly added julia to my path. Previously, I had added it to the path without using quotes 😳 😳 It is working now.
Thank you for your advice. I had even gone as far as editing the /etc/environment file ... but for some reason this path was never reflected in the VSC terminal... until I added it using PATH="path to julia bin folder:$PATH" <---- the " " are very important here‼️
🏆 thanks again @Pere
@mcheart if you had not resolved your server startup issue, this might help?