Let primary summary reads precede optional validation
This commit is contained in:
@@ -34,3 +34,25 @@ The initial capture attempt used waitfor on a static heading; the kit does not
|
||||
index that static label, although the saved PNG visibly showed the warning.
|
||||
Final captures use screenshots and a real Copy Input interaction instead.
|
||||
No physical device or Safari claim is made here. Nothing was deployed.
|
||||
|
||||
## Summary request ordering follow-up
|
||||
|
||||
The integrated application test exposed a real ordering dependency: the shared
|
||||
PipelinesClient serializes each request until its reply. Definition validation
|
||||
was enqueued immediately while its widget mounted, before the schedule section
|
||||
had enqueued `list_schedules`, so a delayed or unanswered optional validation
|
||||
held up primary Summary content.
|
||||
|
||||
Validation now starts in a microtask after synchronous Summary mounting. This
|
||||
lets the schedule request enter the existing transport queue first, without
|
||||
adding a timer or changing the client's serialization contract. The selected
|
||||
source and gateway are captured before deferral, so a later selection cannot
|
||||
change a queued request's source. The application fixture answers the new
|
||||
validation request and asserts that schedules and launch controls are available
|
||||
while validation is still unanswered. No selection, backend or transport code
|
||||
was changed. Focused application/definition-warning tests and analysis are
|
||||
recorded in the follow-up handoff; no full suite or deployment was run here.
|
||||
|
||||
Follow-up result: 149 application/definition-warning tests pass through the
|
||||
memory watchdog (`/tmp/memwatch/out.35VDe8`, peak 2105 MB, 49 s). Focused analysis
|
||||
is clean (`flutter-analyze.NVN15m`).
|
||||
|
||||
Reference in New Issue
Block a user