You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is to be expected, of course, but it took me a quite a while to figure out what the problem was, because the error message is not every informative (I think):
Updating pensieve documentation
Loading pensieve
Error in file(con, "r") : cannot open the connection
Calls: suppressPackageStartupMessages ... process_examples -> unlist -> lapply -> FUN -> file
In addition: Warning message:
In file(con, "r") :
cannot open file '/Users/Max/GitHub/pensieve/dataset <- civicon_2014$sorts[,,"before"]
diag_forced(dataset = dataset,
grid = diag_distro_max(dataset))': No such file or directory
Execution halted
Exited with status 1.
Any chance there might be a more informative error message and/or protection against this mistake?
It's now easy for me to see that of course/Users/Max/GitHub/pensieve/dataset <- civicon_2014$sorts[,,"before"]diag_forced(dataset = dataset, grid = diag_distro_max(dataset))'isn't a file, it was somehow hard to see in the printout unless you knew what you were looking for.
Or maybe I'm just unusually dense.
The text was updated successfully, but these errors were encountered:
I erroneously wrote
@example
instead of@examples
before, well, an actual example (I'm guessing this happens easily).Because
@example
expects a file afterwards as per r-pkgs:the whole documentation (and build) failed, because of this section:
This is to be expected, of course, but it took me a quite a while to figure out what the problem was, because the error message is not every informative (I think):
Any chance there might be a more informative error message and/or protection against this mistake?
It's now easy for me to see that of course
/Users/Max/GitHub/pensieve/dataset <- civicon_2014$sorts[,,"before"]diag_forced(dataset = dataset, grid = diag_distro_max(dataset))'
isn't a file, it was somehow hard to see in the printout unless you knew what you were looking for.Or maybe I'm just unusually dense.
The text was updated successfully, but these errors were encountered: