rcurtin_irc changed the topic of #mlpack to: mlpack: a scalable machine learning library (https://www.mlpack.org/) -- channel logs: https://libera.irclog.whitequark.org/mlpack -- NOTE: messages sent here might not be seen by bridged users on matrix, gitter, or slack
coatless[m] has joined #mlpack
<coatless[m]> Looks like the Slack <-> IRC bridge died on October 18th :'(
<coatless[m]> rcurtin: do you need help with uploading the R package binary to CRAN?
<zoq[m]> <rcurtin[m]> "sounds good, just let me know if..." <- It’s fine, I have to update the docker container and fix an issue with the nginx connection.
<zoq[m]> zoq[m]: Should be resolved later tomorrow.
krushia has quit [Read error: Connection reset by peer]
krushia has joined #mlpack
_slack_mlpack_10 has quit [Quit: You have been kicked for being idle]
<jonpsy[m]> zoq: Have you pushed your changes?
<zoq[m]> <jonpsy[m]> "zoq: Have you pushed your..." <- Not yet, like to fix some other issues first.
<rcurtin[m]> coatless: oh no! I will look into the slack bridge momentarily. it would great if you were willing to get the R package updated! I think that it might actually be a little tricky to get the R package built right---it looks like the Actions script did not succeed: https://github.com/mlpack/mlpack/actions/runs/3307466348
<rcurtin[m]> I assume what will need to happen is that the steps in the [R workflow](https://github.com/mlpack/mlpack/blob/master/.github/workflows/main.yml) will just need to be done by hand on the `4.0.0` tag (and then probably the workflow itself needs to be fixed, not sure what the issue is, but probably not something too tricky; anyway, that's a separate issue)
ryan[m]123 has joined #mlpack
<ryan[m]123> test message from Slack
<ryan[m]123> what? well then why didn't jjb’s message go through!?
<rcurtin[m]> endless mysteries of the software world
<rcurtin[m]> wait, but messages from matrix don't go back to Slack...
<ryan[m]123> Eshaan Agarwal> yeah, sorry about the documentation issue, there was a bug in the website build scripts that I fixed this morning. I still have a little work to do there, but we are transitioning away from Doxygen, so the link for that page is now the section in the README: <https://github.com/mlpack/mlpack/blob/4.0.0/README.md#3-installing-and-using-mlpack-in-c
halfy has joined #mlpack
<halfy> hello world
zoq[m]1 has left #mlpack [#mlpack]
ryan[m]123 has left #mlpack [#mlpack]
_slack_mlpack_U7 has left #mlpack [#mlpack]
RohanKumarSingh[ has left #mlpack [#mlpack]
jjb[m] has left #mlpack [#mlpack]
_slack_mlpack_U0 has left #mlpack [#mlpack]
_slack_mlpack_U4 has left #mlpack [#mlpack]
<rcurtin[m]> test message from Matrix
<halfy> poke poke
ryan[m]123 has joined #mlpack
<ryan[m]123> a third test message from Slack
<rcurtin[m]> and a second test message from Matrix
<ryan[m]123> okay, so it looks like the current state of things is that messages go successfully from Slack to Matrix, but not vice versa; I'm going to let it sit for a few hours and try again, in case there is some process that is happening in the background; and after that I'll open an issue with the Matrix folks. sorry for any inconvenience, but it is getting sorted out 😄
<jonpsy[m]> <zoq[m]> "Not yet, like to fix some..." <- Cool by me, but if the fix is done & tested then it's better if its pushed so we could close a part of our project. Kinda excited for it tbh :)
<coatless[m]> <rcurtin[m]> "I assume what will need to..." <- I'll need to re-write the git actions workflow. :'(
<rcurtin[m]> oh, is something wrong with the workflow itself?
<coatless[m]> Since Gabor took over the r-lib/actions repository, lots of updates have happened. So, we're just a bit behind on adopting (e.g. no more `master` branch.)
<rcurtin[m]> ah, I see, I was wondering if it might be something like that... I'm happy to help out, just point me in the right direction if I can be helpful 😃
<coatless[m]> rcurtin: Possible fix at https://github.com/mlpack/mlpack/pull/3296 Though, I'll likely need to add a commit or two as I may have simplified too much.
<coatless[m]> So, it's building now. But, I'll need to change how the dependency packages are built to speed up the workflow. (e.g. caching dependencies)
<rcurtin[m]> nice! but I don't think there will be a way to trigger that workflow for the 4.0.0 tag, since that tag already happened?
<coatless[m]> rcurtin: correct.
<rcurtin[m]> still a very good thing to have that workflow updated either way
<coatless[m]> The only issue with the R package is a URL pointing to a non-existent documentation page 4.0.1: https://github.com/mlpack/mlpack/actions/runs/3324242063/jobs/5496591426#step:9:28