DanielLeens commented on PR #11307: URL: https://github.com/apache/seatunnel/pull/11307#issuecomment-6514275986
Thanks @SEZ9. Here are current-head pointers for that pass: the 3.5 .cmd launcher captures the Java status at :55, propagates nonzero at :61-64, rejects missing/empty command output at :68-77 and propagates spark-submit at :79-80. The .sh launcher uses quoted "$@" and classpath at :75 and an argument array at :91, without eval. The parent starter pom excludes embedded bindings at :85-95; TestSpark35StarterJarContentIT.java:75-88 requires exactly one external SLF4J 1.7 binding and no SLF4J 2 provider. docs/en/engines/spark.md:19-33 retains 3.4 guidance and names the reused 3.3 translation/Catalyst boundary. The quick-start at :30-33/:111-114 directs 3.5 to batch; Spark35BatchWriteTest.boundedMicroBatchCommitsRowsThroughStreamingAdapter:73-135 separately asserts termination, two input rows and exact committed records on Spark 3.5.8. That test does not establish public-starter streaming/checkpoint recovery. These points support my existing source clearance, not an attribution of runt ime proof to local execution. The actual resource-manager Failsafe "No tests were executed" and cancelled CI shards still need resolution; latest dev has no matching verified fix, so a simple sync or launcher change is not prescribed as their cure. Checked 2026-10-30T03:30:37.152172+00:00; head `4b80eba2519f8a1d13a54229dbd2090d7fca8a9f`. [Signal pull request update](https://github.com/apache/seatunnel/actions/runs/40644991988/job/122671615702)=`SUCCESS`; [Build](https://github.com/apache/seatunnel/runs/122671703070)=`FAILURE`. Base `dev`, `diverged`, ahead 69/behind 64; merge `blocked`. This is an unchanged-head discussion/CI clarification, not another full source review or an effective approval. Daniel has READ repository permission. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
