I have done a clean install fuse on karaf at
C:\esb\redhatfusekaraf\fuse-karaf-7.8.0.fuse-780038-redhat-00001
FUSE_HOME environment variable is set to this directory.
I have OpenJDK installed at
C:\Program Files (x86)\AdoptOpenJDK\jdk-8.0.282.8-hotspot
PATH and JAVA_HOME are set properly and tested.
When I run fuse.bat from the above install here is what I get.
Microsoft Windows [Version 10.0.18363.1440]
(c) 2019 Microsoft Corporation. All rights reserved.
C:\Users\MO Tec>%FUSE_HOME%
'C:\esb\redhatfusekaraf\fuse-karaf-7.8.0.fuse-780038-redhat-00001' is not recognized as an internal or external command,
operable program or batch file.
C:\esb\redhatfusekaraf\fuse-karaf-7.8.0.fuse-780038-redhat-00001\bin>fuse
karaf.bat: Ignoring predefined value for KARAF_HOME
Red Hat Fuse starting up. Press Enter to open the shell now...
100% [========================================================================]
Karaf started in 2s. Bundle stats: 12 active, 13 total
No Fuse Shell. Anything else I can look at?
The problem was caused by a missing ">" in the maven settings.xml I discovered it trying to run an "mvn clean install" when maven crashed.
I fixed the missing ">" and not only did that command run and build success but the Fuse Console now appears.
Related
The problem
I'm trying to run the cordapp-example ("Basic" folder), but when I try to do that I get stuck at the deployNodes instruction by the following top error:
$ ./gradlew deployNodes
Starting a Gradle Daemon, 1 busy and 1 stopped Daemons could not be reused, use --status for details
> Task :workflows-java:deployNodes
Running Cordform task
Deleting C:\Users\auriaad\Desktop\JavaTest\samples-java\Basic\cordapp-example\workflows-java\build\nodes
Bootstrapping local test network in C:\Users\auriaad\Desktop\JavaTest\samples-java\Basic\cordapp-example\workflows-java\build\nodes
Generating node directory for Notary
Generating node directory for PartyA
Generating node directory for PartyB
Generating node directory for PartyC
2020-12-09 13:45:08,526 Execution worker for ':' Thread 4 INFO Cannot initialize scripting support because this JRE does not support it. java.lang.NoClassDefFoundError: javax/script/ScriptEngineManager
at org.apache.
The first time it was showing off errors continuously (at "executing" stage, 38%) and it almost crashed my machine because of resources consumption; so I stopped the process and made it run again, getting the aforementioned error.
What I tried
I checked I set the environment correctly, it appeared so.
I reinstalled the JDK and the JRE, hotspot version.
I deleted the folder of the sample and cloned it again
Additional info
$ java -version
openjdk version "1.8.0_275"
OpenJDK Runtime Environment (AdoptOpenJDK)(build 1.8.0_275-b01)
OpenJDK 64-Bit Server VM (AdoptOpenJDK)(build 25.275-b01, mixed mode)
Windows 10
JDK 8
IntelliJ
Gradle 5.6.4
I can't spot the problem, can you help me?
Apparently the problem was related to OpenJDK by Adopt.
After substituting it with the Zulu (supported) one, everything worked smoothly and the build was successful.
Fix:
Download Zulu Java 8 JDK https://www.azul.com/downloads/
Set the path of JAVA_HOME to '/Library/Java/JavaVirtualMachines/zulu-8.jdk/Contents/Home' with the command 'export JAVA_HOME=/Library/Java/JavaVirtualMachines/zulu-8.jdk/Contents/Home' (DO THIS IN YOUR IDEA TERMINAL)
Close Intellij and open again, go to file -> project structure -> select zulu as the SDK on the dropdown menu
Hope this helps someone
I am attempting to remotely debug a .NetCore application in Ubuntu Linux from Visual Studio 2019 in Windows 10. I can see the remote ipaddress (ping thru command line). I can RDT to the ipaddress. I can successfully transfer files to it via WinSCP.
I created a simple .NetCore "HelloWorld" app and copied onto the Linux VM.
I used the following commands to build and publish:
dotnet build -r linux-x64
dotnet publish --self-contained -r linux-x64
I ran the following command on the Linux VM to ensure that ssh is functional:
sudo apt-get install openssh-server unzip curl
The app is running on Linux.
From VS I try to attach to the process:
I get prompted for logon:
I get the following error:
Is there a step I'm missing somewhere?
Is there a configuration/permissions issue I am unaware of?
Thanks, JohnB
Microsoft has documented debugging a Linux target from a Windows development machine at https://learn.microsoft.com/en-us/visualstudio/debugger/remote-debugging-dotnet-core-linux-with-ssh?view=vs-2022
Unfortunately, using that method, you will need to manually deploy and manually attach the debugger. If you'd like Microsoft to change that, then it would be wise to upvote this issue: https://developercommunity.visualstudio.com/t/Convenient-way-to-add-a-remote-debug-con/917516
A 3rd party developer has created a Visual Studio extension that provides this missing feature to Visual Studio. It can be downloaded from https://github.com/radutomy/VSRemoteDebugger
I had the same problem initially because I didn't enter the connection target in the first screen.
After having entered the correct target myusername#192.168.178.95 in the first screen the second screen did not show up any longer and I got the expected list of processes
I want to run edumips.jar. Whenever I try to open, Java control panel is opened.
When I execute:
strong text
It is first time to download java and excecute .jar file.
What I want:
Please tell me what I'm doing wrong...
UPDATE: there is now an MSI installer for EduMIPS64 which allows you to install and run the simulator without worrying about installing a JRE and configuring it: https://github.com/EduMIPS64/edumips64/releases/download/v1.2.8/EduMIPS64-1.2.8.msi (version 1.2.8 was released at the time of updating this answer, there might be more recent ones).
You need to make sure the Java runtime is associated with the .jar extension to open it with double-click.
To open it once, try right-clicking on the JAR file select Open With... and find the Java runtime binary (it's "OpenJDK Platform Binary" on my Windows machine).
You may also be able to fix this by re-installing the Java Runtime (JRE): usually installers associate .jar files to the Java binary automatically.
Worst case, if Java is installed and the PATH is set up correctly, you can run it from the command line by using the command java -jar edumips64-1.2.6-standalone.jar.
To open the command line, press Win+x and choose Windows PowerShell. Your JAR might be in the Downloads directory so try java -jar Downloads\edumips64-1.2.6-standalone.jar.
I have downloaded .NET Core 3 (preview) and I have in Visual Studio 2019 (preview) created a hello world project consisting of class library and a console program. The program runs on Windows.
I have Windows Subsystem for Linux running Ubuntu 16.04 and I install dot net so that dotnet --info returns something (non error). Are there any other steps required?
If I go to my console apps binary folder and then shift+right mouse button click to get the 'Open Linux shell here' menu item and take that option then my Ubuntu window opens in the same directory as the console app executable.
From the bash prompt if I type the executable name (either with or without.exe) and of the correct casing it just reports 'Command not found'.
I am wondering what step I have missed.
The executable name is not a known command to the shell. You need dotnet <EXECUTABLENAME>
I’m trying to get sqlite3 to work in an electron app running on Windows7 and 10. Running the following command, I was able to create electron-v1.7-win32-x64\node_sqlite3.node
cd node_modules/sqlite3 && sudo npm install nan
&& sudo npm run prepublish && sudo node-gyp configure --module_name=node_sqlite3 --module_path=…/lib/binding/electron-v1.7-win32-x64
&& node-gyp rebuild --target=1.6.11 --arch=x64 --target_platform=win32 --dist-url=https://atom.io/download/atom-shell
--module_name=node_sqlite3 --module_path=…/lib/binding/electron-v1.7-win32-x64
However, I get Uncaught Error: %1 is not a valid Win32 application. \\?\c:\folder\ppt_win32-x64\resources\app\node_modules\sqlite3\lib\binding\electron-v1.7-win32-x64\node_sqlite3.node.
My node version is v7.4.0. Electron v1.6.11.
I was trying to compile for windows from mi Mac and I had that problem too, but after some readings I figured out how to proceed, and after all I can say that I got it. Yesterday I spent all day setting up a windows virtual machine in my (other) Linux laptop (I used my linux laptop just because my mac was exhausted in storage...). I was having too a problem with the preloadScript from electron main process in windows, Cant found the script, it was solved too.
Anyway, I think the library node printer from #tojocky is well maintained, in other hand in the electron-builder documentation they say that you should compile in native for natural reasons. Once you will have it, you'll see that it's a cleaner and pragmatic solution ...
This was my entire process, I hope it helps to someone having the same issue:
Get VirtualBox (or Parallels but is not free)
Get iso for W10
Create a VM with this W10 iso, and you should give to this VM some storage (because some dependency that you'll need to compile), I have assigned 60gb to this VM
Once I had that VM running, I just installed in that machine Visual Studio 2017 (with their build-tools included, it's necessary)
And then, I used CMD to make the rest
Install NodeJS (and NPM, but it comes with)
Install node-gyp globally
Install Python 2.7
Clone your project from git (in my case)
npm i (in your project), you should have as npm dependency in your package.json the module electron-builder of course. (here I had some troubles because when node-gyp tried to rebuild printer to generate the binary for windows it was failing, this was because it was imposible to find the python executable, so if you face this problem you should add it like:npm config set python "c:\Python27\python.exe" in my case )
Then try again npm i and Voila!
If you still having error you can rebuild the native dependency as well, run:
node-gyp rebuild --target=YOUR_ELECTRON_TARGET[eg: 1.8.4] --arch=YOUR_ARCH_TARGET[eg: x64 | ia32] --dist-url=https://atom.io/download/atom-shell
After all, you should make the build using electron-builder, in my case my npm script command was build --win --x64 but you can use the --ia32 flag as well for 32bits