wgzhao commented on PR #12904:
URL: https://github.com/apache/seatunnel/pull/12904#issuecomment-6331441533
Thanks @SEZ9 — here are the exact locations on `3578e25a4` for each point.
**1. `found: false` docs for v1 and the deprecated v2 `/running-job/:jobId`**
- v1 `/hazelcast/rest/maps/job-info/:jobId`:
`docs/en/engines/zeta/rest-api-v1.md:339-372` (ZH
`docs/zh/engines/zeta/rest-api-v1.md:359-390`)
- v1 `/hazelcast/rest/maps/running-job/:jobId`:
`docs/en/engines/zeta/rest-api-v1.md:454-464` (ZH
`docs/zh/engines/zeta/rest-api-v1.md:449-459`)
- v2 deprecated `/running-job/:jobId`:
`docs/en/engines/zeta/rest-api-v2.md:770-780` (ZH
`docs/zh/engines/zeta/rest-api-v2.md:742-752`); the full marker description
lives in the v2 `/job-info/:jobId` section at
`docs/en/engines/zeta/rest-api-v2.md:687-698`
- Python SDK page: `docs/en/engines/zeta/python-sdk.md:72` (ZH `:73`)
**2. CLI polling and the "id may be wrong" wording**
- Post-submit polling enters `_poll_job_status` at
`seatunnel-cli/seatunnel_cli/cli.py:1358`; implementation `:1360-1400`. It
stops immediately on `found: false` (`:1375`), tolerates one
status-less/non-dict 200 (`:1386`), and on a repeat prints the response-shape /
master-failover message (`:1393`).
- "The id may be wrong" now appears only in `run_diagnose`'s HTTP 404 branch
(`:1657`), for an id the user supplied. The post-submit path no longer uses
that wording. `run_diagnose` checks `found` first at `:1687-1688`.
**3. UI error path and missing-state job id**
- `detail.tsx:95-155`: `found === false` switches to the missing state
(`:98`), one status-less 200 is tolerated and a second switches to missing
(`:106-120`), and the catch distinguishes an initial-load error from a
post-load refresh rejection (`:139-154`).
- The missing state renders the requested id via
`t('detail.notFound.description', { jobId })` at `:616`.
**4. SDK non-dict handling**
- `tools/seatunnel-python-sdk/seatunnel/endpoints/jobs.py:90-105`:
`job_exists` raises `TypeError` for a non-dictionary/non-JSON body (`:100`)
before checking `found` (`:104-105`).
On CI: run `39608594369` skipped 53 jobs and failed only two pre-code jobs —
`changes` (`actions/setup-python@v5`: Python 3.11.0/x64 not available for
Ubuntu 26.04, since `ubuntu-latest` migrated to 26.04) and `Code style`
(`seatunnel-ci-tools` testCompile: Lombok `ExceptionInInitializerError` on the
new runner image). Neither exercises this diff, and a plain rerun on the same
image will likely reproduce them; the durable fix looks CI-side (pin the runner
image or update setup-python/Lombok), not in this PR. As suggested, the failed
jobs should be re-run rather than changing code.
--
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]
