When starting ./build/nodes/deployNodes in macOS Mojave 10.14.1, the terminal opens but does not start up the tabs corresponding to each node defined in the deployNodes task in Gradle.
Specifically looking at the tutorial section here.
Anyone have a solution?
To fix this, go to System Preferences -> Security and Privacy -> Privacy -> Accessibility and make sure that Terminal is in the list and checked (enabled).
If you are running nodes from IntelliJ terminal you have to add it and Terminal to Accessibility and Automation sections.
Accessibility:
Automation:
I am facing the same issue (on Mojave) even after adding Intellij and terminal to accessibility and automation.
The work around is to manually start the nodes via; java -jar corda.jar in each nodes directory.
I managed to fix this issue by resetting security permissions on OSX. I could not work out how to add Java into the Accessability group.
Conditions apply in this paragraph! If you type 'tccutil reset AppleEvents' in a Terminal then this will clear all the security associations. Then when you run applications again you'll get prompted to allow or block. So if you do this, then try ./runnodes again you should see a bunch of dialogs which you can click yes to. The nodes should now start ok.
Also, in your security settings you should see 'Java' appear in the Accessibility group.
Instead of accessibility and automation, to make this work on Catalina 10.15.7 I had to add terminal to the Developer Tools section instead of accessibility and automation:
Related
Apologies if I've gotten the terminology wrong. I'm following the vignette on R selenium to the letter, and so I'm using version 2.53.1 of the standalone firefox web driver in docker:
docker run -d -p 5901:5900 -p 127.0.0.1:4445:4444 --link http-server selenium/standalone-firefox-debug:2.53.1
I'm playing around trying to fetch my student data automatically from my university, and so far I've managed to choose the correct university from a list, logging in with my username/password and clicking the "my education" button. Here I get stuck. It doesn't matter if I click the link in the debug tool (that would be tightVNC Viewer) or if I tell the script which links should be clicked. I end up with an empty page with just the word "filter" on it:
This doesn't seem to happen when I use regular firefox:
Also, for some reason the first page is in English why the second is not.
Since the issue remains the same regardless if I use commands or the debug tool the issue might be the web driver I think. Should I still be using version 2.53.1 or is there a newer, better version out there?
Which one in that case?
If I'm on the wrong track and the problem is something else entirely then please tell me so!
I've been trying to build a CordApp and I downloaded the template from GitHub. The code that I've written is available on the following link:
https://github.com/shanmukhipriya99/taskcordapp
When I'm trying to run gradlew.bat deployNodes in the cmd terminal, this is what I got:
[gradlew.bat deployNodes]
Then when I run build\nodes\runnodes in the cmd terminal, this is what I got:
[build\nodes\runnodes]
Then I have three other terminal windows opening-up, they load the Corda part, show some red text that says something about the developer mode and all the node terminals get closed automatically before I'm able to read the entire text.
Can someone please help me in figuring out where I'm wrong!?
Thanks in advance!
It looks like you have had successfully started the nodes all in one terminal. I am not entirely sure, if this is the only issue, but I have seen this issue before. This is caused by lack of permission of the Terminal.
I have seen it happened for both Windows and Unix/Macos users. To resolve it you might need to grant the permission to Terminal manually.
If it still does not work out, I would actually suggest the alternative quick fix that Ashutosh mentioned in comment. Open a new tab and go to the root folder of each nodecd /build/nodes/XXX, and start the node manually via java -jar corda.jar
I'm using the vertex theme from https://github.com/lcpz/awesome-copycats. However, I'm seeing several applications in the context-sensitive menu which I don't even have installed, and want to remove them. For example, AVAHI SSH Session, IntelliJ IDEA, and urxvt (tabbed). When I select any of these items nothing happens. If I install IntelliJ through my package manager (pacman on my arch system) then I get a second entry for IntelliJ and that one actually launches the program. Also it's annoying that Visual Studio Code is in the Accessories submenu. I want it in the Development submenu.
I finally figured it out by accident. I was just researching how to configure VLC media player skins, and on their website, they describe where to place the skins. Under $HOME/.local/share/applications I found a directory called jetbrains-idea-ce.desktop. I simply moved the "applications" folder to $HOME and restarted awesome wm. Now the old and icon-less IntelliJ entry in the context-sensitve menu is gone. Answering my own question for posterity in case someone finds it useful.
I am running a launcher in publish instance,the launcher doesn't invoke the workflow when run mode is publish or publish and author but it works when I make run mode as author
Can someone help me with this behaviour of AEM?
Wrokflow launchers are tied to run-modes and you can change the behavior to run to either or both of them. The default dialog height is less hence it is not visible you need to scroll down.
Taken from the Adobe documentation:
When using one of the above run modes (author, publish, samplecontent, nosamplecontent), the value used at installation time defines the run mode for the entire lifetime of that installation.
For these run modes you cannot change them after installation.
You cannot use runmodes author AND publish at the same time (I wonder what AEM will do if you try to set both runmodes) and switching the runmode is also a bad idea.
See https://docs.adobe.com/docs/en/aem/6-0/deploy/configuring/configure-runmodes.html for details.
There must be something wrong with your instance. Any log messages?
I'm trying to get XCode 4 to symbolicate a crash report. I've googled and followed this link (https://github.com/chrispix/symbolicatecrash-fix) but get stopped. The instructions say "To fix your iOS crash report symbolication, move /usr/local/bin/symbolicatecrash aside and copy in the version in this repo." Well, I cannot find "/usr/local/bin/" on my Mac. I'm new to the Mac world, so I'm sure there's something I'm not understanding. If "/usr/local/bin/" doesn't exist, then where is XCode 4 finding symbolicatecrash? Please point a newbie in the right direction as I have a lot of bugs to be fixing.
Thanks
Tom
that tool has been relocated to /Developer/Platforms/iPhoneOS.platform/Developer/Library/PrivateFrameworks/DTDeviceKit.framework/Versions/A/Resources/symbolicatecrash in newer version of the SDK
you would run it as:
./symbolicatecrash -A -v [crashlog-filename] MyApp.dSYM
keep in mind this is for iOS only, for OSX see http://developer.apple.com/tools/xcode/symbolizingcrashdumps.html (for the app to contain the symbols "DWARF with dSYM" must be enabled in it's build settings)
you would run it as:
./symbolizecrashlog [application-name] [crashlog-filename] > symbolized.crash
I would like to add that all this usually is done automatically, these manual approaches are for cases when there are issues with the system symbols database as discussed in Xcode 4 failure to symbolicate Crash Log