common-utils | 通用工具类。

Turns out there was a misunderstanding. I thought the Test class was making a network call to the localhost Tomcat instance, when in fact it called the source code directly.

That's why when I was launching the Tomcat Run Configuration in Debug mode I would get a registered breakpoint in my source code, but it would never suspend the application, despite me seeing the logs.

And since the application was configured to output logs in a file in target, I thought the logs were coming from Tomcat.

Stepping in from the Test class launched in Debug mode brought me to the application code, and eventually also reached the library code. That is also why I was seeing logs coming from the library, but without seeing the registered breakpoint when I was running the Test class normally after launching the Tomcat Run Configuration in Debug mode.

Ugh. That was an embarrassing and time-consuming journey.

This issue was only occurring in github actions pipeline. It's solved by setting persist-credentials to false otherwise it uses github actions token which does not have the necessary permissions to pull/install the repository. .

Try this solution (uses named capture groups in regex):

Your setup.py lists a lot of top-level packages:

By fixing below things, the issue got resolved -

1.Changed permissions of /usr/share/java/kafka-connect-jdbc/mysql-connector-java-8.0.13.jar to 755 2.Keep only /usr/share/java in plugin path.

3.Change my sql table structure to have one primary key and one column property with incremental nature or timestamp.

The problem here is that the ibmcom/swift-ubuntu:5.0.2 image is built on top of Ubuntu 14.04. The version of libmysqlclient-dev supplied with 14.04 does not include the pkg-config information that allows the Swift compiler to find the headers without help.

There are two solutions to this problem:

1: You could add -Xcc -I/usr/include/mysql/ arguments to the swift build command. Either:

• replace the command you are executing in the build container with swift build -Xcc -I/usr/include/mysql/, or
• if you'd like to keep using the tools-utils.sh script, you can create a file in your project called .swift-build-linux which contains a single line: swift build -Xcc -I/usr/include/mysql/ - this will be picked up by the tools-utils.sh script when it runs the build.

2: You can replace your base images with FROM swift:5.0.2 (for the build image) and FROM swift:5.0.2-slim (for the run image) - these are the official Swift-maintained images which are based on Ubuntu 18.04, and as of the Swift 5.0.2 release, provide a 'slim' image similar to ibmcom's 'runtime' image.

• Note that these images do not bundle the libssl-dev or libcurl4-openssl-dev dependencies, so you will need to include those in your Dockerfile-tools.

This is a classpath issue. Looks like maybe you have an incompatible version of guava in the classpath? If your plugin path isn't including this method in any of the jars it has, that's a connector packaging issue. If it is, then you probably have two versions hanging around. Double check that plugin path with a find command to inspect all jars for that class in the message as a first step. Ultimately, you'll need to figure out what version of the dependency the connector expects and get that version and only that version into the plugin path.

The MySQL driver does not ship with the Kafka Connect JDBC connector. You have to install it yourself and in the correct location.

You need to put the relevant MySQL JDBC Driver JAR in the Kafka Connect JDBC folder before you start the Kafka Connect worker

This post will help you out with more detail.