03:31 < jeffin143> rcurtin : I am not sure , but was anyone working on go binding for Mlpack..???

11:01 < rcurtin> jeffin143: yeah, Yashwant was, but I need to respond to the review comments. if you want to help review feel free :)

12:17 < jenkins-mlpack2> Project docker mlpack nightly build build #461: FAILURE in 1 day 8 hr: http://ci.mlpack.org/job/docker%20mlpack%20nightly%20build/461/

12:19 < rcurtin> I think that failure occurred because the monthly build has been running and took so long that the version of mlpack checked out in the 'docker mlpack git checkout' job became out of date :)

13:23 < zoq> :)

15:03 < jenkins-mlpack2> Project docker ensmallen nightly build build #20: ABORTED in 1 day 10 hr: http://ci.mlpack.org/job/docker%20ensmallen%20nightly%20build/20/

15:15 < KimSangYeon-DGU> The issue in #2017 was fixed, I'll open pull request later because of the last subway that I should take

15:16 < KimSangYeon-DGU> I should run

15:16 < KimSangYeon-DGU> :)

15:16 < rcurtin> KimSangYeon-DGU: awesome, looking forward to the fix!

15:16 < rcurtin> don't miss the train :)

15:44 < zoq> KimSangYeon-DGU: Nice!

16:21 < KimSangYeon-DGU> rcurtin, zoq: Thanks, I got home :)

17:16 < jenkins-mlpack2> Project docker mlpack nightly build build #462: NOW UNSTABLE in 4 hr 59 min: http://ci.mlpack.org/job/docker%20mlpack%20nightly%20build/462/

17:34 < jenkins-mlpack2> Project docker ensmallen nightly build build #21: ABORTED in 2 hr 30 min: http://ci.mlpack.org/job/docker%20ensmallen%20nightly%20build/21/

17:34 < jenkins-mlpack2> noreply: Merge pull request #134 from barak/master

20:11 < rcurtin> KimSangYeon-DGU: nice fix, I saw the commit message :) I always have a lot of fun at the moment when I realize what the problem is, I hope the same was true for you too :)

20:12 < rcurtin> it might be better to make a branch in your fork though, that way we don't end up with a bunch of branches in the main mlpack repository

20:12 < rcurtin> I usually just add a remote (i.e. git remote add https://github.com/rcurtin/mlpack) in my local repository, then when I make a new branch I'll just push it to my remote, i.e. git push -u rcurtin <name-of-branch> then I can easily open a PR :)

20:17 < travis-ci> mlpack/mlpack#8003 (nbc - 91e7bce : Sangyeon): The build has errored.

20:17 < travis-ci> Change view : https://github.com/mlpack/mlpack/commit/91e7bcef72de

20:17 < travis-ci> Build details : https://travis-ci.org/mlpack/mlpack/builds/586219894

22:27 < KimSangYeon-DGU> rcurtin: Ahh, thanks for the info. Actually, I mistakenly made a branch in main mlpack repository and deleted it right away. I'm embarrassed by my mistake :)