You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-`ActivationController` now tracks a suspended state and exposes `handle_exit(code_id, ActivationExitKind)`, so `PY_YIELD` transitions into suspension without disabling the activation while `PY_RETURN`/`PY_UNWIND` mark completion.
36
+
- Resume events clear suspension via `should_process_event`, ensuring activation gating stays engaged until the generator/coroutine finishes.
37
+
- Added Rust unit tests covering the suspension/resume flow, and the runtime now routes return-edge handling through the new enum to keep lifecycle state consistent.
38
+
- Verification: `just dev test` passes end-to-end.
35
39
36
40
### WS4 – Testing & Validation
37
41
-**Status:** Not started.
38
42
39
43
## Next Checkpoints
40
-
1.Begin WS3 by teaching `ActivationController` about suspension/resume semantics.
41
-
2.Plan and implement lifecycle tests ensuring activation gating stays consistent across yields/unwinds.
42
-
3.Evaluate whether additional telemetry/logging is needed before landing WS3/WS4.
44
+
1.Expand WS4 coverage per plan (async awaits, throw/resume, unwind) and update rust/python integration tests accordingly.
45
+
2.Add rust-side assertions (e.g., `print_tracer`) to validate the expanded event mask.
46
+
3.Document any telemetry updates or metadata changes before shipping the feature.
0 commit comments