Max Gordon

I don't think this bug is MacOS specific, similar issue appears in Ubuntu. When running NodeJS 12 and above the below Dockerfile will fail, here is the simplest possible container...

Can confirm on: Atom : 1.10.2 Electron: 0.37.8 Chrome : 49.0.2623.75 Node : 5.10.0

I've just noticed that I sometimes get a double fire when there is a prop change due to the update, solved this through a `setTimeout`

The [torch-dataframe](https://github.com/AlexMili/torch-dataframe/) package solves this issue. It has also samplers, manipulation, categorical conversions and more built-in.

For some strange reason it seems to be little activity - I've created a fork and added some of the most interesting pull requests in my mind + the annoying...

Actually you only need to do: `apm install gforge/atom-git-control` - no 2 (cloning) is not necessary :-)

There are additional issues in https://github.com/jacogr/atom-git-control/blob/master/lib/dialogs/project-dialog.coffee#L44-L46 That include the same issue.

I think you also need to add the `workinDirectory` in `project-dialog.coffe` line 46 due to the same issue. I also suspect that line 33 is also affected.

Added the previous log in my fork: https://github.com/gforge/atom-git-control/commit/c0239fa305194950497d6529dcb4c97b0f534c23 This fork also contains some of the directory bug fixes

One of my plans has been to return a gTree-object from the drawForestplotObject function but so far I've settled with the change to a split between the basic function and...