Upgrade dinky1.2.0-rc-4 version, the previous version's task Flink cannot be triggered or stopped with savepoint

[wangyayuan18]

Search before asking

• I had searched in the issues and found no similar issues.

What happened

Upgrade dinky1.2.0-rc-4 version, the previous version's task Flink cannot be triggered or stopped with savepoint

What you expected to happen

My expectation is to upgrade to Dinky1.2.0 version normally, which can save points to stop the previous version's Flink task

How to reproduce

The Flink task in the previous Dinky version did not stop. Instead, the jar packages in the latest version Dinky1.2.0-rc4 lib directory and the dinky-app-1.2.0 jar directory were directly moved to the relative directory of the previous Dinky version. The Flinkcdc version in the extends directory was updated to 3.2.1, compared to the previous version 3.1.1. The Flink/lib/previous version Dinkyapp package on HDFS was updated to the latest Dinkyapp 1.2.0. Then, the Dinky service was restarted to verify that the savepoint job triggered and stopped, and the page displayed successful triggering and stopping, but the task still ran

1.Errors reported in the log after savepoint triggers and stops
[dinky] 2024-12-06 11:25:21 CST ERROR org.dinky.aop.exception.UnKnownExceptionHandler 39 unknownException - java.lang.StringIndexOutOfBoundsException: String index out of range: 0 java.lang.RuntimeException: java.lang.StringIndexOutOfBoundsException: String index out of range: 0
2.Try disabling the REST API in the system configuration ， Errors reported in the log
[dinky] 2024-12-06 11:27:38 CST ERROR org.dinky.aop.exception.UnKnownExceptionHandler 39 unknownException - java.lang.NullPointerException: Value must not be null. java.lang.RuntimeException: java.lang.NullPointerException: Value must not be null.

Anything else

The two jar packages in the extensions/Flink/Dinky directory of dinkyk1.2.0-rc4 version have also been placed in the lib directory of the previous version

Version

1.2.0

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[aiwenmo]

Whether to replace the dependencies of the following path?

extends/flink/dinky