Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [statet-users] Error update ref: namespace:pkg
Hi Stephan,

Thanks for this suggestion.  I gave it a try, but I'm still getting the same error:

Error in loadNamespace(name) : there is no package called 'pkg'


I am thinking this may be related to how I sourced the libraries I was using in one of my scripts:

needed.pkgs <- c("doParallel", 'data.table', 'dplyr', 'ggplot2', 'stringr') 

for(pkg in needed.pkgs) library(pkg, character._only_=TRUE)


I replaced this with standard calls to library() for each package, but the errors persist, even in a new R session, like something has been corrupted in the workspace.  I tried rebuilding the environment index, but this had no effect (grasping at straws).  I don't *think* this error is being raised when I run R without Eclipse, but I'm not sure I have run long enough to see it; in Eclipse the error is only being raised every ~15 minutes or so (and it's not obviously associated with anything particular I am doing, but doesn't happen unless I am interacting with the console.)

It's more of an annoyance than a show-stopper.  Very strange...

Thanks again,
Mike



On Wed, Oct 30, 2019 at 1:39 PM Stephan Wahlbrink <sw@xxxxxxxxxxxx> wrote:
Hi Michael,

thank you for the analysis.

The error is possibly triggered by the element info hover (str) or a
similar feature. Such tasks usually use a special error handler, I have to
analyze why this doesn't work as expected.

As workaround you can try to disable the hovers in the preferences.

Regards,
Stephan


