feature: UnexpectedTaskExecutionException

[klopfdreh]

It would be great if the CTR throws an UnexpectedTaskExecutionException in favor of UnexpectedJobExecutionException so that it is possible to create an ApplicationListener which can handle certain error causes.

Because the TaskExecution itself is not serializable, the fields are assigned to the UnexpectedTaskExecutionException.

If this code is fine for you it also needs to be merged into: #5368

The UnexpectedTaskExecutionException also uses the ExitCodeGenerator interface so that the error code of a task which has failed is also forwarded through the CTR to its caller.

If the exit code is null, the UnexpectedTaskExecutionException returns -1

[klopfdreh]

@cppwfs - This PR is also mentioned for the time period after 2.11.0, but in general - does the change looks fine for you?

[cppwfs]

Thank you for the contribution. LGTM. But I want to test it once we get PR 5404 merged.

[klopfdreh]

Great! Thanks in advance for testing it! 👍

[klopfdreh]

@cppwfs / @onobc - due to the reason that this is only a small change and tests are already present - can you consider to integrate it in 2.11.1?

[onobc]

Hi @klopfdreh , should not be a problem. If we run into any issues we will ping back here.

[klopfdreh]

Sure - at any time 👍

[onobc]

HI @klopfdreh ,

Just wanted to give you a heads up, we are shipping a very quick 2.11.1 that contains CVE fixes only. No sooner had we released than 2 new CVEs were discovered in libraries we use. We are doing planning for 2.11.2 early next week and will include this PR in the next release which should be out relatively quick.

[klopfdreh]

Thanks for the information! 👍

[onobc]

Hi @klopfdreh , do you mind rebasing against main?

[klopfdreh]

Hi @klopfdreh , do you mind rebasing against main?

Done - let's see what the CI does and if all tests are running as expected.

I force-pushed the changes based on the current main.

[onobc]

Thanks for the contribution @klopfdreh. Awesome work!