Was so excited to explore the "remote development" feature on PyCharm, since I don't have enough computing resources to run on my local machine.
Spent an entire day trying to set it up in multiple remote machines, but all of them failed.
Approach 1 - let local IDE download remote IDE of the same version, failed with logs when I click on "Download and start IDE" option.
Approach 2 - installed the tar.gz IDE of the same version on remote, extracted it, and then ran remote-dev-server.sh registerBackendLocationForGateway resulted in the following o/p.
'/home/<user>/.cache/JetBrains/RemoteDev/userProvidedDist/_scratch_<user>_pycharm_2022.2.4' -> '/scratch/<user>/pycharm-2022.2.4'
after which followed approach 1, it had detected the IDE that I had installed on remote, but failed again with logs when I clicked on "Open and start IDE".
How can I debug this? What else can I look into?
Related
I am trying to connect to a remote server using JetBrains Gateway, so that I can use IntelliJ IDE for code changing purposes.
Both IntelliJ and JetBrains Gateway are -newly installed- on my device and I've rebooted my PC after installation as well.
I entered the hostname, password and it says that I'm "Successfully Connected".
But in the IDE version dropdown, nothing shows up even though I have IntelliJ installed on the system.
I do see the Other options... link. But the following options seem like they are to be used if no IDE is installed :
My Question is
How to get IntelliJ IDE (which is already installed) in the dropdown of JetBrains Gateway
You need to run a script to turn the server on
"The main script to run a remote IDE is remote-dev-server.sh, located in the bin subdirectory of your unpacked IDE"
From the Jetbrains instructions here
Runing the Build and Run Iot Edge Solution in Simulator stopped working suddenly, and the log builds the containers and stops at this message Network azure-iot-edge-dev is external, skipping Everything was working fine 5mins ago, tried rebooting, restarting docker, iotedgehubdev, but in vain. Do you know how can I get more logs and/or resolve this problem ?
This is a generic error that is thrown for a variety of reasons.
Possible causes can be:
Proxy blocking pulling images of edgeHub and edgeAgent
A problem in the deployment.template.json (or debug template), e.g. missing brackets
Ports of edgeHub that are in use
Docker configured for Windows containers when targeting Linux or visa-versa
The Build output or IoT hub output in Visual Studio usually gives a bit more information.
Do you know how can I get more logs and/or resolve this problem ?
Are you trying to debug/simulate it locally on windows 10 machine?
When you need to gather logs from an IoT Edge device, the most convenient way is to use the support-bundle command. By default, this command collects module, IoT Edge security manager and container engine logs, iotedge check JSON output, and other useful debug information. It compresses them into a single file for easy sharing. The support-bundle command is available in release 1.0.9 and later.
Run the support-bundle command with the --since flag to specify how long from the past you want to get logs. For example 6h will get logs since the last six hours, 6d since the last six days, 6m since the last six minutes and so on. Include the --help flag to see a complete list of options.
sudo iotedge support-bundle --since 6h
By default, the support-bundle command creates a zip file called support_bundle.zip in the directory where the command is called. Use the flag --output to specify a different path or file name for the output.
Incase if you are looking to debug the modules locally on VS2019, VS Code below documentations will be useful.
Use Visual Studio 2019 to develop and debug modules for Azure IoT Edge and
Use Visual Studio Code to develop and debug modules for Azure IoT Edge
Please share the complete logs if the above doesn't help.
I have this issue when trying to start a project from within Visual Studio when it's not running in administrator mode. I always forget and end up with this error. Same goes for if I run "iotedgehubdev.exe setup" from a command prompt. It only works when the command prompt is running in administrator mode.
I'm running Windows 10 with WSL2. I'm using VSCode with the Remote - WSL extension to open the files from my wsl file system.
When I boot my Windows laptop, and open VSCode I get the following error:
When I perform a wsl.exe --shutdown in PowerShell, and restart Docker Desktop, Everything works fine. But I have to do this after every laptop restart.
Remote WSL extension version: v0.51.4
Visual Studio Code version: v1.51.1
Windows version: 10.0.19041 Build 19041
Someone any idea?
I have had this problem several times, and I have found that on Windows 10 20H2 one of the two options described below solves the problem.
Network reset
This option can make you lose your network configuration, so use it with discretion and read every warning. You can perform this task by going to Settings > Network & Internet > Status. There you need to click on the option "Network reset" after that, you can start the network reset by clicking on "Reset now" Picture of Windows 10 20H2 status section. Then you will need to wait some minutes until your PC is restarted automatically and try to execute Visual Studio Code under WSL2 again.
Reset Windows
This option is dangerous as it will remove either all your files and programs or all your installed programs. You select what you want to remove before starting the reset process. This option can be performed by going to Settings > Update & Security > Recovery. Then you have to click on the button "Get started" on the section "Reset this PC" and follow the instructions provided by the reset tool Picture of Windows 10 20H2 recovery section. After your Windows is reset, you will have to configure your WSL again because all your WSL files will be lost when executing this operation.
I have a Mainframe/HOST Application to automate using Tosca 11.0, I am unable to scan/steer elements in mainframe screen.
Solution found in Tricentis Support -
The Tosca Host Engine is installed by default as part of a complete Tricentis Tosca installation.
All information regarding software versions and hardware requirements for the engine can be found in the "System Requirements for Tricentis Tosca".
The file PCSHLL32.DLL needs to exist in the system and the operating system needs to know the path to this file (with the system variable PATH).
The 3270 terminal emulation needs to be initialized correctly, so that the connection to the HOST system to be tested can be established. Additional information is available from your system administrator.
I couldn't locate PCSHLL32.DLL in my PC.
Has anyone faced same issue? can someone help where to get PCSHLL32.DLL and get HOST engine working.
I had this problem for a while. I kept trying to figure out how to install the Host module because I couldn't find that PCSHLL32.DLL on my system...
Turns out HOST was already there... I just had to get Tosca Commander configured to find my terminal app (I'm using QWS3720 from Jolly Giant).
Try this - Go into Tosca Settings, and go to Settings > Special Engines > HostEngine> Emulation Environment and check the following settings:
1) Emulation Title: this should be the window title of your terminal emulator. * works as a wildcard. Since QWS3270 changes it's window name to match it's session, we just use * in this field.
2) Emulation Type: try to find your terminal emulator's maker listed here... Mine is set to Jolly Giant.
3) Session ID: this is the important one. This is the HLLAPI ID of the term window, basically the handle that automation needs to know to "see into" the terminal window. it seems to typically be set to "A" (same as with QuickTest Pro/UFT).
Once these settings are correct, then TRY to scan your terminal window. Launch your terminal emulator first, CONNECT with it (to start up the HLLAPI), then run Tosca's scanner - just don't expect it to scan like web pages, it will use the older scanner. Select Scan Application > Other... and it will start the older "Tosca Wizard". Click Scan, then point to your Terminal emulator. If you see the little box showing "Recognized Wizard >HOSTEngine
Good Luck!
I develop locally using PhpStorm, Git and VirtualBox on my local machine. I use Git to handle the process of moving work to staging or production environments. Currently I'm using MobaXterm (an excellent free tabbed ssh client for windows) to have terminal access to do things on staging and production servers. PhpStorm has a local terminal built in, but how would I use it to have multiple ssh terminal access? (This way I can have local, remote staging, and remote production terminal access all from within my IDE)
Figured it out!
On a fresh copy, PhpStorm will have Tools > Terminal to bring up the local terminal. To have additional ssh terminal access, this is what I did...
Setup servers
1.1) File > Settings > (Type: "Deployment" into the search box)
1.2) Hit the + button and fill in the necessary fields into the connection tab.
1.3) Click on the "Mappings" tab and clear the field "Local path"
since we will only be using the terminal.
1.4) Repeat Steps 1.2 and 1.3 for each server you want a terminal tab for.
1.5) Don't set any of these as default, so that you will be prompted to choose
a server in Step #2 below...
Start a remote terminal tab (this will also open up local terminal)
2.1) Tools > Start SSH session (this option doesn't appear until Step #1 is
completed)
2.2) You will be prompted to select a server from Step #1.
The terminal window appears and a new tab appears next to "local" in the
terminal window.
EDIT: (Thanks to Dan Dascalescu) you may want to also ensure the SSH Remote Run plugin is enabled. It's enabled by default in PhpStorm 8 (not sure about earlier versions).
PhpStorm has a plugin called "SSH Remote Run".
See also the built-in terminal.