I am using Goland 2021.3.3. In older versions it used to pop up a confirmation box if a run configuration was already running when the Debug or Run button was pressed. Having been using VS for about 20 years, where the green right arrow meant Continue, I keep hitting it when I mean F9 and losing the place in the debugger. Can this warning a setting I can re-enable or has it just been removed?
Preferences/Settings | Advanced Settings | Confirm rerun with process termination.
Related
Quick question - do you know what to do if my console constantly stalls and I cant get out apart from closing and reopening the console? it happens only when debugger line is activated (import pdb; pdb.set_trace()). Stall is happening once some debugger operation finishes. after I type the next command in the debugger line - i cant hit enter. I can move my cursor in the debugger command line but otherwise it is not responding even to forced keyboard commands Contrl-C. I can only close console and reopen - and even then it takes 10 seconds delay. To do it 50 times - a bit annoying. no answers on internet. did submit feedback to spyder but no answer so far. Any hints you might have?
I am attempting to set up automated testing for my iOS app using TeamCity. Currently, my agent builds, but once building the last target and running codesign, it hangs and displays the following:
[19:29:34][CodeSign] CodeSign /var/root/Library/Developer/Xcode/DerivedData/MyProductiOS-fgkoogiimhlbckdlbckzmqfyaoff/Build/Products/Debug-iphonesimulator/MyProductiOSUITests-Runner.app/PlugIns/MyProductiOSUITests.xctest
[19:29:34][CodeSign] cd /Users/ericmiller/.tcagent/work/f9abef315a0137d4
[19:29:34][CodeSign] export CODESIGN_ALLOCATE=/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/codesign_allocate
[19:29:34][CodeSign] export PATH="/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/usr/bin:/Applications/Xcode.app/Contents/Developer/usr/bin:/Users/ericmiller/.pyenv/shims:/Users/ericmiller/.rbenv/shims:/Users/ericmiller/.pyenv/shims:/Users/ericmiller/Scripts:/usr/local/sbin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/opt/X11/bin:/opt/local/bin"
[19:29:34][CodeSign] Signing Identity: "-"
[19:29:34][CodeSign] /usr/bin/codesign --force --sign - --timestamp=none /var/root/Library/Developer/Xcode/DerivedData/MyProductiOS-fgkoogiimhlbckdlbckzmqfyaoff/Build/Products/Debug-iphonesimulator/MyProductiOSUITests-Runner.app/PlugIns/MyProductiOSUITests.xctest
[19:29:34][CodeSign] /var/root/Library/Developer/Xcode/DerivedData/MyProductiOS-fgkoogiimhlbckdlbckzmqfyaoff/Build/Products/Debug-iphonesimulator/MyProductiOSUITests-Runner.app/PlugIns/MyProductiOSUITests.xctest: replacing existing signature
[19:31:32][CodeSign] 2017-01-22 19:31:32.279 xcodebuild[28262:86807] iOSSimulator: Timed out waiting 120 seconds for simulator to boot, current state is 1.
[19:31:32][CodeSign] 2017-01-22 19:31:32.290 xcodebuild[28262:86805] iOSSimulator: Timed out waiting 120 seconds for simulator to boot, current state is 1.
[19:31:32][CodeSign] 2017-01-22 19:31:32.291 xcodebuild[28262:86797] Error Domain=IDETestOperationsObserverErrorDomain Code=3 "Timed out waiting 120 seconds for simulator to boot, current state is 1. If you believe this error represents a bug, please attach the log file at /var/root/Library/Developer/Xcode/DerivedData/MyProductiOS-fgkoogiimhlbckdlbckzmqfyaoff/Logs/Test/89F7C786-9E91-419F-98CA-F36385618DC2/Session-MyProductiOSTests-2017-01-22_192932-E95vcV.log" UserInfo={NSLocalizedDescription=Timed out waiting 120 seconds for simulator to boot, current state is 1. If you believe this error represents a bug, please attach the log file at /var/root/Library/Developer/Xcode/DerivedData/MyProductiOS-fgkoogiimhlbckdlbckzmqfyaoff/Logs/Test/89F7C786-9E91-419F-98CA-F36385618DC2/Session-MyProductiOSTests-2017-01-22_192932-E95vcV.log}
[19:31:32][CodeSign] 2017-01-22 19:31:32.291 xcodebuild[28262:86797] Error Domain=IDETestOperationsObserverErrorDomain Code=3 "Timed out waiting 120 seconds for simulator to boot, current state is 1. If you believe this error represents a bug, please attach the log file at /var/root/Library/Developer/Xcode/DerivedData/MyProductiOS-fgkoogiimhlbckdlbckzmqfyaoff/Logs/Test/89F7C786-9E91-419F-98CA-F36385618DC2/Session-MyProductiOSUITests-2017-01-22_192932-mrX7wQ.log" UserInfo={NSLocalizedDescription=Timed out waiting 120 seconds for simulator to boot, current state is 1. If you believe this error represents a bug, please attach the log file at /var/root/Library/Developer/Xcode/DerivedData/MyProductiOS-fgkoogiimhlbckdlbckzmqfyaoff/Logs/Test/89F7C786-9E91-419F-98CA-F36385618DC2/Session-MyProductiOSUITests-2017-01-22_192932-mrX7wQ.log}
The simulator app is open in the dock. Clicking on the simulator does nothing, but if I right-click and select the window, I can see that the simulator is indeed running but is not displaying anything. Example
I'm looking for a workaround to test my code, without switching to a physical device instead of a simulator if possible. How can I achieve this goal, and what could be wrong with my configuration?
EDIT:
Sven Driemecker found the solution. Here's my configuration.
Before running the xcodebuild, I run the following shell script to ensure a sanitary testing environment.
xcrun simctl shutdown %env.simulator_guid%
killall Simulator
killall com.apple.CoreSimulator.CoreSimulatorService
xcrun simctl erase %env.simulator_guid%
Then, when running the xcodebuild, add the following option:
-destination "id=%env.simulator_guid%"
And finally, to clean everything up:
xcrun simctl shutdown %env.simulator_guid%
killall Simulator
killall com.apple.CoreSimulator.CoreSimulatorService
Update: Here's a blog post I wrote about how to set up basic TeamCity CI for XCode/iOS.
I have been experiencing a similar error when attempting to run an iOS app in the simulator from Xcode 11.3.1. I have found that re-choosing the virtual hardware can resolve this issue a little quicker than other solutions mentioned on this page.
When I receive the "Timed out waiting for Simulator.app to become ready" error in Xcode, the Simulator.app has typically launched but shows no actual simulator. Choosing Hardware > Device > [OS version] -> [Simulator Name] causes the simulator to appear and successfully launch my app on the next run attempt.
It seems pretty odd, but simply resetting the simulator usually fixes this. We often encounter the same error on our own CI-system.
Try Simulator-Menu -> Reset Content and Settings, then restart the simulator.
You can enforce this on the command line, but I won't recommend it, cause it will slow down your build remarkably.
There is a bug in Xcode 11.3 and earlier which could manifest this way if you have Simulator.app running from another Xcode. There is a small race window in which this could happen. That was fixed in Xcode 11.3.1.
but...
There is a bug in Xcode 11.3.1 and later (through Xcode 11.4.1 as of this comment) which manifests this way as well. To workaround the issue, you can click on Simulator.app in Dock after it launches (even if it is foreground). Alternatively, you can enable pasteboard synchronization in Simulator.app via 'Edit -> Automatically Sync Pasteboard'.
I have not found a good solution to fix the root cause of this issue, but I have found a work around. If you simply open simulator before building your app in Xcode this issue is bypassed.
Just killing and reopening the simulator worked for me.
You can also check the Window menu of the Simulator app.
There could be one or more Simulator windows that are marked as using an [External Display]. When you select a window from the menu nothing will appear, however you will be able to press Cmd-W to close it.
After you've closed all windows using an External Display, the Simulator will start working properly again.
I am uncertain how one can select an External Display for a simulator, however it has happened to me a few times and just quitting the Simulator app did not help. I had to either do what I describe above, or restart the machine.
I'm currently on my third attempt trying to install Visual Studio 2015 on this computer. I have tried rebooting, hard shut downs, canceling setup and restarting, etc. Each time, it gets stuck at applying Microsoft ASP.net. I have tried leaving it overnight (12 hours). My download speed is 50-60 MBPS according to Ookla Speedtest. I am running Windows 10. I did do a "custom" installation and added C++, Python, and the Git extension. If I am not mistaken it said 7 GB size. Why is it doing this? Please help!
I don't understand why this isn't working because I installed VS 2015 for my laptop (a different computer) just a few days ago on a relatives WIFI and their speed was 3-7 MBPS.
(Note: The installer is not technically frozen since the loading dots on the bottom are moving.) However, bar hasn't filled up at all for like 6 hours.
EDIT:
Do I need ASP.NET (for C#, Python, and maybe C++)? Can I uncheck certain features for installation so that it wont try to install this? Also, when I cancel installation it never cancels and just stays there so I have to kill the installer with the task manager. This is getting incredibly frustrating.
Fixed it...
Easiest way is "threaten" to shut down the computer. Go into Power, restart system. You will be warned that there is a logging program which will not let the system reset. Cancel that program and then do NOT restart.
Installer immediately went on to next part and finished install after having been stuck for 6 hours...
I got it to work, it wasn't perfect, but here is what I did: It was getting stuck at very certain points, most notably ASP.NET. I did a little research and got an idea from something I read (I unfourtunetly can't find the source again). Sometimes windows opens invisible "confirm" type windows or installer windows that get stuck. When the installer got stuck I opened up task manager -> details, than checked On the visual studio process by right clicking then clicking analyzing wait chain. This showed me what process the VS install was waiting for. Then, I'd just kill the process. Messy, I know, but better then nothing. I had to do that 2 or 3 times. Afterward it said it installed correctly with 2 components that had warnings. ASP.NET was included. But everything else worked fine (c#, C++) Later I went back and did a repair. That worked pretty smooth. Finally, I installed the Python Tools successfully. (that part is sort of irrelevant but the point was that everything is now working fine).
edit, found another source: Visual Studio 2015 Community Edition Installation Stuck In Windows 10
Yes i had this problem too. To solve this open task manager and go to details tab then search for TiWorker.exe, right click on it and choose analyzing wait chain it will display many instances of the process that are in waiting mode , check all those processes and terminate them after doing this the installer will go to the next step.
To avoid this problem, you have to install IIS first.
Go to Control Panel -> Programs -> Turn Windows features on or off -> Select "Internet Information Services" -> OK
I had this problem a couple of hours before writing this answer and what worked for me was:
I opened other programs at least two or three and went to power and clicked on restart as usual it will warn you about open programs that need too be closed before shutdown or programs that are currently active I then clicked on force close and it closed the first program that I recently opened then I quickly clicked on cancel. Two minutes later instalation was back on track
Press Ctrl+Shift+Esc, then go to Tiworker.exe and terminate all the waiting processes.
I found a solution to this headache of a process to install Visual Studio. If you have tried everything and nothing seams to be working for you even by trying the command line shell then try this.
Go open task manager while running the installer and kill wusa.exe. It will kill the process to search for the update and continue the installation. You may have to kill some other processes as well if they get stuck. Its not great but it seams to be working.
wusa.exe seams to be the task that is the problem that prevents the installer from moving to the next step. This could be because your computer can not reach the update server.
This seams to be the case for both the Community and Enterprise Version of Visual Studio.
I'm trying to install subclipse 1.6.x onto Aptana Studio 3 (build 3.0.7.201112151935). It isn't working cause once I've clicked that I accept the licence agreements the finish button doesn't light up.
I've tried rolling back the configuration history, closing and reopening and installing 1.8.x. 1.8.x worked once, but isn't compatible with my SVN repo so that's no use.
Any guesses/solutions?
Thanks in advance
Rob
There is a bug in Eclipse where the Finish button does not show up. It was fixed, but maybe Aptana is not using the latest version. I seem to recall you could click Back and then Next and the button would enable.
Here are some Eclipse bugs on this:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=136907
https://bugs.eclipse.org/bugs/show_bug.cgi?id=149300
For me I found that there were sub-packages which couldn't be installed.
Bad Components:
Mylyn
Revision graph
These were identified as bad on the sub-components selection screen, however, when this is done, and the licenses are accepted, the "Finish" button does not get highlighted.
I Found that if you remove this bad components on the initial "Available Software" screen (and not on the sub-componets selection screen) and continue, that you the "Finish" button gets highlighted and you can proceed with installation.
I would like to know if it is possible to configure Dr. Watson to silently dump a crashing process without popping up any error dialog box?
We need this because I run a set of integration tests with some applications. We don't want the tests to be blocked by an error message box. We need a way to make Dr. Watson silent but still dump the image when the process crashes.
Best,
Dr.Watson itself is silent by default. anyway, if you want to control the way Dr.Watson works, enter "drwtsn32.exe" at a command prompt to display the configuration dialog for this software. also, to install Dr.Watson as the default debugger, use "drwtsn32.exe -i".
the settings for the default debugger is stored in the registry at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AeDebug. the Auto value should be set to 1 for the system to automatically launch the default debugger. in your case, it is mandatory to set this value to 1.
once all the above things are setup, you can instruct Windows to stop displaying the "X has encountered a problem and needs to close" dialog. on Windows XP, this is controlled in the System Control Panel, on the Advanced tab, the Error reporting button on the bottom of the dialog allows to control how the system reacts when an error occurs. (on other versions of Windows, there should be something similar, search for "Error reporting" on Google)
with the debugger set to auto, Dr.Watson properly configured and error reporting disabled, the system should not show any dialog when a crash occurs.