The little red 'stop' button is disabled in my Anaconda-installed RStudio: I cannot use it to stop either a running Shiny app or dashboard and I cannot use it to interrupt Sys.sleep(30). I already reported this to RStudio and they confirmed that this behavior is unexpected, here. Has anybody else run into this? Any workarounds?
Related
We have a very bizarre situation that I can't seem to find a solution to online. When opening and using a terminal window on a Mac, a repetitive "~7" is being typed. I've attached a screenshot where I've tried to interrupt it with a Ctrl+C but to no avail. The same behavior does not occur if I open a text editor or any other program - just the terminal env has this problem. Does anyone have any idea what's happening?
Here's a screenshot of the OS and all other details:
In windows terminal (latest version) I am trying to open an Azure Cloud Shell. Functionality is working, however I am unable to read the display as when I set focus to the window, it becomes obscured (foreground shading is applied). When I select a different window, the terminal returns to normal.
Does anyone know how to change the theme to something useful or to turn off this foreground shading?
Regards
In writing out the bug as mentioned above I found I needed to delete my old settings file. Once I did this, and restarted terminal it started working.
I note when the azure shell is started, it briefly becomes transparent before updating itself.
Whenever UwAmp restarts itself (for example, when I modify php.ini or switch to a different version of php) it often crashes whatever Chrome pages I have opened, whether they are pages that I'm testing on UwAmp or something completely unrelated like Facebook. They go blank and I have to reload them. Sometimes it closes Chrome altogether, I have to restart it and I get the message saying that Chrome closed unexpectedly. What gives? Is this a known bug? Is there any way to prevent it? How and why does UwAmp even have control over Chrome? This is on Windows 10 x64, UwAmp 3.1.0, latest 64-bit Chrome.
Thanks!
EDIT: It just closed Notepad++ on me, so it's not specific to Chrome. There's also a message that pops up sometimes within UwAmp, saying that the process couldn't be killed because access was denied. Maybe UwAmp is trying to kill the wrong process? It also happens when I manually click the "Stop" button.
That's an issue I encounter too. If I exit UwAmp, sometimes it force closes another program (Firefox, qBittorrent, Spotify...)
I had reported this issue to the developer, but got no reply.
So, I guess we'll have to live with it.
When you start your session/computer, open first all the other softwares you wish to use (chrome, firefox, aBittorrent, Sportify or whatsoever). Then at the end, open uwamp.
It shouldn't crash down other softwares when you stop/start apache/mysql, or when you close down uwamp.
A workaround is to open uwamp.ini and change the AUTO_RESTAT_CONFIG_CHANGED to "0".
This will disable uWamp's auto-restart feature during server configuration changes.
I'm running Python 2.7 with ArcGIS Desktop 10.1 on Windows for Server (2 Xeon 2.13 Ghz processors).
Is it possible to suppress or automatically close the dialogue box from Windows that says "python.exe has stopped working" when python crashes? I have a continuously running, multiprocessing script that sometimes crashes for unknown reasons (working on that). When I click to close the crash report window, the script restarts and everything is okay. I want this to happen automatically until I can track down what is causing the crashes.
Thanks very much!
Doug
Procedure for disabling the Windows Debugger dialogue box found here:
http://msdn.microsoft.com/en-us/library/windows/desktop/bb204634(v=vs.85).aspx
This prevents the debug dialogue box that requires the user to click [Debug] or [Cancel] if python crashes.
However, there is now another Windows dialogue box that says "python.exe has stopped working. Please close the program" with a button [Close Program]. Sheesh!
The dialog you refer to is part of Windows Error Reporting.
The exact method varies between editions of Windows (Windows 7 instructions here, Google will happily provide for other versions...), but if you disable this feature of Windows, your crashes will happen a lot faster(!).
This is an simply an arcpy bug. You can try to avoid using the steps that are causing the crash, but it generally happens under different tools when used to process through a long list of data.
The only workaround I have found is to make my script save its progress along the way to disk so if you restart the process, it knows where to pickup from.
If you then disable windows debugger message by altering the registry (see below), you can then just repeatedly execute the script in cmd.exe until it completes the entire batch without having to close the process manually every time in between.
I know this is an awful workaround, but it is quite uncommon to have a python library kill off the python interpreter.
DWORD HKLM or HKCU\Software\Microsoft\Windows\Windows Error Reporting\DontShowUI = "1"
DWORD HKLM or HKCU\Software\Microsoft\Windows\Windows Error Reporting\Disabled = "1"
I recently installed the latest Pentadactyl nightly (as of 2-Nov-12) on FF 16.0.2, on OS X Mountain Lion. I am slowly coming to grips with the extensive options, however I cannot figure out how to use FireBug 1.10.6, which I had installed previously and was using.
I searched around a bit and found some bug reports which mentioned that installing AceBug would magically "fix" any issues, but I tried AceBug 1.10.0 and still no dice - how do I see and interact with the FireBug console, etc?
I found a Pentadactyl plugin called firebug-pentadactyl on Github that claims to add FireBug support to Pentadactyl but when I type:
:firebug console
...nothing happens. Who here is successfully using Pentadactyl with FireBug and can tell me what I'm doing wrong?
Thanks
Whoops, answered in the comments, but will repeat here:
This problem was due to the fact that the F12 "Open Firebug panel" hotkey is by default mapped to "Volume Up". If you hold Fn and press F12, the Dashboard is shown. I fixed this by going to System Preferences > Mission Control, and remapping the Dashboard shortcut to a different function key. Probably wouldn't be encountered by a Linux or Windows user.