I've had an issue that started yesterday with R Studio. When I install a package, even a small one, it fills the screen with an ever increasing progress line. The installation never finishes. The installation does finish in base R but the progress line still keeps growing. I'm running OSX Yosemite, R version 3.2.2, RStudio Version 0.99.893 (this also happens with the previous version of RStudio as well). Any ideas on why this may have started occurring? I teach a lot and use R, so I can pinpoint the change to yesterday morning, without any software changes to that point in previous weeks.
Related
I wrote a program about a month ago, and it worked fine. I haven't touched it since than, until today.
All of a sudden, I get the warning when opening Pycharm: "PyCharm has failed to load the environment from '/bin/zsh'. Integration with tools that rely on environment variables may work incorrectly." I couldn't find a good explanation and solution to this warning, without leaning out of my comfort zone of altering files on my computer.
When running the program I got the error message "Process finished with exit code 139 (interrupted by signal 11: SIGSEGV)". I have read that this error is related to a memory problem or, that a file needs to be closed.
I have cleaned the memory of my mac so far I know how to and all files are closed. The program reads from one file, but this is only one line, which has worked before and I don´t see how this could cause the error. Otherwise, I did write few other scripts in the same project over the last month, but that shouldn't be a cause of a memory issue, right?
Restarting Pycharm and my computer didn´t change anything.
The only other thing I can think of is, that I have updated my mac to Monterey version 12.2.1.
Could that be the cause for this behaviour? Did anyone else have a similar experience after this update?
And is it possible for the error message and Pycharms warning to be related?
I am thankful for any tip, that may help me understand this behaviour.
I was able to fix this issue through the following steps:
Updating PyCharm to the latest version
Within PyCharm going to File -> Invalidate Caches -> Checking all boxes -> Clicking "Invalidate and Restart"
(Previous attempts to Invalidate Caches with only the default boxes checked did not work for me, but checking all the boxes fixed the issue.)
I'm running in to an issue where my solution freezes when debugging. If I place a breakpoint at the beginning of the solution, it wont freeze and will allow me to either continue or step through just fine. With this solution however, I need it to start from a specific point in the code. When I try to start it from that specific point, it'll freeze, and the output and locals box will have a popup in each saying "Busy..". It did not have this issue a few days ago, but just started yesterday.
It only occurs to this specific solution (I can debug other solutions just fine). Using C#/.NET mostly.
Remedies I've tried: Clean/Rebuild, repair on installer, uninstall just app, uninstall app and associated files, running Release, code cleanup, upgrading/downgrading vos, placing breakpoint at beginning then jumping to next breakpoint at specified point, removing antivirus software temporarily
Running latest version of Visual Studios 19 Community at the moment.
I didn't find the solution necessarily, but deemed it to be an issue with the "Locals" box that displays all your local variables and values. If I close out of this, I can continue with debugging. From further research, it seems that tool has been known to be pretty buggy.
Not a programming problem per se, but rather a programming environment problem that I have been unable to find a solution to.
The problem relates to Adobe's Extendscript Toolkit (both 3.5 and 4), but so far I haven't been able to solve the problem, so here I am...
The error I get has appeared more or less over night. I didn't experience this problem yesterday, nor this morning. But exactly WHAT has happened is beyond me. I have removed preferences, I have uninstalled, reinstalled, created a new user, restored old preferences from Time Machine and I'm now pretty much lost for options.
Basically, nothing works in ESTK anymore. Just opening ESTK and entering alert('Hello') won't work. Neither will $.writeln(). Everything running from within ESTK seems to give the same error;
Cannot execute script in target engine 'main'
With details:
Cannot execute script in target engine 'main'!
(#1116) Can't start debug session.
Below is a screenshot taken from the new user I created to test, same problem.
The "funny" thing is that all the scripts (InDesign CS5, still hanging on to it for reasons) still work perfectly in the applications' script panels. So there is nothing wrong with the scripts (heck, they haven't changed one bit, and still refuses to run in ESTK).
As mentioned, I've tried installing the ESTK CC (version 4) as well, but the very same problem occurs there. Which leads me to think the problem lies somewhere else, but I do not know where, and why.
So, if anyone can shed any light on this issue, at all, I would be very happy. Debugging is basically the only thing ESTK is good for in my book, but now that even that functionality is gone, I don't know how to efficiently debug the scripts which is kind of hampering the workflow.
For reference, I'm running InDesign CS5 (from the old Creative Suite) on a 2008 Mac Pro with 10.11.6 (El Capitan) installed. Well aware that it's pretty out of date, but that is beside the point here.
In the above mentioned forum, Adobe has published a stable workaround!You just have to correct a setting inside the estk application:
Open the file(Mac): “/Applications/Adobe ExtendScript Toolkit CC/ExtendScript Toolkit.app/Contents/SharedSupport/Required/cdic/11BTBackend.jsx”
Search for the value: 604800000 (line reads bt.timeout = 604800000)
Replace that value with 604800 and save
Quit ExtendScript Toolkit and relaunch.
I can confirm that it works.
From the adobe Forum :
"we have found a first workaround: just change your date to any date before 20-nov-2018"
https://forums.adobe.com/message/10761440#10761440
Seems like a date issue :(
I just published a quick update about this on the Adobe Tech Blog.
For the time being, if you dismiss the dialog, you can still run your script via ESTK and step through code as usual.
Alternatively, if you really want to avoid the dialogs, and you don’t mind setting your clock back, you can sidestep the issue by setting your system clock back to November 19, 2018 or before. On most systems, changing the system time can have unintended side effects, so this isn’t recommended unless you’re really certain about it.
I'm working on an R package, bigKRLS. bigKRLS works on Windows RGui but encounters a fatal error on Windows RStudio. Some details...
Windows RGui works but Windows RStudio encounters a fatal error; confirmed on four different machines using R 3.3.0, 3.3.1, 3.3.3; RTools 3.3 and 3.4 following the best practices recommended by the Coatless Professor; RStudio 1.0.136; Windows 7 and 8. Presently, bigKRLS works on RStudio for Mac OS X Yosemite and Ubuntu 14.04 without issue.
bigKRLS depends on bigmemory, Rcpp, RcppArmadillo, and snow (but the problem pre-dates the recent addition of snow, which can be disabled for testing purposes by setting bigKRLS(..., Ncores = 1)).
devtools::install_github('rdrr1990/bigKRLS')
library(bigKRLS)
vignette("bigKRLS_basics")
set.seed(2017)
X <- matrix(runif(60), ncol=3)
y <- X %*% 3:1 + rnorm(20)
out <- bigKRLS(y, X)
summary(out)
The code above yields model estimates started with R2 = 0.663 (we've of course estimated lots more complicated models on other platforms).
Windows RStudio loads library(bigKRLS) without warning; bigKRLS() outputs that it's cleaned the data successfully. Among other things, that means y and X are now big.matrix objects. Then the first "real" step: bigKRLS() calls bGaussKernel(), which is where the session aborts after two minutes or so. But there doesn't seem to be anything wrong with bGaussKernel(). bGaussKernel() runs just fine if called from the command line in under a second. In fact, if you initialize each variable that bigKRLS() requires, you can run all of its code in Windows RStudio.
Currently, the package detects when Windows RStudio is being used and safely exits the function, directing users instead to RGui. Any suggestions as to a better a workaround would be greatly appreciated!
First, the problem on Windows is not related to the compiler. If you managed to install RTools correctly, then everything is going well for using RGUI. Instead, the problem that you are having seems to be with RStudio's use of Boost for their application that accidentally polluted calls to the boost namespace provided by the BH package in the rsession process. RStudio, more so #kevinushey, recently addressed this issue by creating a custom build of Boost for RStudio that lives within rstudio_boost. The details and solution of this error can be found in more depth at https://github.com/rstudio/rstudio/pull/1061.
Long story short, if this is indeed the case, simply check if the RStudio version is >=1.1.129 will suffice. To do so, you will first need to get an RStudio daily version. With this in hand, we can reference the solution that #DirkEddelbuettel derived for his fabulous anytime package that was running into this issue. Specifically, to overcome this, he has added a short isRStudio() function on package load and calls the function each time before handing data off into C++.
The isRStudio() function #DirkEddelbuettel uses is given as:
isRStudio <- if (Sys.getenv("RSTUDIO", unset="0") == "1" &&
exists("RStudio.Version") &&
## the following is evil but keeps R CMD check off our back
eval(parse(text=paste("RStudio.Version()$Version",
">=", "\"1.1.129\"")))) TRUE else FALSE
Note: The use of eval(parse(text=...)) is to avoid running into package check issues such as...
.onLoad: no visible global function definition for ‘RStudio.Version’
Undefined global functions or variables:
RStudio.Version
I've been using phantom.js on Windows 7 for quite some time now (I think v1.4.0 was the first version I used) and everything was always fine. But for some reason the process isn't properly terminated any longer when calling phantom.exit() and I absolutely don't know why.
The problem started to occur in v1.7.0, from one day to another. Everything once worked fine in 1.7.0 but then it did no more. Even after upgrading to 1.8.0 and now 1.9.0 it still doesnt work. The console just hangs. I can't type anything, phantomjs.exe is still listed in the list of processes in the taskmanager, even CTRL+C doesn't do anything. The whole thing is just frozen.
The underscore in the console blinks as if it expected more input but I can't type anything. The only chance I have is to close the cmd window using the [X] button which is totally dumb for automated testing.
I use the precompiled binaries I downloaded from http://phantomjs.org/ and as I said: it stopped working from one day to another. I even reinstalled it a few times, even to different folders but the process just doesn't get terminated any longer. Anyone who has an idea what the problem could be?
This is a known issue with the Nvidia drivers when you have two cards.
To resolve this issue you need to select "High-performance NVidia processor" in the NVidia control panel (NVidia Control Panel > Manage 3D Settings > Global Settings).
Read more here: https://github.com/ariya/phantomjs/issues/10845