Python: reactively() yields (response, aborted) and never raises - #204
Conversation
Current Aviator status
This PR was merged using Aviator (commit 9316156).
See the real-time status of this PR on the
Aviator webapp.
Use the Aviator Chrome Extension
to see the status of your PR within GitHub.
|
febb032 to
580bffa
Compare
Code reviewFound 2 issues. Both are Python
reboot/tests/reboot/reactivity_test.py Lines 30 to 34 in 580bffa
reboot/tests/reboot/dashboard/code_watcher_tests.py Lines 417 to 422 in 580bffa 🤖 Generated with Claude Code |
|
This pull request failed to merge: PR has a blocked label, remove to re-queue. After you have resolved the problem, you should remove the |
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
580bffa to
fa6cc67
Compare
In Python
.reactively()now yield a(response, aborted)and keep reading across errors instead of raising the method'sAbortedand stopping. The caller decides whether tocontinue,break, orraise aborted. This is the first half of making reactive reads consistent across clients (which will replace #185); the web client will follow in a separate PR, React already behaves this way.