Where/how to report package issues?

17 views
Skip to first unread message

Per Nyfelt

unread,
Dec 26, 2018, 9:37:50 AM12/26/18
to Renjin
Hi, i found a difference in behavior for the downloader package

The following works in GNU R
library(downloader)
filename <- basename(url)
download(url, destfile=filename)

But in Renjin Studio (and in the scriptengine) it gives the following error:
Renjin 0.9.2716
Copyright (C) 2018 The R Foundation for Statistical Computing
Copyright (C) 2018 BeDataDriven

library(downloader)
filename <- basename(url)
download(url, destfile=filename)
Error: missing value where TRUE/FALSE needed

What would be the best procedure to report this? Should i open an issue at https://github.com/bedatadriven/renjin/issues or somewhere else?

would it help if hamcrest tests accompany the diff?

if so, should those tests be submitted as pull requests somewhere (I did not find a "natural" place for this in the renjin repo, although test-packages seems to be a reasonable place)?

Best regards,
Per

Alexander Bertram

unread,
Dec 29, 2018, 6:25:34 PM12/29/18
to Renjin
Hi Per,

In general, the difference in behavior won't lie with a package itself, but rather some part of Renjin itself (base, stats, graphics, etc). 

I dug into the example above and found that the download() function calls if(capabilities("libcurl")) which fails indirectly because we hadn't added the "libcurl" capability to Renjin yet. Because the result is a zero-length vector, the if statement evaluation fails.

The most helpful would be to post this kind of bug and test case to the Renjin project, though I understand that it's not always easy to identify the root cause of a problem affecting a package.

The next best thing is to open a place holder bug mentioning the package, and we'll rename the issue once the root cause is identified. But it may take longer to fix in this case.

Best,
Alex

Per Nyfelt

unread,
Dec 30, 2018, 8:53:56 AM12/30/18
to Renjin
Very good, thanks Alex!
Reply all
Reply to author
Forward
0 new messages