06:04 < jenkins-mlpack2> Yippee, build fixed!

06:04 < jenkins-mlpack2> Project docker ensmallen nightly build build #88: FIXED in 49 min: http://ci.mlpack.org/job/docker%20ensmallen%20nightly%20build/88/

08:18 < jenkins-mlpack2> Yippee, build fixed!

08:18 < jenkins-mlpack2> Project docker mlpack nightly build build #529: FIXED in 3 hr 4 min: http://ci.mlpack.org/job/docker%20mlpack%20nightly%20build/529/

14:40 < rcurtin> zoq: maybe I don't understand the azure interfaces, but I'm not sure how to get to the test failures for the macOS plain job here:

14:40 < rcurtin> https://dev.azure.com/mlpack/mlpack/_build/results?buildId=15

14:40 < rcurtin> if I click on the failed "publish tests" step for the macOS plain build, it says:

14:41 < rcurtin> "Published Test Run : https://dev.azure.com/mlpack/mlpack/_TestManagement/Runs?runId=108&_a=runCharts."

14:41 < rcurtin> but if I try to go to that link, it asks me to sign in to Microsoft Live...

14:42 < rcurtin> once I finally create the account and give Microsoft permission to spam me about their products, etc., etc. :) it finally gives me a 401...

14:50 < zoq> rcurtin: I think the one posted in the job itself is internal not sure; what I usually do is to open the Tests tab right beside the Summary and Logs.

14:51 < zoq> Also I have to debug the failing linux builds, I think the config is fine, and there is some strange problem with the serialization.

14:52 < zoq> And I'd like to merge the results into one agent, Shogun managed to do it, so I guess it's possible.

14:57 < zoq> Btw. azure does not share the github group permissions, similair to appvoyer so I think I have to invite people, so that they can restart the job if necessary.

15:43 < rcurtin> ahhh, got it, I hadn't seen the "tests" tab

15:44 < rcurtin> thanks!

15:48 < jeffin143> :) just got my hands on this : https://ibb.co/cvV17qb

15:49 < jeffin143> Had a wonderful summer 🚀🚀

16:16 < rcurtin> jeffin143: nice! got mine a little while back

16:17 < rcurtin> strangely the color is basically exactly the same as my company's t-shirts... so when I wear this year's GSoC shirt, people in my company get a bit confused :)

16:18 < jeffin143> Haha :)

17:12 < travis-ci> mlpack/mlpack#8338 (master - ed9d7e2 : Shikhar Jaiswal): The build has errored.

17:12 < travis-ci> Change view : https://github.com/mlpack/mlpack/compare/20fcca48fd02...ed9d7e27cefb

17:12 < travis-ci> Build details : https://travis-ci.org/mlpack/mlpack/builds/615119762

17:28 < Nakul> Hello all!,

17:29 < Nakul> can someone provide some resource for notebook for mlpack.

17:45 < zoq> Nakul: Hey, not sure what you mean with notebook.

17:47 < Nakul> somewhere i saw that we can use notebook like(jupyter notebook) for mlpack as well

17:48 < Nakul> but i can't find any resource on internet

17:50 < zoq> Nakul: Right, there is no mlpack notebook at least not yet, we really like the idea so there so they are coming for sure

17:51 < Nakul> so is it in development process ?

17:54 < zoq> Getting a notebook working with mlpack is simple, it's the same process as linking locally, the difficult part is workout a notebook that shows something useful. The process is really similair to writing a tutorial, anyway I don't think we haven't made any huge process yet, if you like to work on that please feel free.

17:55 < KimSangYeon-DGU> I'll bring a cup of tea before the meeting :)

17:58 < Nakul> zoq thanks for information , offcourse would love to do some research over it : )

18:00 < zoq> KimSangYeon: Will go with https://www.clubmate.de/about-club-mate.html today.

18:00 < rcurtin> uh, hang on, I have two zoom accounts, having trouble starting the meeting...

18:01 < rcurtin> ok, got it working

18:55 < rcurtin> KimSangYeon-DGU: do you mean mlpack.__version__?

19:00 < rcurtin> I think that was a success, thanks everyone who joined the meetup :)

19:02 < KimSangYeon-DGU> Thanks for meeting :)

19:03 < zoq> Agreed, I really liked the informal meeting, even if we haven't talked for hours and hours, it's a nice opportunity to site down and go through some PRs.

19:05 < rcurtin> definitely, do you think I should send out a quick email with a few bullet points of what we talked about?

19:09 < zoq> rcurtin: I think that is a good idea.

19:10 < KimSangYeon-DGU> Agreed

19:11 < rcurtin> ok, let me get that sent out then :)

19:11 < KimSangYeon-DGU> Thanks!

19:18 < rcurtin> ok, done :)

19:25 < KimSangYeon-DGU> How can we get the current version of mlpack in `CMakeLists.txt`?

19:27 < rcurtin> I think the best way is to look in src/mlpack/CMakeLists.txt... the version gets extracted in lines 108-119

19:27 < rcurtin> basically it's pulled from src/mlpack/core/util/version.hpp

19:30 < KimSangYeon-DGU> Ahh, thanks, I thought that is the next version

19:30 < rcurtin> oh, wait, that would get the version of the repository

19:31 < rcurtin> do you mean the version of the repository or the latest stable release version?

19:31 < KimSangYeon-DGU> pip install mlpack

19:31 < KimSangYeon-DGU> I mean 3.2.1

19:31 < KimSangYeon-DGU> the latest stable release version

19:31 < rcurtin> ok, I see

19:31 < rcurtin> so to do that you might want to parse CHANGELOG.md for the first version line

19:32 < KimSangYeon-DGU> Aha

19:32 < KimSangYeon-DGU> Ok

19:32 < rcurtin> if you're looking to fix #2091 though, I think you can use version.hpp just fine

19:32 < rcurtin> since when we make a release of 3.2.2, version.hpp will contain "3.2.2" as the version (not "3.2.3")

19:32 < KimSangYeon-DGU> Right, I'll try to fix the #2091 issue

19:33 < KimSangYeon-DGU> Thanks for the info

19:33 < rcurtin> ahh, ok, then it should be just fine to use version.hpp, since then the version that gets put into __init__.py will be the same as the version of the repository

19:34 < KimSangYeon-DGU> Ok :)