Last week, without any changing of our configurations or dependencies, our builds started failing.
The errors we are getting during any run of any karma tests are along the lines of:
26 03 2018 10:25:34.870:INFO [framework.detect-browsers]: The following browsers were detected on your system: [ 'Chrome', 'Chromium' ]
26 03 2018 10:25:34.874:WARN [framework.detect-browsers]: No launcher found for browser Chrome, it will not be used.
26 03 2018 10:25:34.874:WARN [framework.detect-browsers]: No launcher found for browser Chromium, it will not be used.
26 03 2018 10:25:34.874:INFO [framework.detect-browsers]: The following browsers will be used: []
We can replicate this on all machines across versions 1 of karma-detect-browsers, all the way up to the latest 2.3.1.
All the machines may use potentially slightly different versions of node and npm, but our CI server where this was first detected uses node version 8.4.0 and npm version 5.3.0.
Not sure if anyone else has had this problem or can offer some advice?
We have had the same issue today. The issue is with a minor version of karma-detect-browsers. Try locking the version to 2.2.6 and reinstall, then test again.
This fixed the problem for us. We'll report it back to the package maintainer.
Related
So I was using ChromeDriver 2.40 which worked great with OpenFin 10.66.41.18 or Chromium 66.0.3359.181 if you prefer.
However after upgrading to latest OpenFin stable version (11.69.42.29), I started getting an error denoting version mismatch between ChromeDriver and Chromium:
Chrome version must be >= 66.0.3359.181
Fair enough, I thought and downloaded Chromedriver 2.44 which is the closest I can get to v69, still getting an error:
Chrome version must be >= 69.0.3497.0
So, close but no cigar as OpenFin now runs on Chromium 69.0.3497.128
But that means we reached a dead end completely losing the ability to automate OpenFin as if you get the next available ChromeDriver (so 2.45) you get an error that chrome:
Chrome version must be between 70 and 73
In other words, latest stable version of OpenFin is not supported with a matching ChromeDriver. Just raising this in case anyone else is experiencing the same issue.
As a workaround I reverted back to 10.66.41.18 as I'm using a config file to launch my app.
So, I've changed from:
"runtime": {
"version": "stable"
}
to this one:
"runtime": {
"version": "10.66.41.18"
}
I am not sure why I am getting this error when I run the following method:
import wptools
wptools.page('E.T._the_Extra-Terrestrial').get()
*TypeError: the JSON object must be str, not 'bytes'*
I have confirmed that this command works on other computers so I'm not sure if there is a bug within the library or if I'm just missing something.
I am running windows 10.
'3.5.2 |Anaconda 4.1.1 (64-bit)| (default, Jul 5 2016, 11:41:13) [MSC v.1900 64 bit (AMD64)]'
I confirmed there was a bug. Developer has updated it. See github issue for reference.
https://github.com/siznax/wptools/issues/95
DraftSight 2017SP1 Linux (beta) worked on Fedora 24. It fails after upgrading to Fedora 26. Running it from the command line so you can see the low-level errors,
/opt/dassault-systemes/DraftSight/Linux/DraftSight
Qt: Session management error: None of the authentication protocols specified are supported
Could not parse stylesheet of object 0x238a050
Could not parse stylesheet of object 0x238a050
In the graphics environment you see the usual start screens, then error pop-ups which offer to report the error and then close the application when clicked. One says that error-reporting is not available.
Similarly with 2017SP3 and 2018SP0. Fedora updates are current as of today.
This system is an Intel core i3. lspci reports "Intel Corp Xeon E3-1200 v3/4th Gen core processor Integrated Graphics Controller (rev 06)"
2018SP0 does work once an Nvidia GT710 card and the nvidia driver module are installed. It does not work with the nouveau driver module and the same card.
Does anybody have any insight as to the cause? A regression in Fedora, or a latent bug in DraftSight, or anything else?
Knowing whether it works with Fedora 26 and AMD graphics might be very helpful.
Edit March 2018
Doesn't work but differently on a system with AMD R5 230. No "Could not parse" errors, not anything else on the terminal window, but Draftsight starts up with the display all wrong and then locks up. Clicking the "X" gets to "the program is not responding".
Also worth noting that this isn't a Wayland issue. Systems are running Cinnamon and lightdm, so it's good old X.
Also a work-around, if performance is unimportant. (And it probably isn't, with Gen 4 Intel Graphics). Run it as a "remote" application on localhost, on a system with Intel graphics.
$ ssh -X 127.0.0.1
password:
Last login: Wed Mar ...
-bash-4.4$ /opt/dassault-systemes/DraftSight/Linux/DraftSight
(success)
Further update Fedora 29, DraftSight 2018SP3
New wrinkles for Nvidia, Cinnamon as above
Needs invocation
LD_PRELOAD=/usr/lib64/libfreetype.so.6 /opt/dassault-systemes/DraftSight/Linux/DraftSight
otherwise fails with /lib64/libfontconfig.so.1 lookup error FT_DOne_MM_Var
Also kernel 4.20 plus NVidia 390.87 fails to build. There's a patched NVidia installer that does work at if_not_false_then_true site.
Also does not install a .desktop file into /usr/share/applications
I had similar problems when I updated Fedora 24 to 25. The parse stylesheet messages still show up but I can run draftsight from an Xorg session, (not Wayland), using the nouveau drivers but only under root privileges using sudo .
You might try the following script:
sudo DISPLAY=$DISPLAY vblank_mode=1 /opt/dassault-systemes/DraftSight/Linux/DraftSight
I can only get DraftSight to run as root under Fedora 27, 4.18.16-100.fc27.x86_64. I have installed a VM with Ubuntu, and it runs fine, without elevated privileges.
I am using Linux (Ubuntu 12.04) with 64-bit java 7 and Eclipse (Indigo).
On the game project we are using slick2d and along with it lwjgl. I was halted by the following errors.
(fixes explained in the answer)
java.lang.UnsatisfiedLinkError: no lwjgl in java.library.path
java.lang.UnsatisfiedLinkError: no jinput-linux64 in java.library.path
Failed to open device (/dev/input/event8): Failed to open device /dev/input/event8
Versions:
Slick2D
Mon, 01 Oct 2012 09:54:11 +0100
Sun May 11 20:17:03 BST 2008
build=264
LWJGL (could be 2.8.5 already, but now this):
2.8.4
To fix this, follow the instructions provided in the 'slick2d' documentation
http://www.slick2d.org/wiki/index.php/Main_Page
This seems to be a real bug with slick2D/lwjgl on the versions that we are currently using. To fix this you can't use 64-bit java (with linux at least). Download the 32-bit java from Oracle web site and configure this to be your IDEs runtime environment (you may need to search for more help how to do this in your particular IDE)
This is purely related to permissions on linux. Go to '/dev/input' and change the folder permission 'sudo chmod 644 *' so that the process can simply read what's in there.
There didn't seem to be info on how to fix this problem whole together. Hope this helps some one else.
Download slick and copy needed libs (jinput-linux64, lwjgl, .dll & .so files) to your java.library.path
to get the java.library.path you can do so: System.out.println(System.getProperty("java.library.path"));
I get a weird exception while using CORBA ACE/TAO. I am trying to run a service written in Java that sends/receives messages from clients.
When I run the same code in Windows 7 32-bit it works fine! I exported an executable jar file and tried to run it on my mac, but the problem was still there.
The exception I get is the following:
Dec 7, 2011 6:43:52 AM com.sun.corba.se.impl.naming.namingutil.CorbalocURL badAddress
WARNING: "IOP00110603: (BAD_PARAM) Bad host address in -ORBInitDef"
org.omg.CORBA.BAD_PARAM: vmcid: SUN minor code: 603 completed: No
at com.sun.corba.se.impl.logging.NamingSystemException.insBadAddress(NamingSystemException.java:148)
at com.sun.corba.se.impl.logging.NamingSystemException.insBadAddress(NamingSystemException.java:166)
at com.sun.corba.se.impl.naming.namingutil.CorbalocURL.badAddress(CorbalocURL.java:104)
at com.sun.corba.se.impl.naming.namingutil.CorbalocURL.handleColon(CorbalocURL.java:140)
at com.sun.corba.se.impl.naming.namingutil.CorbalocURL.handleIIOPColon(CorbalocURL.java:115)
at com.sun.corba.se.impl.naming.namingutil.CorbalocURL.<init>(CorbalocURL.java:67)
at com.sun.corba.se.impl.naming.namingutil.INSURLHandler.parseURL(INSURLHandler.java:41)
at com.sun.corba.se.impl.resolver.INSURLOperationImpl.operate(INSURLOperationImpl.java:114)
at com.sun.corba.se.impl.resolver.ORBInitRefResolverImpl.resolve(ORBInitRefResolverImpl.java:31)
at com.sun.corba.se.impl.resolver.CompositeResolverImpl.resolve(CompositeResolverImpl.java:20)
at com.sun.corba.se.impl.resolver.CompositeResolverImpl.resolve(CompositeResolverImpl.java:22)
at com.sun.corba.se.impl.orb.ORBImpl.resolve_initial_references(ORBImpl.java:1151)
at ami.ImplRepoClient.<init>(ImplRepoClient.java:23)
at ami.Famine.initialize(Famine.java:22)
at ami.Famine.initialize(Famine.java:12)
at test.Test.main(Test.java:45)
Exception in thread "main" org.omg.CORBA.BAD_PARAM: vmcid: SUN minor code: 603 completed: No
at com.sun.corba.se.impl.logging.NamingSystemException.insBadAddress(NamingSystemException.java:148)
at com.sun.corba.se.impl.logging.NamingSystemException.insBadAddress(NamingSystemException.java:166)
at com.sun.corba.se.impl.naming.namingutil.CorbalocURL.badAddress(CorbalocURL.java:104)
at com.sun.corba.se.impl.naming.namingutil.CorbalocURL.handleColon(CorbalocURL.java:140)
at com.sun.corba.se.impl.naming.namingutil.CorbalocURL.handleIIOPColon(CorbalocURL.java:115)
at com.sun.corba.se.impl.naming.namingutil.CorbalocURL.<init>(CorbalocURL.java:67)
at com.sun.corba.se.impl.naming.namingutil.INSURLHandler.parseURL(INSURLHandler.java:41)
at com.sun.corba.se.impl.resolver.INSURLOperationImpl.operate(INSURLOperationImpl.java:114)
at com.sun.corba.se.impl.resolver.ORBInitRefResolverImpl.resolve(ORBInitRefResolverImpl.java:31)
at com.sun.corba.se.impl.resolver.CompositeResolverImpl.resolve(CompositeResolverImpl.java:20)
at com.sun.corba.se.impl.resolver.CompositeResolverImpl.resolve(CompositeResolverImpl.java:22)
at com.sun.corba.se.impl.orb.ORBImpl.resolve_initial_references(ORBImpl.java:1151)
at ami.ImplRepoClient.<init>(ImplRepoClient.java:23)
at ami.Famine.initialize(Famine.java:22)
at ami.Famine.initialize(Famine.java:12)
at test.Test.main(Test.java:45)
In both cases I use java 1.6. The java version in my mac is "build 1.6.0_29-b11-402-10M3527"
Does anybody have any idea of what the problem could be??
Thanks,
Dimos.
Probably your Mac can't resolve the address you pass with -ORBInitDef. Try to ping the server manually and see if that works.