wgzhao commented on PR #12904:
URL: https://github.com/apache/seatunnel/pull/12904#issuecomment-6306919129
Thanks for the follow-up. Answers and locations:
- **Warning clearing**: on every successful refresh `loadError` and
`lastRefreshError` are reset,
so the warning is a transient toast and a recovered job does not keep a
stale error. The
post-load rejection spec now includes a third, successful response and
asserts that the job
updates and the refresh warning is gone afterwards.
- **F8**: yes, the missing-state description is rendered with
`t('detail.notFound.description', { jobId })`, and the spec asserts that
the route job id
(`123456789`) appears.
- **F1/F3 (docs)**: `found: false` is documented in EN/ZH v1 `/job-info` and
`/running-job`, and
in the v2 `/running-job` blocks; each points at the full v2 description
and the old-server
fallback.
- **F2/F4/F5 (CLI)**: `_poll_job_status` tolerates one status-less response,
uses a distinct
response-shape/failover message on a repeat, and the post-submit path no
longer says the id may
be wrong. `run_diagnose` checks `found: false` first and keeps the
status-less fallback.
- **F7 (SDK)**: `JobsApi.job_exists` raises `TypeError` for a
non-dictionary/non-JSON body instead
of reporting the job as absent.
Latest head: `86e750827`. UI `detail.spec.ts` has 6 cases, including the
post-load rejection and
recovery assertions; `vue-tsc` and `prettier --check` pass. The earlier
`engine-v2-it` Java 11/17
and UI build results remain the relevant green checks; the only Build
failures are the base
`LLMBooleanOutputTest` serialVersionUID issue.
--
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]