[30.10.2019 20:10] Michael Rowe wrote:
> Hi again,
>
> Digging into this more, the reason it was acting like the enter key was
> being held down when this error occurred is that I have
> options(error=utils::recover) set.  This option kicks you into the R (text)
> debugger when an error occurs; I usually run in this mode.  For some
> reason, in this case the error, loadNamespace(name) : there is no package
> called 'pkg', kicks into the debugger where you have to select the frame
> you want to enter, and then is getting input from somewhere that is not a
> valid frame, and so it asks the question again.
>
> [image: image.png]
>
> Note that this error is being triggered independently of me doing anything
> in the console.  Once I changed options(error=utils::dump
>
> Any insights on what might be causing this or how I might stop it would be
> much appreciated.
>
> Thanks,
> Mike
>
> On Mon, Oct 28, 2019 at 10:46 AM Michael Rowe <mwrowe@xxxxxxxxx> wrote:
>
>> Hi,
>>
>> I am running Eclipse with StatET on a Mac.  Every 10 minutes or so, the
>> console starts spewing output as if I were holding the enter key down.  It
>> will stop, eventually, if I hit the interrupt (X) on the console interface
>> several times.
>>
>> This seems to coincide with the following error:
>>
>> Error update ref: namespace:pkg
>> (plugin: org.eclipse.statet.r.console.core)
>>
>>
>> I tried updating StatET from 4.0.1, and also I have tried disabling
>> automatic update of the environment index, but these didn't help.
>>
>> Is anyone else seeing this behavior? Any ideas on what to do?
>>
>> Thanks,
>> Mike
>>
>> Here is my session info:
>>
>> Most recent StatET version (4.0.2.201910101100).
>> Mac OS 10.14.6 (Mohave)
>>
>> eclipse.buildId=4.10.0.I20181206-0815
>> java.version=1.8.0_222
>> java.vendor=AdoptOpenJDK
>> BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=en_US
>> Framework arguments:  -product org.eclipse.epp.package.java.product
>> -product org.eclipse.epp.package.java.product -keyring
>> /Users/mike.rowe/.eclipse_keyring
>> Command-line arguments:  -os macosx -ws cocoa -arch x86_64 -product
>> org.eclipse.epp.package.java.product -data
>> file:/Users/mike.rowe/Documents/workspace_201812/ -product
>> org.eclipse.epp.package.java.product -keyring
>> /Users/mike.rowe/.eclipse_keyring
>>
>> ...and here is the stack trace:
>>
>> org.eclipse.statet.jcommons.status.StatusException: Evaluation failed:
>> Namespace 'pkg' not available.
>> at
>> org.eclipse.statet.rj.server.client.AbstractRJComClient.toStatusException(AbstractRJComClient.java:1410)
>> at
>> org.eclipse.statet.rj.server.client.AbstractRJComClient.evalData(AbstractRJComClient.java:1444)
>> at
>> org.eclipse.statet.r.nico.impl.RjsController.evalCombinedStructSpecialEnv(RjsController.java:1255)
>> at
>> org.eclipse.statet.r.nico.impl.RjsController.evalCombinedStruct(RjsController.java:1269)
>> at
>> org.eclipse.statet.internal.r.console.core.RObjectDB.evalResolve(RObjectDB.java:626)
>> at
>> org.eclipse.statet.internal.r.console.core.RObjectDB.resolve(RObjectDB.java:544)
>> at
>> org.eclipse.statet.r.console.core.RWorkspace.resolve(RWorkspace.java:437)
>> at
>> org.eclipse.statet.r.console.core.util.LoadReferenceRunnable.run(LoadReferenceRunnable.java:223)
>> at
>> org.eclipse.statet.rj.ts.core.AbstractRToolRunnable.run(AbstractRToolRunnable.java:70)
>> at
>> org.eclipse.statet.nico.core.runtime.ToolController.runHotModeLoop(ToolController.java:1390)
>> at
>> org.eclipse.statet.r.nico.impl.RjsController.access$9(RjsController.java:1)
>> at
>> org.eclipse.statet.r.nico.impl.RjsController$NicoComClient.processHotMode(RjsController.java:419)
>> at
>> org.eclipse.statet.rj.server.client.AbstractRJComClient.runMainLoop(AbstractRJComClient.java:940)
>> at
>> org.eclipse.statet.rj.server.client.AbstractRJComClient.answerConsole(AbstractRJComClient.java:1191)
>> at
>> org.eclipse.statet.r.nico.impl.RjsController.doSubmitL(RjsController.java:1127)
>> at
>> org.eclipse.statet.nico.core.runtime.ToolController.submitToConsole(ToolController.java:1921)
>> at
>> org.eclipse.statet.r.nico.AbstractRDbgController.submitToConsole(AbstractRDbgController.java:796)
>> at
>> org.eclipse.statet.r.console.core.AbstractRController.submitFileCommandToConsole(AbstractRController.java:223)
>> at
>> org.eclipse.statet.r.nico.AbstractRDbgController.doSubmitFileCommandToConsole(AbstractRDbgController.java:861)
>> at
>> org.eclipse.statet.r.nico.impl.RjsController.doSubmitFileCommandToConsole(RjsController.java:1122)
>> at
>> org.eclipse.statet.r.nico.AbstractRDbgController.submitFileCommandToConsole(AbstractRDbgController.java:845)
>> at
>> org.eclipse.statet.r.launching.SubmitFileViaCommandRunnable.run(SubmitFileViaCommandRunnable.java:88)
>> at
>> org.eclipse.statet.nico.core.runtime.ToolController.loopRunTask(ToolController.java:1260)
>> at
>> org.eclipse.statet.nico.core.runtime.ToolController.loopTopLevel(ToolController.java:1052)
>> at
>> org.eclipse.statet.nico.core.runtime.ToolController.run(ToolController.java:623)
>> at org.eclipse.statet.nico.core.runtime.ToolRunner.run(ToolRunner.java:93)
>> at
>> org.eclipse.statet.nico.core.runtime.ToolRunner.access$0(ToolRunner.java:91)
>> at
>> org.eclipse.statet.nico.core.runtime.ToolRunner$1.run(ToolRunner.java:105)
>>
>
>
> _______________________________________________
> statet-users mailing list
> statet-users@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/statet-users
>

Back to the top