CLI tools for Node.js Core collaborators
Promises/A+ conformant implementation
Windows hooker - intercepts system calls to make fullscreen programs running in a window, to support a better compatibility, to enhance video modes and to stretch timing. It is tipically very useful to run old windows games.
Resources for Mongoose
Markdown-formatted Creative Commons licenses
An express middlware to create a CMS with dust themes and formage as backend
Adblock Plus extension for Google Chrome
Facilitating joint collaboration amongst the TSC and CommComm
3. The fact that Fiji hangs at startup on some systems with the new launcher, but not with the old launcher, is a critical new bug, which we still don't understand. @haesleinhuepf On your affected system, please rename
debug.exeand run it, to see what's happening in more detail. If there's nothing helpful there, you can then generate a thread dump (ctrl+pause) to see if things are deadlocked on the Java side. Please paste any interesting findings here on this issue.
I'm seeing the above mentioned quick crash issue after updating just now (Windows 10 64bit Insider build 20185).
Following is the console output after renaming to
Detected Fiji Using JRE from ImageJ.cfg: D:\bin\tools\fiji/jre Found Java options in ImageJ.cfg: '-Xmx7560m -cp ij.jar' JRE not found in 'D:\bin\tools\fiji/jre' JAVA_HOME contains a JRE: 'D:\bin\tools\fiji/java/win64/jdk1.8.0_172//jre' java -Xmx7560m -Dpython.cachedir.skip=true -Dplugins.dir=D:\\bin\\tools\\fiji -Xincgc -XX:PermSize=128m -Dsun.java.command=ImageJ -Djava.class.path=D:\\bin\\tools\\fiji/jars/imagej-launcher-5.0.3.jar -Dimagej.dir=D:\\bin\\tools\\fiji -Dij.dir=D:\\bin\\tools\\fiji -Dfiji.dir=D:\\bin\\tools\\fiji -Dfiji.defaultLibPath=bin/server/jvm.dll -Dfiji.executable=D:\\bin\\tools\\fiji\\debug.exe -Dij.executable=D:\\bin\\tools\\fiji\\debug.exe -Djava.library.path=D:\\bin\\tools\\fiji/lib/win64;D:\\bin\\tools\\fiji/mm/win64 -Dsun.java2d.noddraw=true -Dij.debug=true -Dscijava.log.level=debug net.imagej.launcher.ClassLauncher -classpath D:\\bin\\tools\\fiji/jars/ij-1.53c.jar fiji.Main -port7 Using JAVA_HOME D:\bin\tools\fiji/java/win64/jdk1.8.0_172//jre Opening Java library D:\bin\tools\fiji/java/win64/jdk1.8.0_172//jre/bin/server/jvm.dll Java HotSpot(TM) 64-Bit Server VM warning: ignoring option PermSize=128m; support was removed in 8.0 Java HotSpot(TM) 64-Bit Server VM warning: Using incremental CMS is deprecated and will likely be removed in a future release Adding option: -Djava.home=D:\bin\tools\fiji/java/win64/jdk1.8.0_172/ Launching main class fiji.Main with parameters [-port7] Class loader = sun.misc.Launcher$AppClassLoader@c387f44 java.lang.ClassNotFoundException: fiji.Main at java.net.URLClassLoader.findClass(URLClassLoader.java:381) at java.lang.ClassLoader.loadClass(ClassLoader.java:424) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) at net.imagej.launcher.ClassLauncher.launch(ClassLauncher.java:264) at net.imagej.launcher.ClassLauncher.run(ClassLauncher.java:198) at net.imagej.launcher.ClassLauncher.main(ClassLauncher.java:89) java.lang.NullPointerException at net.imagej.launcher.ClassLauncher.launch(ClassLauncher.java:281) at net.imagej.launcher.ClassLauncher.run(ClassLauncher.java:198) at net.imagej.launcher.ClassLauncher.main(ClassLauncher.java:89)
comment created time in 3 months
PR opened mochajs/mocha
- Filling out the template is required. Any pull request that does not include enough information to be reviewed in a timely manner may be closed at the maintainers' discretion.
- All new code requires tests to ensure against regressions.
Description of the Change
We must be able to understand the design of your change from this description. Keep in mind that the maintainers and/or community members reviewing this PR may not be familiar with the subsystem. Please be verbose.
<!-- Explain what other alternates were considered and why the proposed version was selected -->
Why should this be in core?
<!-- Explain why this functionality should be in mocha as opposed to its own package -->
<!-- What benefits will be realized by the code change? -->
<!-- What are the possible side-effects or negative impacts of the code change? -->
Enter any applicable Issues here.
Mocha follows semantic versioning: http://semver.org
Is this a breaking change (major release)?
Is it an enhancement (minor release)?
Is it a bug fix, or does it not impact production code (patch release)? -->
pr created time in 3 months