On the PostgreSQL (9.3.0) + postGIS (2.1.0) side, I'm receiving the following WARNING log:
CONTEXT: SQL function "st_force_2d" during startup
WARNING: ST_Force_2d signature was deprecated in 2.1.0. Please use ST_Force2D
I found that the reason is the mapserver (6.2.1) layer used in the mapfile quering postgis data.
Do you know if in mapserver 6.4.0 (just released a week ago) the issue is resolved?
It was not addressed in 6.4.0. Opening an issue on the MapServer issue tracker would be a good start to get this added into a future release.
Related
I have Symfony 5 project and just following the instructions to install the DoctrineMongoDBBundle package, and I'm receiving te following error,
Attempted to load interface "CommandSubscriber" from namespace "MongoDB\Driver\Monitoring".
Did you forget a "use" statement for another namespace?
/vendor/doctrine/mongodb-odm/lib/Doctrine/ODM/MongoDB/APM/CommandLoggerInterface.php (line 9)
I have the following versions of mongodb and doctrine running.
doctrine/mongodb-odm-bundle": 4.1
mongodb/mongodb": 1.6
Also the php driver installed through Pecl (Version 1.7.4)
Anyone got any ideas to what I'm missing?
If it helps anyone in the future, whilst the MongoDB Driver was installed, I needed to restart PHP FPM, that fixed it.
Attempting to install Specio::Constraint::Simple, running into the following error:
Can't resolve method "???" overloading "&{}" in package
"Specio::Constraint::Simple" at Specio::Constraint::Simple->new line
35.
Only related article I have found has been: https://rt.cpan.org/Public/Bug/Display.html?id=117975
Any suggestions would be appreciated.
Thank you
This is caused by a bug in older versions of Role::Tiny that was fixed in version 1.003003:
overloads specified as method names rather than subrefs are now applied
properly
Upgrading Role::Tiny should fix it and allow Specio::Constraint::Simple to be installed normally.
Actually, you don't even need to do that manually: Version 0.26 of Specio now requires at least version 1.003003 of Role::Tiny. Any future attempt to install Specio will upgrade Role::Tiny automatically (if required).
I am trying to upgrade to Jira 7 from version 6. I used the rapid upgrade method. It installs fine but I get an error on the browser “There is a problem with your Jira Access”. I went through the logs and I see that 6 plugins are failed to load during the Jira startup. Somehow they are disabled. I replaced couple of these .jar files with latest .jar and re-started the service, but I get the same error.
I also ran this query update pluginstate set pluginenabled='true' in the db but no luck.
Here is the log:
net.customware.plugins.connector.salesforce.salesforce-connector-plugin' - 'ServiceRocket Salesforce.com Connector Plugin - Plugin' failed to load.
Cannot start plugin: net.customware.plugins.connector.salesforce.salesforce-connector-plugin
Unresolved constraint in bundle net.customware.plugins.connector.salesforce.salesforce-connector-plugin [206]: Unable to resolve 206.0: missing requirement [206.0] osgi.wiring.bundle; (osgi.wiring.bundle=net.customware.plugins.connector.atlassian.jira-connector-plugin) [caused by: Unable to resolve 204.0: missing requirement [204.0] osgi.wiring.package; (osgi.wiring.package=javax.xml.rpc)]
It was loaded from C:\JIRA_data\plugins\installed-plugins\salesforce-connector-plugin-6.0.8.jar.
We had the same problem last week, upgrading from 6.4.13 to 7.1.6. There are some incompatible plugins that crash Jira 7 when started, despite an apparently successful upgrade. Please refer to this page for details on the target plugins, as well as a way to solve the problem:
https://confluence.atlassian.com/jirakb/upgrading-to-jira-7-throws-a-nosuchmethoderror-on-com-atlassian-crowd-embedded-api-user-781396615.html
I'm running Eclipse with RoboVM plugin and I wanted to try IOSDemo sample project described on robovm.org (http://www.robovm.org/docs.html). When creating the project in Eclipse and running it I got following error message.
An internal error occurred during: "Launching IOSDemo".
java.lang.IllegalAccessError: tried to access method java.lang.Object.clone()Ljava/lang/Object; from class soot.toolkits.scalar.LocalSplitter
I found out that it's related to JDK version (I'm running JDK 8.0 ea, build 112). When running on JDK 1.7.0_45 and building the project on cmd line it builds and runs OK.
Is it known problem, is there any workaround or fix? Thanks
This is most probably due to a bug [1] in the recent early access builds of Java8. It looks like the bug was resolved a few days ago but as far as I can see the fix didn't make it into the b113 build. Please use the latest Java7 release or an earlier Java8 EA build until a Java8 build is available with this fix included.
[1] https://bugs.openjdk.java.net/browse/JDK-8026394
This question is in continuation of this post, I have tried installing Xerces-C but the thing is Xerces-C version is 2.8.0 and 3.0.0 and XML::XERCES latest version is 2.7.0 and so am getting following error message:
Update2: Here is the error which am getting, it says there is somekind of version mismatch.
Using XERCES_LIB = /home/adoshi/XML-Parser/Parser2/
xerces-c_2_8_0-hppa-hpux-acc_3(1)/xerces-c_2_8_0-hppa-hpux-acc_3/lib
Using XERCES_INCLUDE = /home/adoshi/XML-Parser/Parser2/
xerces-c_2_8_0-hppa-hpux-acc_3(1)/xerces-c_2_8_0-hppa-hpux-acc_3/include
WARNING
You have defined the XERCESCROOT variable, but the file:
XERCESCROOT/src/xercesc/config.status
does not seem to point to the config.status file that was used to
build your Xerces-C library. Without that file, I may not be able to
properly build the C++ glue files that come with Xerces.pm.
Proceeding anyway ...
Using Xerces-C version info from /home/adoshi/XML-Parser/Parser2/xerces
-c_2_8_0-hppa-hpux-acc_3(1)/xerces-c_2_8_0-hppa-hpux-acc_3/include/xercesc/util
/XercesVersion.hpp
*** Version Mismatch ***
You are attempt to build XML::Xerces-2.7.0-0 using Xerces-C-2.8.0,
this will most likely fail, so I am aborting.
You must use Xerces-C-2.7.0
Any guidance would be highly appreciated.
Did you read the download page that clearly says "Older releases are available from the archive download site."? Perhaps you can find a 2.7.0 release there.