Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error in search_path_unsetup while running demo(unitizer) #188

Closed
richierocks opened this issue Oct 6, 2016 · 5 comments
Closed

Error in search_path_unsetup while running demo(unitizer) #188

richierocks opened this issue Oct 6, 2016 · 5 comments
Labels
Milestone

Comments

@richierocks
Copy link

@richierocks richierocks commented Oct 6, 2016

I ran

library(unitizer)
demo(unitizer)

and it worked OK until the line

unitize(.unitizer.test.file)

Then it failed with the following output

Search Path Setup...                                                                                                                        
All sinks released, even those established by test expressions.
All sinks released, even those established by test expressions.
Error in search_path_unsetup() : 
  Unexpectedly failed while attempting to restore search path.  You may need to exit R to restore search path and to untrace `library/attach/detach`; this should not happen so please report to maintainer.
Error in search_path_setup() : 
  Unexpectedly failed while attempting to setup search path.  You may need to exit R to restore search path and to untrace `library/attach/detach`; this should not happen so please report to maintainer.

The traceback is as follows

10: stop("Unexpectedly failed while attempting to setup search path.  You may ", 
        "need to exit R to restore search path and to untrace ", 
        "`library/attach/detach`; this should not happen so please report to ", 
        "maintainer.")
9: search_path_setup()
8: isTRUE(search.path.setup <- search_path_setup())
7: unitize_core(test.file.inf, list(store.id.inf), interactive.mode = interactive.mode, 
       par.env = par.env, search.path.clean = search.path.clean, 
       search.path.keep = search.path.keep, force.update = force.update, 
       auto.accept = auto.accept, pre.load = pre.load, mode = "unitize")
6: unitize(.unitizer.test.file) at unitizer.R#75
5: eval(ei, envir)
4: eval(ei, envir)
3: withVisible(eval(ei, envir))
2: source(available, echo = echo, max.deparse.length = Inf, keep.source = TRUE, 
       encoding = encoding)
1: demo(unitizer)

I'm running R-devel 3.4.0 (rev 71184) under Windows 10 x64, in case it makes a difference.

@brodieG brodieG added the bug label Oct 6, 2016
@brodieG
Copy link
Owner

@brodieG brodieG commented Oct 6, 2016

Thanks for reporting. I have yet to test on R-devel, so that may be the issue. However, I have also made many many changes in the development branch, so I would really appreciate it if you could try:

devtools::install_github("brodieG/diffobj@development")    # need to add version dependency...
devtools::install_github("brodieG/unitizer@development")

and see if you get the same error.

Also, are you using Rstudio or just running Cli?

@brodieG brodieG added this to the 1.2.0 milestone Oct 6, 2016
@brodieG
Copy link
Owner

@brodieG brodieG commented Oct 6, 2016

Also, if you're currently on v0.9.0 of unitizer, you can try setting options(unitizer.search.path.clean=FALSE) to disable search path manipulation for the time being.

@brodieG
Copy link
Owner

@brodieG brodieG commented Oct 6, 2016

Using development versions of unitizer and diffobj, the demo ran fine for me under:

R Under development (unstable) (2016-09-11 r71233) -- "Unsuffered Consequences"
Copyright (C) 2016 The R Foundation for Statistical Computing
Platform: x86_64-pc-linux-gnu (64-bit)
@brodieG
Copy link
Owner

@brodieG brodieG commented Nov 28, 2016

I pushed a new version out to master that should address this issue and many others (1,000 commits since the version you tried). The problem was caused by changes introduced in R-devel.

@brodieG brodieG closed this Nov 28, 2016
@brodieG
Copy link
Owner

@brodieG brodieG commented Nov 28, 2016

Also, obviously, @richierocks feel free to re-open if it is not fixed for you.

brodieG added a commit that referenced this issue Dec 7, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.