The Kaa IoT website shows that the current available sandbox has Kaa version 0.10.0. Since there are some bugs (https://jira.kaaproject.org/browse/KAA-1087) which have been fixed in the subsequent versions of Kaa, I wanted to know if the next versions i.e. 0.10.1 or 0.11.0 are available for the Sandbox.
Nope, these two versions (0.10.1 or 0.11.0) aren't officially released. Instead you can compile source code which milestone is 0.11.0 and install kaa in a single linux node envirorment.
Related
Has anyone installed the latest concierge with the RedWeb SDK?
Since installing I can no longer save and have the program automatically compile the code. It will compile and then loops. Normally you save your file and it automatically compiles and responds with the ready and the localhost, etc... I have to kill the terminal session in VSC and restart a terminal session and do ngv run and it will work.
Note: This is the Concierge version released this week. We are developing specifically for RedWeb and not the desktop version which has a different SDK. Just curious if anyone is experience this with SabreRedWeb-SDK-21.5.5
I had issues with that version also. Sabre has just finalized version 21.6 SDK and it should be on the website soon. The newer version worked fine with all my testing so far.
I have downloaded the wso2 open source of master branch from github, but the build is failing. Can anyone guide me in the right direction? How do I get the publisher and store of wso2 api mananager up?
Make sure you install nodejs and java8(or higher) to your computer. you can try with any version after checking out to the particular tag or if you want the latest release pack, go with the master branch. First build the carbon repo(https://github.com/wso2/carbon-apimgt) and after you build the carbon repo then take the version(it's in main pom file()) of that and update carbon version(<carbon.apimgt.version>) of the product-apim(https://github.com/wso2/product-apim/) main pom file(it's already included a carbon version, replace it to your version). Then build the product-apim.
The master branch is the ongoing development branch. Hence could you please refer this link [1] to get start the WSO2 APIM. This will guide you on how to start publisher and developer portals.
[1]. https://apim.docs.wso2.com/en/latest/getting-started/quick-start-guide
What is the maven version you have in your windows machine? When working with windows it is highly suggested to use compatible versions rather than the latest versions.
I have issues to run Spring-Kafka version 1.3.9 with Kafka client 0.10.2.2
The https://spring.io/projects/spring-kafka says that "All users with brokers >= 0.10.x.x (and all spring boot 1.5.x users) are recommended to use spring-kafka version 1.3.x or higher" I have setup in my pom.xml the Spring-Kafka version 1.3.9 and overriding the Kafka client from 0.11.x.x to 0.10.2.2
When I run the instance I have this error:
Caused by: java.lang.NoClassDefFoundError:
org/apache/kafka/common/header/Headers
at org.springframework.kafka.core.KafkaTemplate.(KafkaTemplate.java:74)
~[spring-kafka-1.3.9.RELEASE.jar:?]
The 0.11.x.x contains the package header. However, the version 0.10.2.2 doesn't.
The brokers with version 0.10.x.x aren't compatible with spring-kafka version 1.3.9. And this is the opposite with what the spring-kafka website says. Please, correct me if I'm wrong.
My question is any problem to use the 0.11.xx version instead of 0.10.x.x right? I couldn't see the release notes between the two versions. Btw, my Kafka instance is running on 0.10.x.x version. Thanks
Please don't ask the same question in multiple places; it's a waste of our time (and yours).
As I said in the GitHub issue...
You should not downgrade the kafka-clients. The 0.11 clients can communicate with the 0.10.x.x broker.
See the Confluent compatibility matrix.
I think the table on the project page is quite clear; it states that spring-kafka 1.3.x is compatible with the 0.11.x.x and 1.0.x.x clients.
For a complete discussion about client/broker compatibility, see the Kafka Compatibility Matrix.
Let me know if we can make it clearer.
Note that while the 0.11 client will work with the 0.10 broker, you obviously can't use 0.11 broker features (such as headers).
0.10.x.x is very old. The current version is 2.2.1 (and 2.3.0 will be out soon). There have been lots of improvements over the years.
The doc of the latest version of mPDF on github suggest the only way to install it is by using composer. But how to do on a shared host without SSH access?
Is there an other way to install it? Or will it be? Or should I just continue to use the older version still available for download (but it looks no longer supported and no longer compatible with the latest version of PHP)?
The documentation on the main mPDF Github page is for development version. There still are ready-to-use packages for version 6.1.0 which can be uploaded and used as-is.
However, I would recommend installing mPDF via composer locally and then transfer the whole local installation to your server via FTP or whatever you use.
As the composer is de-facto standard for package management now, future versions of mPDF will not provide those pre-prepared packages anymore.
Do we have any cli/api to check openstack development version..i mean whether my system installed havana or grizzly.I searched the openstack cli/api docs but i don't find any relevant.
OpenStack has a number of elements if you want to verify state.
Each of the component projects and each of the python-client api bindings have their own versions. Then there are configurable options for addressing API versions in REST queries.
I took a crack at building an API for the very purpose of verifying this data as well as all python dependencies a while back with the aim of cross verifying that against a vulnerability database but I simply haven't had the time to bring it to completion.
This would be a very useful feature I think.
You might look at your pip requires if you installed from source. Alternatively you can follow the debian package version chain from dependencies and that should provide good insight into what is installed on your system though it's not exactly verified.