dead link

[stan-dev]

dead link

[jgabry]

Do you mean that url itself or the ones constructed from it? That url itself isn’t intended to be used on its own, but rather to be the first part of the url that gets made on line 230. Does it fail to download the files when you call rstan_package_skeleton or just not work if you paste that url from line 229 into a browser? If just the latter then I don’t think there’s anything to fix, but if it’s preventing rstan_package_skeleton from downloading the needed files then we definitely need to fix it. When I run it seems to work but let me know if it doesn’t work you and I’ll dig into it further.

…

On Thu, Apr 19, 2018 at 2:35 PM Adam ***@***.***> wrote: line 229 in the rstan_package_skeleton file has the following dead link 'https://raw.githubusercontent.com/stan-dev/rstanarm/master' — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#29>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AHb4Q6rp_OkubiwbMESQmeA3uKu6WGeDks5tqNkAgaJpZM4TcSjZ> .

[apeterson91]

Yes, when I ran the function the tools/make_cpp.R file only had a 404:NOT FOUND error.

FWIW, there are also appear to be some inconsistencies in the way the files are set up in the rstan_package_skeleton file (i.e. it still makes an exec folder) and the way it expects to read them (looking for src/stan_files). I suspect this is a result of the changes to rstanarm. Not sure if I should make a separate issue here for that here or elsewhere.

[jgabry]

Ugh, this was definitely not an issue when we were testing before the release. Thanks for letting us know! I’ll figure out what’s going on and report back here. You’re using rstantools v1.5.0, right? If so it shouldn’t be creating exec and certainly shouldn’t have broken urls, so I’ll try to sort it out ASAP.

…

On Thu, Apr 19, 2018 at 3:33 PM Adam ***@***.***> wrote: Yes, when I ran the function the tools/make_cpp.R file only had a 404:NOT FOUND error. FWIW, there are also appear to be some inconsistencies in the way the files are set up in the rstan_package_skeleton file (i.e. it still makes an exec folder) and the way it expects to read them (looking for src/stan_files). I suspect this is a result of the changes to rstanarm. Not sure if I should make a separate issue here for that or elsewhere. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#29 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AHb4Q5Md4-vCWb3gs3HNgArJDP97qexmks5tqOaWgaJpZM4TcSjZ> .

[apeterson91]

Hmm. I'm apparently using v1.3.0... but I ran update.packages before I used it. Is v1.5.0 only available via github?

[jgabry]

Weird. It's definitely on CRAN:

https://CRAN.R-project.org/package=rstantools

Which mirror are you using to download it?

[apeterson91]

Rstudio's. I've since updated it via another method (via the Rstudio GUI surprisingly enough) and that seems to have resolved the issue. I'm not sure why the base function (nor the devtools version) was updating it...

[jgabry]

I’m glad you got it installed, but yeah that’s very strange it couldn’t be installed the other ways. I’m really not sure how to explain that!

…

On Fri, Apr 20, 2018 at 10:39 AM Adam ***@***.***> wrote: Rstudio's. I've since updated it via another method (via the Rstudio GUI surprisingly enough) and that seems to have resolved the issue. I'm not sure why the base function (nor the devtools version) was updating it... — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#29 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AHb4Q4sEhd5e1IreKm211uB2GLP5PdzWks5tqfMcgaJpZM4TcSjZ> .