While deploying confluent-replicator with 5.1.2 version its throwing below error :
org.apache.kafka.common.config.ConfigException: Invalid value io.confluent.connect.replicator.util.ByteArrayConverter for configuration key.converter: Class io.confluent.connect.replicator.util.ByteArrayConverter could not be found.
Using confluent version 5.1.2 and replicator image as: docker pull confluentinc/cp-enterprise-replicator:5.1.2
Same works fine if i use docker pull confluentinc/cp-enterprise-replicator:3.3.1
I tried 3.3.1 version it works but it doesn't work with 5.1.2 and 5.2.1
docker pull confluentinc/cp-enterprise-replicator
Ideally plugin for Bytarrayconverter should get added with 5.1.2 version but its not getting added
Related
I have a django model where I have a OneToOneField to djstripe's Customer. When I run makemigrations a migration is created with the following dependency:
dependencies = [ ('djstripe', '0011_alter_invoice_charge_alter_invoice_customer_and_more'), ('users', '0007_rename_username), ]
Everything seems to be okay locally, but then when I deploy my code it fails with the following error:
django.db.migrations.exceptions.NodeNotFoundError: Migration users.0008_stripecustomer dependencies reference nonexistent parent node ('djstripe', '0011_alter_invoice_charge_alter_invoice_customer_and_more')
Our pipeline does not run makemigrations, only migrate, so this seems a little weird that a djstripe migration is created when I run makemigrations locally but then I cannot use it in deployment. Plus, such migration does not exist in djstripe GitHub repository.
dj-stripe version: 2.6.1
Python version: 3.9
Django version: 4.0.1
Stripe API version: 2.68.0
Database type and version: postgres 12.9
It's an known bug in v. 4 - https://github.com/dj-stripe/dj-stripe/issues/1649#issuecomment-1117774629
To solve it you'd have to downgrade django to 3.x.x. They should fix it in the next update as well.
Running into this module error no one on my team, which is all new, does not know. Below is my terraform version. And yes, I know terraform 0.11 is old as hell but I was just hired and have to fix this.
$ terraform --version
Terraform v0.11.14
provider.aws v2.70.0
provider.grafana v1.10.0
provider.kubernetes v1.8.0
provider.null v2.1.2
provider.postgresql v1.7.2
provider.random v2.3.1
Error:
Error: Error asking for user input: 1 error occurred:
* module.editedout-dev-keycloak.provider.grafana: Incompatible API version with plugin. Plugin version: 5, Core version: 4
As described in the documented requirements for the Grafana provider version 1.10, the minimum core version of Terraform for that version of the provider is 0.12. The reason for this can be seen referenced in the CHANGELOG with issue 159. The provider upgraded to version 2 of the provider SDK, which enforces core Terraform at minimum version 0.12. More details around that minimum version bump can be read in that issue description.
If you want to move forward, then you would need to lock in the Grafana provider to version 1.9.0. In Terraform version 0.11, you would achieve that with the following declarative syntax in a config file for the root module config, or preferably in the module declared as editedout-dev-keycloak in the error message you displayed:
provider "grafana" {
version = "1.9.0"
}
enter image description here
I used dbeaver to connect to Trino of Phoenix, and there was such an error
Could not load/instantiate class org.apache.phoenix.query.DefaultGuidePostsCacheFactory
this my configuration
hbase version 2.3.4
phoenix version 5.1
trino version 353
phoenix5 jar phoenix-client-embedded-hbase-2.3-5.1.0.jar
I recently upgraded my Sonar Version to 5.5 and all the compatible plugins with it.
Here are the versions of the plugins installed:-
sonar-ldap-plugin-1.5.1.jar
sonar-javascript-plugin-2.13.jar
sonar-java-plugin-3.14.jar
sonar-build-breaker-plugin-2.1.jar
sonar-php-plugin-2.8.jar
sonar-findbugs-plugin-3.3.jar
If I use sonar-findbugs-plugin-3.3.jar, the Sonar is not getting Up and throwing below error :-
java.lang.IllegalArgumentException: The rule 'EC_INCOMPATIBLE_ARRAY_COMPARE' of repository 'findbugs' is declared several times
If I downgrade the Jar to sonar-findbugs-plugin-3.2.jar it works but fails to analyse the Project and throws below error :-
An API incompatibility was encountered while executing org.sonarsource.scanner.maven:sonar-maven-plugin:3.0.2:sonar
I have tried the versions - 3.3,3.3.1 and 3.3.2
Any Help ?
I'm working no setting up Hygieia dashboard.
Hygieia: https://github.com/gigaaks/Hygieia
Trying both approaches of setting it up locally or using Docker based installation/setup.
I'm successfully able to get mongoDB, it's API, UI modules up and running. Hygieia main login screen comes up fine. I successfully created the login user and able to log in.
At this point, I have mongoDB running, API, UI pieces running and it's time to create a CAP One / Split Dashboard (templates provided by Hygieia). When I provide the values for creating a new dashboard, it's throwing the following error in the API logs on the server (vagrant/VirtualBox instance) OR within the Docker's container.
What I found was there are lots of issues in this project's module where things are not correct i.e. database name in one module is dashboard, in other module it's dashboardb and in other, it's expecting dashboarddb. I fixed those issues in my github repo/project and initiated a pull request which is approved and will be merged. The following error though, tells my that Hygieia's UI piece is NOT sending a parameter what the API piece is expecting while trying to create a dashboard (in mongoDB). The parameter is "type" and as UI (Hygieia GUI) is not sending it (as per their latest code in GitHUB), the API is failing throwing an error saying that type variable value is passed as NULL. I found the same when I tried POST operation by sending the same JSON RestAPI query using Postman.
Due to this, I'm currently not able to create a dashboard and start using the collectors provided by Hygieia out of the box (for Stash, GitHub, Jenkins, SonarQube etc).
Has anyone of you have faced or found a workaround for this error/issue?
2016-04-01 02:40:40,357 WARN c.c.d.rest.RestApiExceptionHandler - Bad Request - bind exception:
org.springframework.validation.BindException: org.springframework.validation.BeanPropertyBindingResult: 1 errors
Field error in object 'dashboardRequest' on field 'type': rejected value [null]; codes dashboardRequest.type,NotNull.type,NotNull.java.lang.String,NotNull]; arguments [org.springframework.context.support.DefaultMessageSourceResolvable: codes [dashboardRequest.type,type]; arguments []; default message [type]]; default message [may not be null]
at com.capitalone.dashboard.rest.RestApiExceptionHandler.handleMethodArgumentNotValid(RestApiExceptionHandler.java:55) [api.jar!/:2.0.0-SNAPSHOT]
at org.springframework.web.servlet.mvc.method.annotation.ResponseEntityExceptionHandler.handleException(ResponseEntityExceptionHandler.java:156) [spring-webmvc-4.1.7.RELEASE.jar!/:4.1.7.RELEASE]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_72-internal]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_72-internal]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_72-internal]
at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_72-internal]
at org.springframework.web.method.support.InvocableHandlerMethod.doInvoke(InvocableHandlerMethod.java:221) [spring-web-4.1.7.RELEASE.jar!/:4.1.7.RELEASE]
at org.springframework.web.method.support.InvocableHandlerMethod.invokeForRequest(InvocableHandlerMethod.java:137) [spring-web-4.1.7.RELEASE.jar!/:4.1.7.RELEASE]
at org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:110) [spring-webmvc-4.1.7.RELEASE.jar!/:4.1.7.RELEASE]
The issue was coming due to that fact that I used Hygieia modules docker images built locally using Maven (mvn clean install ; mvn docker:build) but for the UI module, as I was getting an error message, I cherry picked that image from captial one/hygieia-ui image. For some reason, it didn't work and was showing the above error (as there could be API level changes).
I had to run the following to get Hygieia dashboard up and running in local machine:
git config --global --unset-all url.https
git config --global url."https://".insteadOf git://
npm config set prefix /usr/local
sudo npm install --color=false; sudo npm install -g bower gulp; sudo npm install bower install
mvn clean install; mvn docker:build
gulp serve
Now, everything is working as expected for creating dashboard (PS: You have to create mongo db database first using mongo command line as shows in Hygieia's documentation).
npm -g option will install bower and gulp globally. without -g, it'll also install the same locally. Global values actually refer the local values.
For docker based solution, I just used docker-comopose file and got it up and running.
NodeJS(node) version: v5.10.0
NPM (Node pkg mgr) : 3.8.3
Bower version : 1.7.9
Gulp version : [08:18:42] CLI version 3.9.1,[08:18:42] Local version 3.9.1,
Maven version : Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T16:41:47+00:00)
java version "1.8.0_77"
Java(TM) SE Runtime Environment (build 1.8.0_77-b03)
Java HotSpot(TM) 64-Bit Server VM (build 25.77-b03, mixed mode)
Java version :