IGNITE-28345 Skip client compute notification on executionFut fail

[ptupitsyn]

• Client request handler: prevent unexpected notifications when job/task execution fails early
• CI config: add build failure detection for "Unexpected xxx ID" in .NET to catch those problems early

https://issues.apache.org/jira/browse/IGNITE-28345

[Copilot]

Pull request overview

Fixes IGNITE-28345 by preventing client compute result notifications from being sent when the initial job submission (executionFut) fails, avoiding protocol-level “unexpected notification” scenarios on the client side.

Changes:

• Update compute execute notification flow to skip sending notifications when executionFut completes exceptionally.
• Add TeamCity Linux .NET log fail conditions to immediately fail builds on “Unexpected notification ID” / “Unexpected response ID”.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
modules/client-handler/src/main/java/org/apache/ignite/client/handler/requests/compute/ClientComputeExecuteRequest.java	Avoids sending compute result notifications when submission fails (no JobExecution available).
.teamcity/test/platform_tests/PlatformDotnetTestsLinux.kt	Makes CI fail fast on protocol desync log signatures in .NET platform tests.

Comments suppressed due to low confidence (1)

modules/client-handler/src/main/java/org/apache/ignite/client/handler/requests/compute/ClientComputeExecuteRequest.java:144

• sendResultAndState ignores errState from execution.stateAsync(): if state retrieval fails while the result succeeds, the notification is still sent as successful and the state is packed as nil, which can hide the underlying failure. Consider passing a combined error (first non-null of err and errState) for consistency with ClientComputeExecuteMapReduceRequest (which uses IgniteUtils.firstNotNull).

                execution.resultAsync().whenComplete((val, err) ->
                        execution.stateAsync().whenComplete((state, errState) -> {
                            try {
                                notificationSender.sendNotification(
                                        w -> {
                                            Marshaller<Object, byte[]> marshaller = extractMarshaller(execution);
                                            ClientComputeJobPacker.packJobResult(val, marshaller, w);
                                            packJobState(w, state);
                                        },
                                        err,
                                        hybridTimestamp(val));

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.