search for: stop_on_error

...e, it is now exactly what Martin mentions. I think it > is a good start that can eventually be extended later for > what you are asking. I tend to agree; this seems indeed much easier than I anticipated. Thank you, Jan! I'm testing a version which uses the logical variable 'stop_on_error' rather than 'no_stop_on_error' (because !no_stop_on_error is hard to mentally parse quickly). My proposed name '--no-stop-on-error' was a quick shot; if somebody has a more concise or better "English style" wording (which is somewhat compatible with all the other o...

...ary: the 'curl' package has alternative implementations of url() and download.file() which exercise the correct behavior. I can only speculate, but if the motivation is to explicitly support retrieval of error pages, perhaps the download.file() and url() functions can gain an argument 'stop_on_error' or something similar which give the user an option to ignore server errors. However this behavior should certainly not be the default. When a function or script contains a line like this: download.file("https://someserver.com/mydata.csv", "mydata.csv") Then in the next...

...s. I think it > > is a good start that can eventually be extended later for > > what you are asking. > > I tend to agree; this seems indeed much easier than I > anticipated. Thank you, Jan! > > I'm testing a version which uses the logical variable > 'stop_on_error' rather than 'no_stop_on_error' (because > !no_stop_on_error is hard to mentally parse quickly). > > My proposed name '--no-stop-on-error' was a quick shot; if > somebody has a more concise or better "English style" wording > (which is somewhat compat...

...ackage has alternative implementations of url() > and download.file() which exercise the correct behavior. > > I can only speculate, but if the motivation is to explicitly support > retrieval of error pages, perhaps the download.file() and url() > functions can gain an argument 'stop_on_error' or something similar > which give the user an option to ignore server errors. However this > behavior should certainly not be the default. When a function or > script contains a line like this: > > download.file("https://someserver.com/mydata.csv", "mydata.csv&...

I'm using caret to assess classifier performance (and it's great!). However, I've found that my results differ between R2.* and R3.* - reported accuracies are reduced dramatically. I suspect that a code change to kernlab ksvm may be responsible (see version 5.16-24 here: http://cran.r-project.org/web/packages/caret/news.html). I get very different results between caret_5.15-61 +

Hi Martin, Jan, On 11/03/2016 03:45 AM, Martin Maechler wrote: >>>>>> Jan Gorecki <J.Gorecki at wit.edu.pl> >>>>>> on Tue, 1 Nov 2016 22:51:28 +0000 writes: > > > Hello community/devs, Is there an option to run package > > tests during R CMD check and not stop on first error? I > > know that testing frameworks (testhat

Hi Martin, Indeed it does (and I should have confirmed myself with R-patched and R-devel before posting...) Thanks, and sorry for the noise. Kevin On Tue, Aug 25, 2015, 13:11 Martin Morgan <mtmorgan at fredhutch.org> wrote: > On 08/25/2015 12:54 PM, Kevin Ushey wrote: > > Hi all, > > > > The following fails for me (on OS X, although I imagine it's the same >