Skip to content
This repository has been archived by the owner on Jan 3, 2018. It is now read-only.

Configuration Problems and Solutions

Jump to bottom
Ethan White edited this page Apr 3, 2014 · 33 revisions

Despite our best efforts to ensure that bootcamp attendees configure their computers ahead of time, installation and configuration issues pop up frequently during bootcamps. This page collates common configuration problems encountered by instructors and presents their solutions.

To instructors: Please feel free to edit this page to add new problems and solutions to the appropriate sections as you encounter them. The only requirement is that you should have only add a problem once you have identified and confirmed a solution that at least worked for the cases that you encountered personally. If you encounter a problem that you don't know how to solve, please raise it in an issue in the bc repo so that the community can find a resolution.

Bash

Windows (Git Bash)

  • None of the bash commands seem to work, although the student opened "Git Bash" and the command window is open

    • Ensure that the student has run the program mysys and not git-cmd - the latter will not open the bash emulator environment.

  • User has created/saved files and doesn't know where they are

    • Have users run cd after opening Git Bash and before doing anything else - this will place users in a home directory with Desktop as a subdirectory. cd then cd Desktop will place users on their Desktop. (#56)

  • Copy/paste doesn't work in the command window

    • To copy, right click the title bar and go to Edit -> Mark. Then you can use the mouse to select text and anything you select is copied. You can use Edit -> Paste to paste, or the Insert key is a shortcut. (#140)

Python

All

  • Command ipython notebook fails with ipython not found-type error

    • Very likely that Canopy or Anaconda did not properly append path to Python installation on system path (on Canopy, this easily occurs if students do not open GUI after installation or if they accidentally select "No" when asked if they want to make Canopy the default Python environment). To fix, export path in .bash_profile. On a Mac using Canopy, command is PATH=/Users/<username>/Library/Enthought/Canopy_64bit/User/bin:$PATH; export PATH

  • Imports of scientific Python packages fails from a command line interpreter or script (i.e., python myfile.py) even though user installed Canopy/Anaconda

    • Ensure that path to Canopy/Anaconda python comes before path to system Python (see above). Check with which python and make sure it is Canopy/Anaconda version.

  • IPython notebook appears to be running but no output is shown after cells are run

Windows (Anaconda)

  • New users can't easily open an IPython notebook in an arbitrary directory
    • The start menu shortcut created by Anaconda starts a notebook server in %USERPROFILE%\Documents\IPython Notebooks" by default.
    • New users, who may be unfamiliar with the command prompt, might have trouble opening a notebook in any other directory.
    • A simple batch file with the single-line command "ipython notebook" will start a notebook server in any directory from which it is run.
    • To make a batch file script that opens an ipython notebook in whatever directory it's run from:
      1. Create a simple .txt file: Right Click -> New -> Text Document
      2. Re-name it "Start IPython Notebook Here.bat" (don't forget to change the extension!)
      3. Open it with notepad: Right Click on it -> Edit
      4. Add the text "ipython notebook" to the file -- it should look just like you would type it in a command prompt.
      5. Save & close.
    • Now when a user double clicks on the .bat file, a notebook server will spawn in that directory.
    • The user can move the .bat file to wherever they want their IPython notebook's working directory to be.
    • The user can make copies of the .bat file, and stash one in all the directories they frequently use.
    • Instructors can distribute a copy of the file in the same folder as any example notebooks, so the users can just double-click-and-go in the correct directory. No need to teach users the command prompt.

git

All

  • When pushing to GitHub, username/password are rejected, although student knows that they are correct
    • Some students have needed to use their full email address, rather than their username, in the username field.
    • (Although this makes little sense) Try hitting backspace many times in the password field to "clear out old password info". This might be a Git Bash issue, but unconfirmed.

Windows (Git Bash)

  • User is prompted to enter email address on first commit

    • Appears to be a bug in 1.8.4, as user is prompted even if global config is set with email address. This should only occur on first commit.

  • git push to a Github repo fails with error could not read Username for https:...: No such device or address

    • Bug in Git Bash 1.8.5 - have users install 1.8.4. (#234)
    • This appears to be an issue with the default credential store. Changing the credential store will solve the problem, but I don't see the right command in a quick Google search. I'll look again later...
    • If Git Bash 1.8.5 has been installed, using ssh instead of https for the push is a workaround, but takes several minutes to set up. First generate and set up the SSH key. After generating the ssh key and setting up github to use it, change the origin from the git repository directory (replace username and repo name below):

  • Configuring the git editor to a Windows program like Notepad++.exe is not intuitive. If the path to the program is not in the PATH, changing the system environment variable may require a restart. Additionally, the editor program may open with the previous session and tabs, causing the commit to abort. The following setup works for Notepad++ (adjust for the correct install path for 32-bit / 64-bit executable): git config --global core.editor "'C:/Program Files/Notepad++/notepad++.exe' -multiInst -notabbar -nosession -noPlugin"

Windows (Rstduio):

  • git tab does not appear in Rstudio
    • You need to tell Rstudio where to find your git executable. Assuming you are using gitbash,
      • Go to Tools -> Global options
      • Select Git/SVN
      • Under Git executable select Browse
      • Navigate to and select following file: C:/Progarm Files (x64)/git/bin/git
    • Restart Rstudio

Mac

  • Running git command fails with Illegal operation-type error

    • It appears that git 1.9.x is incompatible with Snow Leopard (10.6), although this is not stated on installer page. Try uninstalling and re-installing 1.8.x.
    • We experienced this problem with both 10.6 & 10.7 and installing 1.8.x did not solve the issue
    • Install older installers from https://code.google.com/p/git-osx-installer/downloads/list

  • Had a failure including "lazy symbol binding failed" on 10.8.5

    • most advice involved installing XCode with the command line tools (didn't try given the 1.6 GB download)

Linux

  • Permission denied (public key) on pushing to Github

    • Has several causes and thus several solutions. Github has a list, in a nutshell:
      • Don't use sudo (and check whether the permissions for SSH keys are correct)
      • Connection problems or weird routing problems: ssh -vT [email protected] should print github.com and port 22
      • Connect only as user git
      • Check whether ssh-add -l prints a key, if not, create one
      • Check whether ssh-keygen -lf ~/.ssh/id_rsa.pub prints several keys, and check which one GitHub uses in the account settings
      • You can always troubleshoot more using ssh -vT [email protected]

  • error 403 returned on a git push to github

  • a git push results in a dialog requiring a password to unlock the private key: "Enter password to unlock the private key. An application wants access to the private key xxxxx".

Clone this wiki locally