pkg ]add command never returns - installation

New to julia. When I try to add a pkg via a julia prompt, the add command never returns to the command prompt in powershell. Same behavior in the default console in the windows julia install.
(v1.3) pkg> add Gadfly
Cloning default registries into `C:\Users\omort\.julia`
Cloning registry from "https://github.com/JuliaRegistries/General.git"
Fetching: [========================================>] 99.9 %
The gadfly install docs say to hit delete to return to the prompt, but that doesn't seem to work for me.
Seems to work ok in bash on Ubuntu. What am I missing?
Following David Varela's suggestion below:
(v1.3) pkg> registry update General
[ Info: registry `General` not found.
However - running a bare registry update did push the command forward, though it errored out:
(v1.3) pkg> add Gadfly
Cloning default registries into `C:\Users\omort\.julia`
Cloning registry from "https://github.com/JuliaRegistries/General.git"
ERROR: SystemError: opening file "C:\\Users\\omort\\.julia\\registries\\General\\Registry.toml": No such file or directory
Stacktrace:[...]
The ~/.julia directory exists, but that toml file does not.
Note: I was able to get this working effortlessly on a second Windows laptop this morning, so it's something specific to this install.

Related

No pyvenv.cfg file in poetry installation (brand new computer)

I have a brand-spanking new machine (Windows 10 Pro). I have never run any python ever on it. I have a project which I have downloaded which uses poetry which is some sort of environment configuration thing which I have also never heard of.
I realized upon looking at the code that I needed this poetry thing, so I googled how to install it. What I found was this command:
(Invoke-WebRequest -Uri https://install.python-poetry.org -UseBasicParsing).Content | python -
This command was to be run from Powershell, however it failed initially because Python was not found. I looked inside the pyproject.toml file and saw that it was dependent on python 3.8 so I went to the Microsoft Store and installed this version. That went well. I then retried the command listed above to install poetry.
This failed and referenced an error log file which I found and opened. The file is pretty short, all it says is:
No pyvenv.cfg file
Traceback:
File "<stdin>", line 919 in main
File "<stdin>", line 552 in run
Upon googling for this error/problem I have found a couple of references, but they are not relevant for my use case. Rather than trying things randomly, I am wondering if someone can just point me in the right direction to resolve this.
Looks like this guy figured it out already:
python poetry installation failed on Windows 10 - no pyvenv.cfg file
Basically go to this site: https://www.python.org/downloads/ and reinstall python. no idea why it works but it does. Note, I had to close and reopen powershell for this to work.

Command not found when trying to set up substrate

This is the first time I use the terminal on my mac OS. I have followed the instructions so far and restarted Terminal. I tried again making sure I followed every step. That is the reason it says it's already there. The next item I copied and pasted says command not found. Should I delete and start over?
-bash: rustup: command not found
Elizabeths-MacBook-Pro:~ el1748eth$ git clone -b v2.0.0 --depth 1 https://github.com/substrate-developer-hub/substrate-node-template
fatal: destination path 'substrate-node-template' already exists and is not an empty directory.
Elizabeths-MacBook-Pro:~ el1748eth$ cd substrate-node-template/
Elizabeths-MacBook-Pro:substrate-node-template el1748eth$ cargo build
-bash: cargo: command not found
Elizabeths-MacBook-Pro:substrate-node-template el1748eth$

Cannot run git clone or pip install commands

So i'm pretty new to the whole windows repo cloning thing. I installed python 2.7, added the path to my windows cmd and I still cannot run any git clone commands. It shows the following output :
git clone
File "", line 1
git clone
^
I've been scouring the internet for an answer but apparently it should work if I use cmd.
Any help would be appreciated!
git clone
File "", line 1
git clone
^
I have had the same issue recently with 3.7, so I made a new username and it worked. Kind of nice, a clean new Windows profile, even though I just started using it again compared to linux. A pain though.
Make sure all other versions of Python are not installed, or at least affecting the path to the file you need the pip installs to be saved. Python can be saved in a few different locations, and some rare times it has been shown in very obscure places. Check where your file saved on your PC. Probablu C:/ then could be many paths. /Users/UnserNameHere/Windows/ProgramFiles. I would use the search bar in the good old GUI while searching under the C drive (if you have multiple HDD/SDD then pic the one used for the C drive, if nothing comes up try the other drives.
Your looking for a file PythonFoundation I can't remember the entire name, however it will have a very long name Python Foundation are in the name of the file. This is where thing are store and where the path should be sending modules, at least the correct file inside that file.
Also try doing it from other Python versions installed. If you had 3.6 and got 3.7 it doesn't mean 3.6 has been deleted. Also doesn't mean you path, is not set to 3.6 while using 3.7. Same with Python 2, most people or many have both. The pip commands vary between python versions pip3 I believe is used (getting windows and linux a little mixed up right now)
If all fails do it the old fashon way, find the mod, download it, and move it to the python file I mentioned above. The homepage for python should have a tab linking to a page, or it's on the main page, letting you know where it has been known to save. Google how to see he path Pip is taking, or how to see if pip is installed and where, and what paths are set to.

How do I get around "Filename too long" error when running `chef install` on Windows 10?

I'm transitioning from berkshelf to the Policyfile workflow, and everything was running fine until I attempted to resolve all the dependencies. Two of my dependencies are from git, so when I run chef install in the cookbook directory, I get the following error:
Error: Failed to generate Policyfile.lock
Reason: (CookbookOmnifetch::GitCommandError) Git error: command `git reset --hard 7e5e4bccf57718cacc246f1b4d501ff7de8ac13d` failed. If this error persists,
try removing the cache directory at 'C:/Users/pcummuskey/AppData/Local/chefdk/cache/.cache/git/780b7dbee933c3a9efbfd3898d54cdf72784fa7e'.Output from the command:
error: unable to create file test/kitchen/.kitchen/tmp/librarian/cache/source/chef/site/877777683730772c36b1e6a3fc3aa2c3/windows/version-uri/a3432e93fb3c21cb7111fde71e435661/package/files/default/handlers/windows_reboot_handler.rb: Filename too long
Checking out files: 100% (389/389), done.
fatal: Could not reset index file to revision '7e5e4bccf57718cacc246f1b4d501ff7de8ac13d'.
Predictably, removing the cache folder had zero effect on the problem. I'm in the middle of checking whether I can get it working in the ubuntu subsystem and/or docker atm, but it'd be nice to be able to run it natively on Windows.
I don't get this problem using "git bash" (MINGW64) packaged in Git for windows installer.
As an example:
$ pwd
/c/Users/foobar/AppData/Local/chefdk/cache/.cache/git/13036489648c6f8811262c6a50ff6b03da2395b7/4416ca3886d025b3ead519f1ee53af03ecb630f64416ca3886d025b3ead519f1ee53af03ecb630f64416ca3886d025b3ead519f1ee53af03ecb630f64416ca3886d025b3ead519f1ee53af03ecb630f6/4416ca3886d025b3ead519f1ee53af03ecb630f64416ca3886d025b3ead519f1ee53af03ecb630f64416ca3886d025b3ead519f1ee53af03ecb630f61
Managed to work around the issue by making a local cookbooks folder and checking out the dependencies to there and referencing them by path. It's not pretty, but it does the trick.

How to properly install Cabal 1.18.02 in Windows 7?

I'm trying to install the new Cabal in Windows 7. It successfully installs 1.18.02, but when I run "cabal --version" it shows 1.16. The folder C:\Users\me\AppData\Roaming\cabal\bin is at the front of my PATH.
When I directly run the 1.18 executable, I get a bunch of "cabal.exe does not exist" errors.
How can I configure Cabal to use version 1.18 by default?
There is a path conflict due the way haskell platform installs cabal.exe
As seen in this ticket
To fix it:
Delete `C:/program files(x86)/Haskell platform/lib/extralibs/bin/cabal.exe.`
In any case, you can use search tool to find which cabal.exe to delete.
I used cabal-dev to install cabal 1.18 to a sandbox, such that C:\cabal-dev\cabal-dev\bin contains the latest (1.18) cabal executable. I then set C:\Cabal-dev\cabal-dev\bin as the first Variable value in the "Path" variable in "systems variables" (as opposed to the "PATH" variable in "user variables"). That worked for me, and allowed me to keep the older build of cabal intact, (in case its needed later).
It worked for me. Good luck. Here are my exact steps:
Install cabal-dev
open command prompt anywhere
execute following command: “cabal install cabal-dev”
Install new cabal
create directory: c:\cabal-dev, cd to it
execute following command: “cabal-dev install cabal-install”
Set new, upgraded cabal path as higher priority
Close any open command prompts
run: Sysdm.cpl
Go to the “Advanced” tab
Click “Environment Variables”
Select the “Path” variable listed in the “System variables” (lower) windows
Click edit
Add following string to the beginning of the variable value:
“C:\Cabal-dev\cabal-dev\bin;”
Ok, Ok, Ok
Ensure latest cabal is being run:
Open command prompt (anywhere except c:\cabal-dev\ *)
execute following command: “cabal –V”
cabal version should be 1.18.0.2
One other possible cause of this error (aside from the cabal in extralibs problem described in another answer) is that the ld in your path can't read the .o files that GHC produces.
I hit this problem with GHC 7.8.1 RC1, and could see this going wrong by running cabal install with -v3. The 'ld' on my path was coming from Haskell Platform 2013.2.0.0.
Adding mingw\bin from the new GHC's directory to the path fixed the problem.

Resources