I found here that neo4j has a new spatial type point , i downloaded 4.1 and 3.3.5 community versions (which are the latest versions) and they both return this error
Neo.ClientError.Request.Invalid: Point is not yet supported as a return type in Bolt
in which version i can use point() ?
It's available from the 3.4 series so you don't have to use the alpha pre-release version if you don't want to.
I tried the alpha pre-release 3.5.0 version and it works
Related
This CoralUI documentation page has a migration guide from earlier versions of CoralUI.
How do I learn which Adobe Experience Manager (AEM) CoralUI version I am using?
I think I can see it by going into CRXDE package manager and using the browser search (not the Search packages field) for coral:
I am learning to use opencv. I am trying to install it from opencv official website. Is it okay to install the latest version(4.0.0)? I suppose that latest version should be compatible with the earlier versions so there shouldn't be any problem.
Is it okay to install the latest version(4.0.0)
Generally: Yes, why not? If you want to use the newest modules (like gapi, added in 4.0.0) you will need to use the newest version. It also makes a lot of sense to use the newest because they improved the performance for some operations compared to version 3.x.x.
I suppose that latest version should be compatible with the earlier versions so there shouldn't be any problem
Not necessarily. Version 4 to 3 might be compatible (I'm still using 3.x.x), but 3 to 2 are in fact not completely compatible. Most noticeable they moved a lot of functionality from the highgui package. From the official change log:
Although OpenCV 3 can be viewed as refined OpenCV 2 and is similar to the latter, this new version is not completely backward-compatible with OpenCV 2
I'd recommend you to read the official changelog for yourself and decide if you need the new functionality or if you want to stay with an older version. If you are new to OpenCV it probably makes sense to start with the newest version.
I used a Older Corona SDK but i installed recent version 3.0.0 . When is tried to use stateText:setReferencePoint(display.CenterReferencePoint); it shows following runtime error! in newer version Corona SDK. What's the problem? can anyone suggest me any solution? Image of my Error
First, Corona SDK version numbers are something like the year and a four digit build number. The current public build for instance is 2014.2189, so I don't' know what 3.0.0 is. But that said,
:setReferencePoint() was an API in our older Graphics 1.0 based engines (build numbers less than 2000). They have been replaced by Anchor Points in Graphics 2.0 based builds (build numbers 2000 and greater).
You have two choices. If you want to continue to use :setReferencePoint() you must add this to your config.lua where you set the width and height:
graphicsCompatibility = 1,
Or you can switch to using AnchorPoints. See the tutorial: http://coronalabs.com/blog/2013/10/15/tutorial-anchor-points-in-graphics-2-0/
I would like to know if anyone is using Neo4J 1.8.x Embedded with Sun JDK 7? IF so, have you hit any issues and what are they?
Let me also clarify, I'm not looking to build the Neo4J source code - only run Neo4j 1.8.1 Embedded on Sun Java 7.
I know that Neo4j 1.9 is the first version that will support Java 7, but if Neo 1.8.1 runs on Sun JDK 7 without any problems, we will be considering deploying with that.
There are a number of benefits (i.e. security, etc.) to going with Java 7, but if there are compatibility issues with Neo 1.8.1, we'd like to find out.
Thanks,
Bob
Java 7 has changed the built in sorting algorithm. The new sorting algorithm (TimSort) is more sensitive to concurrent modification. Where the sorting algorithm in Java 6 and earlier would just produce a result that wasn't perfectly sorted in the face of concurrent modification, TimSort will throw an exception.
Neo4j uses these sort() methods in its page cache.
These exceptions means that Neo4j will crash unexpectedly when running with multiple threads on Java 7.
The Neo Technology team are addressing this issue for Neo4j 1.9.
I'm working with WSF here: http://wso2.org/project/wsf/ruby/1.1.0/docs/manual.html
The documentation cites 1.8.5 or above, but I'm running into issues with 1.9.3p0. Can anyone confirm that this framework is incompatible with ruby 1.9.3?
The WSF/Ruby framework can most probably be incompatible with 1.9.3p0. That statement of version 1.8.5 or higher is based on the assumption that WSF/Ruby will remain backward compatible. Since there is no active development on the project, any issues with later Ruby versions may not be fixed.