Repository navigation
Shareable virtual-time traces for debounce and disposal #860
PerchAnton
started this conversation in
Show and tell
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I made an external RxPY example driven by TestScheduler. Its traces advance virtual time to check that a later value replaces a pending debounce value, completion flushes the pending value, and disposal prevents later delivery. The report records observed values after each time advance.
It uses no sleeps or wall-clock assumptions, and does not cover threads or network sources.
Adapter · three traces · setup and scope · external PR #14.
Python 3.12, reactivex 6.1.0; 3 traces / 14 steps. Linux, Windows and macOS CI.
The JSON runner is my external interaction-check project. Upstream would gain no runtime dependency. Would this be useful as a community example for reproducible timing reports?
All reactions