New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NameError: global name 'wd_to_path_set' is not defined #607

Closed
joshuataylor opened this Issue Oct 10, 2016 · 4 comments

Comments

Projects
None yet
3 participants
@joshuataylor

Ubuntu 16.04, using xubuntu (if that matters)

Traceback (most recent call last):

  File "cola/cmds.py", line 1865, in do_cmd
    return cmd.do()

  File "cola/cmds.py", line 1267, in do
    fsmonitor.current().refresh()

  File "cola/fsmonitor.py", line 73, in refresh
    self._thread.refresh()

  File "cola/fsmonitor.py", line 240, in refresh
    self._worktree_path_to_wd_map)

  File "cola/fsmonitor.py", line 263, in _refresh_watches
    wd_to_path_set.pop(wd)

NameError: global name 'wd_to_path_set' is not defined

Randomly appears, not sure what triggers it.

@davvid davvid closed this in 08a9e55 Oct 11, 2016

@fabier

This comment has been minimized.

Show comment
Hide comment
@fabier

fabier Nov 19, 2017

Traceback (most recent call last):

File "/home/xxx/share/git-cola/lib/cola/cmds.py", line 1865, in do_cmd
return cmd.do()

File "/home/xxx/share/git-cola/lib/cola/cmds.py", line 1267, in do
fsmonitor.current().refresh()

File "/home/xxx/share/git-cola/lib/cola/fsmonitor.py", line 73, in refresh
self._thread.refresh()

File "/home/xxx/share/git-cola/lib/cola/fsmonitor.py", line 240, in refresh
self._worktree_path_to_wd_map)

File "/home/xxx/share/git-cola/lib/cola/fsmonitor.py", line 263, in _refresh_watches
wd_to_path_set.pop(wd)

NameError: global name 'wd_to_path_set' is not defined

fabier commented Nov 19, 2017

Traceback (most recent call last):

File "/home/xxx/share/git-cola/lib/cola/cmds.py", line 1865, in do_cmd
return cmd.do()

File "/home/xxx/share/git-cola/lib/cola/cmds.py", line 1267, in do
fsmonitor.current().refresh()

File "/home/xxx/share/git-cola/lib/cola/fsmonitor.py", line 73, in refresh
self._thread.refresh()

File "/home/xxx/share/git-cola/lib/cola/fsmonitor.py", line 240, in refresh
self._worktree_path_to_wd_map)

File "/home/xxx/share/git-cola/lib/cola/fsmonitor.py", line 263, in _refresh_watches
wd_to_path_set.pop(wd)

NameError: global name 'wd_to_path_set' is not defined

@davvid

This comment has been minimized.

Show comment
Hide comment
@davvid

davvid Nov 20, 2017

Member

This issue was first fixed in v2.9 back in November 2016. It's been over a year and we've had a few releases since then, most recently v3.0. If you're hitting this, I would suggest cloning the repo and keeping a symlink to bin/git-cola somewhere in your path, e.g. in ~/bin:

mkdir -p ~/src
git clone git://github.com/git-cola/git-cola.git ~/src/git-cola
mkdir -p ~/bin
cd ~/bin
ln -s ../src/git-cola/bin/git-cola
ln -s ../src/git-cola/bin/git-dag

Lastly, edit your ~/.bashrc and make sure that $HOME/bin is at the front of the $PATH environment variable. Once it's setup then git cola will use the version from the cloned repo. I hope that helps.

The better solution would be to host a git-cola ppa so that users can try newer cola versions on older ubuntu releases. If someone wants to help, #460 is our issue to track that request.

Thanks for the reminder that we should make it easier for ubuntu users to try new versions.

Member

davvid commented Nov 20, 2017

This issue was first fixed in v2.9 back in November 2016. It's been over a year and we've had a few releases since then, most recently v3.0. If you're hitting this, I would suggest cloning the repo and keeping a symlink to bin/git-cola somewhere in your path, e.g. in ~/bin:

mkdir -p ~/src
git clone git://github.com/git-cola/git-cola.git ~/src/git-cola
mkdir -p ~/bin
cd ~/bin
ln -s ../src/git-cola/bin/git-cola
ln -s ../src/git-cola/bin/git-dag

Lastly, edit your ~/.bashrc and make sure that $HOME/bin is at the front of the $PATH environment variable. Once it's setup then git cola will use the version from the cloned repo. I hope that helps.

The better solution would be to host a git-cola ppa so that users can try newer cola versions on older ubuntu releases. If someone wants to help, #460 is our issue to track that request.

Thanks for the reminder that we should make it easier for ubuntu users to try new versions.

@fabier

This comment has been minimized.

Show comment
Hide comment
@fabier

fabier Nov 20, 2017

fabier commented Nov 20, 2017

@fabier

This comment has been minimized.

Show comment
Hide comment
@fabier

fabier Nov 21, 2017

fabier commented Nov 21, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment