Using the installation guide link provided by one of the stack overflow user, I have build Hydrograph on my machine.
I followed the steps line by line as per the document to compile the Hydrograph git code and found that it generates 3 different versions of Hydrograph (macOS, Windows and Linux). This consumed almost 2 GB of additional space on my Mac. I do not need Windows and Linux version. Is this correct behavior of the compilation/build process??
Before reaching out to stack overflow community, I had reported the issue on Hydrograph public GitHub repository but haven't got any response.
Reported Issue is here.
-ira wati
The Hydrograph(UI) is designed to work on Windows, mac and linux OS(and tested very well for Windows 64bit and Mac). That's why it has POM which creates different builds for OS,Windows and Mac. You can update the POM to create build for specific OS.
Related
We’ve been trying to get SikuliX 2.0.5 to run on a RHEL 8 system, and not having much luck.
We went through the instructions on this webpage:
https://sikulix-2014.readthedocs.io/en/latest/newslinux.html#newslinux
We started on RHEL 7, but the OpenCV shared library required a newer version of GLIBC than is standard on RHEL 7 (version ‘GLIBC_2.27’ not found (required by ~/.Sikulix/SikuliLibs/libopencv_java430.so)), so we moved up to RHEL 8. We had to build OpenCV (v4.3.0) from source because we could not find a java companion package for RHEL 8, which required quite a few other dependencies, but in the end we got it built with most options enabled, and installed as root on the system. We also got Tesseract installed via a package, as well as xdotool and wmctrl.
We are setting LD_LIBRARY_PATH to ensure that the OpenCV libs are picked up, and when we run with the “-v -c” options to the IDE, there are no obvious problems reported. It seems to believe it is moving the mouse, though we can see that it is not, and when we try to capture a screenshot, the “canvas” from which to capture is either uninitialized/garbage frame buffer memory, or a totally black screen. On rare occasions we have seen the actual desktop, but most times we do not.
Originally the system had 2 monitors, but was subsequently reconfigured to a single display system. We were originally running remotely over NoMachine, but have also tried running locally and observed no difference in behavior.
Any pointers or suggestions would be most welcome. Given that no error messages are being reported, we are out of ideas for how to proceed in debugging the problem. It appears that more native support is provided for Debian-based systems, but we’re attempting to validate a product which only advertises support for RHEL systems, so we’d prefer to get it working in this environment if at all possible.
SNMPFWD is discussion forum is hosted on stack overflow and object items discussed can not be found. In trying to implement a windows based portion of the package no code links are available.
It looks like SNMPFWD is a Python library. It can be installed by running pip install snmpfwd on a command line.
You'll need to have Python installed on your windows system to do so. You can download the latest Python release for Windows here: https://www.python.org/downloads/windows/
My company is using an old CentOS6 and they wont update it before months (years?). This is totally out of my control and it obviously makes using up to date software a nightmare.
I would like to use Visual Studio Code as a C++ IDE but its intellisense plugin is running with glibc >=2.14 and Centos6 comes with glibc 2.12.
It also needed some more dependencies I managed to recompile and load with LD_LIBRARY_PATH. I tried compiling a new glibc and load it as well but it segfault, as expected.
I used the compiled version of VSCode from the official website.
I tried compiling it myself but it requires to download many files and my virtual machine does not have Internet, I can only transfer files through ftp. I created a local yarn repository, compiled all appropriate version of Yarn, NodeJS but a compiled binary is trying to download electron and I have no idea where to put the file to trick him into thinking it's downloaded already (assuming I could).
There are standalone solutions to run software on old distribution, like AppImage but VSCode is not part of their apps.
Would you have any idea on how to run VSCode on Centos6? Did you ever try to compile VSCode without and Internet Connection?
Currently the only viable solution I see would be to create an AppImage at home.
To run VS Code Server on CentOS 6, I followed the "glibc and libstdc ++ on RHEL / CentOS 6 update" article from here.
Perhaps this option will help you.
What's missing in dbgeng.dll in windows 7 Vs the dbgeng.dll distributed with debugging tools for windows ?
Very late to the party on this one but I've run into one very significant difference recently:
The dbgeng.dll built into windows installations will not support remote debugging where as the one installed with debugging tools does!
There appear to be other differences also that I didn't dig deeper into - all I knew was a working program using the built in dll started crashing when using the debugging tools one... which was a pain considering I would have liked to use the remote debugging facility out of the box.
This post shows the difference between Windows 7 and Windows 8 preview, I believe Windows 8 version is similar or possibly same as latest one that ships that is in debugging tools because when I do use dependencyWalker I notice that the one in Debugging Tools also has this new exported method DebugCreateEx which is also in the latest version
Windows 7 System 32 version:
Dependency walker:
Debugging tools version:
Dependency walker:
Hope this helps in some way to explain the differences, especially the post at the top.
I have a very strange issue that I'm hoping someone can help me with. I have various installations of Eclipse on my development machine at work. The one I primarily use is Weblogic WorkSpace Studio 10.2. This installation, along with a few Pulse installations I have set up works fine when I'm logged into my computer physically.
However, when I try to log into the computer using Microsoft's Remote Desktop Connection utility I get an error stating: "Could not create Java virtual machine." and then I get the lovely Eclipse error box which I personally can gather almost nothing from.
Even if you don't have the solution, any help would be greatly appreciated.
Justin
What ended up working for me was the memory settings for the JVM. Apparently the remote desktop connection, or some other setting in Windows, blocks off a fairly large amount of space. By reducing the heap size allocation for the JVM during Eclipse and server start-up I was able to get this working. As a side note, I had PLENTY of space that windows could have used, so I don't think blankly adding more memory would necessarily solve the issue. If you find another solution, please let me know.
• We came across an issue when user RDC’s to a remote system where the OS is Windows 10 and has a running Eclipse instance, the Eclipse instance terminates
• Eclipse is one of the IDE’s for Java
• The issue is because of Windows 10 Exploit protection
• Pre-requisite: You will need Administrative permissions for executing the below
• Navigate to Settings -> Update & Security -> Windows Security -> App & Browser Control -> Exploit Protection Settings
• Add the program to exclude as below
P.s. As of Window 10 1909 MS security advisory mentions we can disable some exploit protections by default.
Perhaps it is permission related. take a look at similar issue that symantec has:
http://service1.symantec.com/support/ent-security.nsf/854fa02b4f5013678825731a007d06af/8ea1593f1d1fcee68025759a003d8403?OpenDocument
Try to see if you have same patches installed that causes the security issue. Also refer to application log to see if there is a more specific error. Good luck :)
I think issue happens due to Windows, not Eclipse nor JVM. There is still open Bug report on the Eclipse side and one of the comments state that Microsoft is working on the issue.
I have tried Windows Remote Desktop-ing into my dev machine at work (which had only one version of eclipse installed on it). I had no troubles.
Is it possible that your problems stem from multiple versions of eclipse running at the same time?
Also, have you tried a fresh install of eclipse on your dev machine?
If the above two suggestions don't work, then the only thing that I can think of is what Mohammad said: you might need to check your permissions.
I would check the system log if I were you: Start > run > eventvwr
The first thing to look at is the .log file which is in your eclipse's metadata folder (found in your workspace at $WORKSPACE_ROOT/.metadata/.log). If you post the stack trace that it generates upon initialization, we can give a definitive answer.
I am now experiencing this in Eclipse (the Oxygen release and Java 1.8.0_181). I previously had the same problem with another Java-based program (Oxygen XML/XSL editor - the product name is coincidentally the same as the Eclipse version). Last year the Oxygen support team answered that it may be a known problem in Java.
Even without seeing a crash report, considering your sequence of
events, this seems like a known common cause of crash for the Java
runtime. Keeping Oxygen/Java running for a long time, until the screen
or video card enters sleep then connecting/disconnecting
screens/projectors or connecting/disconnecting RDP can trigger a crash
in the Java runtime. We keep updating the Java runtime (JRE) with each
new version of Oxygen, but so far the issue has not been resolved in
newer versions of the JRE.
e.g. Java VM logged issue:
https://bugs.openjdk.java.net/browse/JDK-8153389