nielifeng commented on issue #10041: URL: https://github.com/apache/seatunnel/issues/10041#issuecomment-5140249025
I traced the reported stack to `FinishedJobsServlet -> JobInfoService#getJobsByStateJson -> BaseService#getJobInfoJson` (despite the issue title mentioning `running-jobs`). The null-safety problem was fixed by #10599, merged as `f1b72bca6`: it guards missing `jobDAGInfo` and nullable job timestamps instead of dereferencing them. I verified the fix on the current `dev` build at `7e25769`, which contains that merge commit: - `/running-jobs?page=1&rows=10` returned HTTP 200 through both master-role and worker-role REST endpoints. - `/finished-jobs/CANCELED?page=1&rows=10` returned HTTP 200 through both roles. - `/finished-jobs/FAILED?page=1&rows=10` returned HTTP 200 through both roles. - The three canceled job records currently present serialized `jobDag`, `metrics`, `startTime`, and `finishTime` successfully, with no null dereference. - The cluster remained clean after the read-only verification: 3 workers, 24/24 slots free, and 0 running/pending/failed jobs. I could not reproduce the 2.3.12 NPE on current `dev`. This issue can be closed as fixed by #10599; users on 2.3.12 should upgrade to a release containing `f1b72bca6`. -- 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]
