goodboy
/
tractor
1
0
Fork 2
Code Issues 4 Pull Requests 10 Packages Projects Releases Wiki Activity

py3.13 test-suite surgery #8

New Issue
Open
opened 2025-02-26 16:32:12 +00:00 by goodboy · 1 comment
goodboy commented 2025-02-26 16:32:12 +00:00
Owner

With py 3.13 comes all sorts of “fun”, namely some fairly disruptive lib and UX changes that break the test suite and in particular the pdbp REPL experience.

This issue is mostly meant as a notes-to-self while i work through figuring out all the broken test suites and ideally using any hanging tests to drive a tighter timeout style going forward.

Summary of to-blame cpython, stdlib, and core runtime changes

  1. trio’s release schedule requires we bump to at least trio>0.27 which flips on strict egs by default.
    • breaks most of our test suite, including hanging some tests, and likely will require either setting some strict_exception_groups=False (like ca65aea090 to start) in various suites and/or just forcing the move to explicit except* handling throughout..
    • this needed to be done sooner then later anyway Bp
  2. asyncio re-mucking its SIGINT machinery.
    • alongside new support for infected_aio=True set in the root actor massively borks the to_asyncio oriented tests amongst other very strange SIGINT handler mgmt (that i’d call fairly questionable)..
    • see #2 for hopefully most fixes to all this..
    • also interplays with the new .pause_from_sync() stuff intro-ed in #1 since all that is commonly/intended to be used within (partial) asyncio.Tasks.
  3. cpython deciding to render colored console output in tracebacks which completely rekts pattern matching in the tests/devx/test_debugger.py suite(s).
    • obvi we need to disable that for tests as per 8fa538c40e
  4. the stdlib getting a readline.backend: str and seemingly cpython itself being more commonly built (definitely with our move to uv for pking) to use libedit meaning our use of pdbp gets REPL UX issues (tab complete, vi mode) without specially configuring.
    • not that we test for this yet, but maybe we should ??

Summary of problematic/failing tests of note..

after running the full set and ctl-c any hangers the report is something like,

  • 92 failed,
  • 176 passed,
  • 7 skipped,
  • 4 xfailed,
  • 771 warnings

all in 10658.31s (2:57:38).. yeah bc some got left hanging until i noticed and mashed the SIGINT..

1st-PASS hanging tests

These needed ctl-c (and thought would need timeout wrapping..) UPDATE: seems like for some weird reason certain tests were hanging due to debug_mode==True being set in the ._state._runtime_vars?? No idea why it stopped either 😂

gonna order these according to what i think is least annoying to deal with first and then link commits which provide timeout-ing and then with follow up patches to fix 🙏..

  • ‘tests/test_child_manages_service_nursery.py::test_actor_managed_trio_nursery_task_error_cancels_aio[asyncio_mode=False]’
  • ‘tests/test_rpc.py::test_rpc_errors[this_mod_bad_func]’

test_iter_peer_cancellation-suite,

  • ‘tests/test_inter_peer_cancellation.py::test_do_not_swallow_error_before_started_by_remote_contextcancelled’
  • ‘tests/test_inter_peer_cancellation.py::test_peer_canceller[rte_during_ctxerr=False’
  • ‘tests/test_inter_peer_cancellation.py::test_peer_canceller[rte_during_ctxerr=True]’
  • ‘tests/test_inter_peer_cancellation.py::test_peer_spawns_and_cancels_service_subactor[None-None]’
  • ‘tests/test_inter_peer_cancellation.py::test_peer_spawns_and_cancels_service_subactor[None-KeyboardInterrupt]’

infected_asyncio-suite,

  • ‘tests/test_infected_asyncio.py::test_aio_simple_error’
  • ‘tests/test_infected_asyncio.py::test_aio_cancelled_from_aio_causes_trio_cancelled’
  • ‘tests/test_infected_asyncio.py::test_trio_error_cancels_intertask_chan’
  • ‘tests/test_infected_asyncio.py::test_aio_errors_and_channel_propagates_and_closes’
  • ‘tests/test_infected_asyncio.py::test_echoserver_detailed_mechanics[raise_error=False]’
  • ‘tests/test_infected_asyncio.py::test_echoserver_detailed_mechanics[raise_error=<class ’Exception’>]’

Seemingly all fixed after 71562e0af7

2nd-PASS (28) failing tests

once there were no more hangs the soln patches seemed to have narrowed us down to the remaining fail set,

  • tests/test_advanced_faults.py::test_ipc_channel_break_during_stream[break_parent-no_msgstream_aclose] - RuntimeError: generator raised StopIteration
  • tests/test_advanced_faults.py::test_ipc_channel_break_during_stream[break_parent-pre_aclose_msgstream] - RuntimeError: generator raised StopIteration
  • tests/test_advanced_faults.py::test_ipc_channel_break_during_stream[break_both_parent_first-no_msgstream_aclose] - RuntimeError: generator raised StopIteration
  • tests/test_advanced_faults.py::test_ipc_channel_break_during_stream[break_both_parent_first-pre_aclose_msgstream] - RuntimeError: generator raised StopIteration

Solved by 375c00da6e

  • tests/test_discovery.py::test_close_channel_explicit[trio-False] - BaseExceptionGroup: Exceptions from Trio nursery (1 sub-exception)
  • tests/test_discovery.py::test_close_channel_explicit[trio-True] - BaseExceptionGroup: Exceptions from Trio nursery (1 sub-exception)
  • tests/test_discovery.py::test_close_channel_explicit_remote_arbiter[trio-False] - BaseExceptionGroup: Exceptions from Trio nursery (1 sub-exception)
  • tests/test_discovery.py::test_close_channel_explicit_remote_arbiter[trio-True] - BaseExceptionGroup: Exceptions from Trio nursery (1 sub-exception)

Solved by 375c00da6e

  • tests/test_docs_examples.py::test_example[quick_cluster.py]
    • AssertionError: assert 1 == 0
  • tests/test_docs_examples.py::test_example[server.cpython-312.pyc]
    • UnicodeDecodeError: ‘utf-8’ codec can’t decode byte 0xcb in position 0: i…

Fixed by ad56d10c51

  • tests/test_infected_asyncio.py::test_basic_interloop_channel_stream[fan_out_w_chan_subscribe=False] - tractor._exceptions.RemoteActorError: remote task raised a ‘AsyncioTaskExited’
  • tests/test_infected_asyncio.py::test_basic_interloop_channel_stream[fan_out_w_chan_subscribe=True] - tractor._exceptions.RemoteActorError: remote task raised a ‘AsyncioTaskExited’

fixed by 7fac170f8d and e1bacaf4f4

  • tests/test_task_broadcasting.py::test_consumer_and_parent_maybe_lag[trio-task_delays1] - ExceptionGroup: Exceptions from Trio nursery (1 sub-exception)
  • tests/test_task_broadcasting.py::test_no_raise_on_lag - BaseExceptionGroup: Exceptions from Trio nursery (1 sub-exception)

Fixed by 55809dac51

3rd-PASS (22) failing tests

no more hanging tests, just devx/debugger relateds, root-infected-aio and some typed-msging laggards.

= 22 failed, 242 passed, 7 skipped, 4 xfailed, 1220 warnings in 464.82s (0:07:44) =

  • tests/test_trioisms.py::test_stashed_child_nursery[False]
    • ExceptionGroup: Exceptions from Trio nursery (1 sub-exception)
  • tests/test_trioisms.py::test_acm_embedded_nursery_propagates_enter_err[True-False]
    • AttributeError: ‘NoneType’ object has no attribute ‘value’
  • tests/test_trioisms.py::test_acm_embedded_nursery_propagates_enter_err[True-True]
    • AttributeError: ‘NoneType’ object has no attribute ‘value’

|_> fixed by d32dc4e889

  • tests/devx/test_debugger.py::test_subactor_breakpoint[ctl-c=False-trio]
    • pexpect.exceptions.EOF: End Of File (EOF). Exception style platform.
  • tests/devx/test_debugger.py::test_subactor_breakpoint[ctl-c=True-trio]
    • pexpect.exceptions.EOF: End Of File (EOF). Exception style platform.
  • tests/devx/test_debugger.py::test_multi_nested_subactors_error_through_nurseries[trio]
    • pexpect.exceptions.TIMEOUT: Timeout exceeded.

Mostly repaired by #18

4th-PASS (11 failing) -> back to where i was pre 3.13 XD

  • tests/devx/test_pause_from_non_trio.py::test_pause_from_sync[ctl-c=True-trio]

    • this is getting stuck in a really bad root actor state where SIGINT is being ingored if you look at the process in htop.. So, made a couple issues and linked to .xfail()-ed tests:

  • tests/devx/test_pause_from_non_trio.py::test_sync_pause_from_aio_task[ctl-c=True-trio]

    • this is exiting early due to KBI since our shield handler seems to get removed?

  • commit 81349f7c09 marks the tests

  • #9 is the issue to track and ideally fix and/or report upstream ;)

  • tests/devx/test_tooling.py::test_shield_pause[trio]

    • ValueError: Could not find pattern in before output?

All fixed by b1bcbf5693 and generally in #18

5th-n-FINAL? (4 failing)

So more or less back to where i was doing typed-msging unit tests?

Bo

  • tests/test_caps_based_msging.py::test_codec_hooks_mod[use_codec_hooks-any_type]
    • tractor._exceptions.RemoteActorError: remote task raised a ‘TypeError’
  • tests/test_caps_based_msging.py::test_codec_hooks_mod[use_codec_hooks-nsp_type]
    • tractor._exceptions.RemoteActorError: remote task raised a ‘ValidationError’
  • tests/test_caps_based_msging.py::test_codec_hooks_mod[use_codec_hooks-maybe_nsp_type]
    • tractor._exceptions.RemoteActorError: remote task raised a ‘ValidationError’
  • tests/test_caps_based_msging.py::test_limit_msgspec
    • AssertionError: assert typing.Union[typing.Any, msgspec.Raw] is typing.Any

All changed and fixed after #19

With py 3.13 comes all sorts of "fun", namely some fairly disruptive lib and UX changes that break the test suite and in particular the `pdbp` REPL experience. This issue is mostly meant as a notes-to-self while i work through figuring out all the broken test suites and ideally using any hanging tests to drive a tighter timeout style going forward. --- #### Summary of to-blame cpython, stdlib, and core runtime changes 1. `trio`'s release schedule requires we bump to at least `trio>0.27` which flips on strict egs by default. - breaks most of our test suite, including hanging some tests, and likely will require either setting some `strict_exception_groups=False` (like ca65aea0902c9b94d4c504d8339dd7046d68f03a to start) in various suites and/or just forcing the move to explicit `except*` handling throughout.. - [ ] this needed to be done sooner then later anyway Bp 2. `asyncio` re-mucking its SIGINT machinery. - alongside new support for `infected_aio=True` set in the root actor massively borks the `to_asyncio` oriented tests amongst other very strange SIGINT handler mgmt (that i'd call fairly questionable).. - see https://pikers.dev/goodboy/tractor/pulls/2 for hopefully most fixes to all this.. - also interplays with the new `.pause_from_sync()` stuff intro-ed in #1 since all that is commonly/intended to be used within (partial) `asyncio.Task`s. 3. cpython deciding to render colored console output in tracebacks which completely rekts pattern matching in the `tests/devx/test_debugger.py` suite(s). - obvi we need to disable that for tests as per 8fa538c40e4631018a77c421be632eb889f50f1c 4. the stdlib getting a `readline.backend: str` and seemingly cpython itself being more commonly built (definitely with our move to `uv` for pking) to use `libedit` meaning our use of `pdbp` gets REPL UX issues (tab complete, vi mode) without specially configuring. - [ ] not that we test for this yet, but maybe we should ?? --- #### Summary of problematic/failing tests of note.. after running the full set and ctl-c any hangers the report is something like, - 92 failed, - 176 passed, - 7 skipped, - 4 xfailed, - 771 warnings all in 10658.31s (2:57:38).. yeah bc some got left hanging until i noticed and mashed the SIGINT.. --- ##### 1st-PASS hanging tests These needed ctl-c (and thought would need timeout wrapping..) UPDATE: seems like for some weird reason certain tests were hanging due to `debug_mode==True` being set in the `._state._runtime_vars`?? No idea why it stopped either :joy: gonna order these according to what i think is least annoying to deal with first and then link commits which provide timeout-ing and then with follow up patches to fix :pray:.. - 'tests/test_child_manages_service_nursery.py::test_actor_managed_trio_nursery_task_error_cancels_aio[asyncio_mode=False]' --- - 'tests/test_rpc.py::test_rpc_errors[this_mod_bad_func]' --- `test_iter_peer_cancellation`-suite, - 'tests/test_inter_peer_cancellation.py::test_do_not_swallow_error_before_started_by_remote_contextcancelled' - 'tests/test_inter_peer_cancellation.py::test_peer_canceller[rte_during_ctxerr=False' - 'tests/test_inter_peer_cancellation.py::test_peer_canceller[rte_during_ctxerr=True]' - 'tests/test_inter_peer_cancellation.py::test_peer_spawns_and_cancels_service_subactor[None-None]' - 'tests/test_inter_peer_cancellation.py::test_peer_spawns_and_cancels_service_subactor[None-KeyboardInterrupt]' --- `infected_asyncio`-suite, - 'tests/test_infected_asyncio.py::test_aio_simple_error' - 'tests/test_infected_asyncio.py::test_aio_cancelled_from_aio_causes_trio_cancelled' - 'tests/test_infected_asyncio.py::test_trio_error_cancels_intertask_chan' - 'tests/test_infected_asyncio.py::test_aio_errors_and_channel_propagates_and_closes' - 'tests/test_infected_asyncio.py::test_echoserver_detailed_mechanics[raise_error=False]' - 'tests/test_infected_asyncio.py::test_echoserver_detailed_mechanics[raise_error=<class 'Exception'>]' Seemingly all fixed after 71562e0af7e9d13f04f8069640307b42557cdfe3 --- ##### 2nd-PASS (28) failing tests once there were no more hangs the soln patches seemed to have narrowed us down to the remaining fail set, - tests/test_advanced_faults.py::test_ipc_channel_break_during_stream[break_parent-no_msgstream_aclose] - RuntimeError: generator raised StopIteration - tests/test_advanced_faults.py::test_ipc_channel_break_during_stream[break_parent-pre_aclose_msgstream] - RuntimeError: generator raised StopIteration - tests/test_advanced_faults.py::test_ipc_channel_break_during_stream[break_both_parent_first-no_msgstream_aclose] - RuntimeError: generator raised StopIteration - tests/test_advanced_faults.py::test_ipc_channel_break_during_stream[break_both_parent_first-pre_aclose_msgstream] - RuntimeError: generator raised StopIteration Solved by 375c00da6e7595454b363c726766081e6b7d3a03 - tests/test_discovery.py::test_close_channel_explicit[trio-False] - BaseExceptionGroup: Exceptions from Trio nursery (1 sub-exception) - tests/test_discovery.py::test_close_channel_explicit[trio-True] - BaseExceptionGroup: Exceptions from Trio nursery (1 sub-exception) - tests/test_discovery.py::test_close_channel_explicit_remote_arbiter[trio-False] - BaseExceptionGroup: Exceptions from Trio nursery (1 sub-exception) - tests/test_discovery.py::test_close_channel_explicit_remote_arbiter[trio-True] - BaseExceptionGroup: Exceptions from Trio nursery (1 sub-exception) Solved by 375c00da6e7595454b363c726766081e6b7d3a03 - tests/test_docs_examples.py::test_example[quick_cluster.py] - AssertionError: assert 1 == 0 - tests/test_docs_examples.py::test_example[server.cpython-312.pyc] - UnicodeDecodeError: 'utf-8' codec can't decode byte 0xcb in position 0: i... Fixed by ad56d10c51ec29ee9248f2e438e9b2451270ed8c - tests/test_infected_asyncio.py::test_basic_interloop_channel_stream[fan_out_w_chan_subscribe=False] - tractor._exceptions.RemoteActorError: remote task raised a 'AsyncioTaskExited' - tests/test_infected_asyncio.py::test_basic_interloop_channel_stream[fan_out_w_chan_subscribe=True] - tractor._exceptions.RemoteActorError: remote task raised a 'AsyncioTaskExited' fixed by 7fac170f8d271dd5513368ebd4d66999c1e8815d and e1bacaf4f4223d40e9b6869fdc9138ac0773f6f9 - tests/test_task_broadcasting.py::test_consumer_and_parent_maybe_lag[trio-task_delays1] - ExceptionGroup: Exceptions from Trio nursery (1 sub-exception) - tests/test_task_broadcasting.py::test_no_raise_on_lag - BaseExceptionGroup: Exceptions from Trio nursery (1 sub-exception) Fixed by 55809dac51ca9f1f343468dfa4c4e8369fc7e6bf --- ##### 3rd-PASS (22) failing tests no more hanging tests, just devx/debugger relateds, root-infected-aio and some typed-msging laggards. `= 22 failed, 242 passed, 7 skipped, 4 xfailed, 1220 warnings in 464.82s (0:07:44) =` - tests/test_trioisms.py::test_stashed_child_nursery[False] - ExceptionGroup: Exceptions from Trio nursery (1 sub-exception) - tests/test_trioisms.py::test_acm_embedded_nursery_propagates_enter_err[True-False] - AttributeError: 'NoneType' object has no attribute 'value' - tests/test_trioisms.py::test_acm_embedded_nursery_propagates_enter_err[True-True] - AttributeError: 'NoneType' object has no attribute 'value' |_> fixed by d32dc4e889443d81a818438ea9db326cbc6eab6c - tests/devx/test_debugger.py::test_subactor_breakpoint[ctl-c=False-trio] - pexpect.exceptions.EOF: End Of File (EOF). Exception style platform. - tests/devx/test_debugger.py::test_subactor_breakpoint[ctl-c=True-trio] - pexpect.exceptions.EOF: End Of File (EOF). Exception style platform. - tests/devx/test_debugger.py::test_multi_nested_subactors_error_through_nurseries[trio] - pexpect.exceptions.TIMEOUT: Timeout exceeded. Mostly repaired by #18 ##### 4th-PASS (11 failing) -> back to where i was pre 3.13 XD - tests/devx/test_pause_from_non_trio.py::test_pause_from_sync[ctl-c=True-trio] - this is getting stuck in a really bad root actor state where SIGINT is being ingored if you look at the process in `htop`.. So, made a couple issues and linked to `.xfail()`-ed tests: - tests/devx/test_pause_from_non_trio.py::test_sync_pause_from_aio_task[ctl-c=True-trio] - this is exiting early due to KBI since our shield handler seems to get removed? - commit 81349f7c09acf9098b560f44e32cb27d91e41242 marks the tests - #9 is the issue to track and ideally fix and/or report upstream ;) - tests/devx/test_tooling.py::test_shield_pause[trio] - ValueError: Could not find pattern in `before` output? All fixed by b1bcbf569386398eba3fc65d8d943e2941cfcc77 and generally in #18 ##### 5th-n-FINAL? (4 failing) So more or less back to where i was doing typed-msging unit tests? Bo - tests/test_caps_based_msging.py::test_codec_hooks_mod[use_codec_hooks-any_type] - tractor._exceptions.RemoteActorError: remote task raised a 'TypeError' - tests/test_caps_based_msging.py::test_codec_hooks_mod[use_codec_hooks-nsp_type] - tractor._exceptions.RemoteActorError: remote task raised a 'ValidationError' - tests/test_caps_based_msging.py::test_codec_hooks_mod[use_codec_hooks-maybe_nsp_type] - tractor._exceptions.RemoteActorError: remote task raised a 'ValidationError' - tests/test_caps_based_msging.py::test_limit_msgspec - AssertionError: assert typing.Union[typing.Any, msgspec.Raw] is typing.Any All changed and fixed after #19
goodboy commented 2025-03-25 16:16:07 +00:00
Poster
Owner

As an update we are entirely clean here as of #18 with some lingering typed-msging tests being reworked in a follow up downstream PR.

As an update we are entirely clean here as of #18 with some lingering typed-msging tests being reworked in a follow up downstream PR.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
hilevel_serman
oco_supervisor_prototype
shm_apis
ext_type_plds
py313_support
aio_abandons
runtime_to_msgspec
main
pkg_tidying
structural_dynamics_of_flow
multihost_exs
one_ring_to_rule_them_all
uv_migration_pre_msgspec_in_runtime
remote_inceptions
ext_type_plds_XPS_BACKUP
modden_spawn_from_client_req
multihomed
devx_subpkg
asyncio_debugger_support
ctx_cancel_semantics_and_overruns
pre_pretty_struct_dep_commit_b54cb66
ctx_cancel_semantics_and_overruns_REVERSED_FACEPALM
uv_migration
to_asyncio_refinery
runtime_to_msgspec_XPS_BACKUP
rae_message_packing
msg_codecs
old_msg_types
asyncio_debug_mode
pause_from_sync_w_greenback
mv_to_new_trio_py3.11
modden_spawn_from_client_req_XPS_BACKUP
shielded_ctx_cancel
dereg_on_oserror
ctx_cancel_semantics_and_overruns_XPS_GH_BACKUP
msgtypes
master
switch_to_pdbp
proper_breakpoint_hooking
drop_proc_actxmngr
ctx_result_consumption
readme_touchups
ipython_integration
breceiver_internals
piker_pin
ipc_failure_while_streaming
deprecate_arbiter_addr
prompt_on_ctrlc
dun_unset_current_actor
ipc_failwhilestream_backup
macos_in_ci
harden_cluster_tests
eg_backup
exceptiongroups
egs_with_ctx_res_consumption
debug_lock_blocking
callable_key_maybe_open_context
spawn_backend_table
pin_pre_trio_0.22
pytest_report_workaround
lifetime_stack_tests
we_bein_all_matchy
debug_event_guard
disable_win_ci
alpha5
signint_saviour
sigintsaviour_citesthackin
sigintsaviour_ci_worked
aio_error_propagation
drop_msgpack
310_windows
ci_sdist_install
include_readme
310_plus
name_query
sort_subs_results_infected_aio
aio_explicit_task_cancels
fence_mp
sigint_ignore_in_pdb_repl
sigint2
msgpack_lists_by_default
nspaths
experimental_subpkg
maybe_cancel_the_cancel_
moar_timeoutz
drop_old_nooz_files
raise_runinactor_error
win_ci_timeout
alpha4
infect_asyncio
expected_ctx_cancelled
new_mypy
context_caching
end_of_channel_fixes
agpl_commit_msg_fix
agpl
stricter_context_starting
acked_backup
faster_daemon_cancels
early_deth_fixes
clusters_and_hot_tips
alpha3
pubsub_startup_response_msg
iaio_backup
trionics
graceful_gather
246_facepalm_backup
patch-async-enter-all
immediate_remote_cancels
less_logging
zombie_lord_infinite
optional_msgspec_support
fix_kbi_in_ctx_block
logo_tweaks
use_trio_on_win
alpha2
msgspec_infect_asyncio
live_on_air_from_tokio
tokio_backup
debugger_test_tweaks
fix_news_links
wats_da_nooz
ctx_debugger
bi_streaming_no_debugger_stuff
round_2_ci_windows
CI_increment_for_windows_bidirstreaming
ctx_debugger_from_hardening
infect_asyncio_backup
debugger_hardening
bi_streaming
transport_cleaning
context_finesse
cf_backup
db_backup
pre_bad_close
stdstream_clobber_fix
bistream_backup
transport_hardening
msgspec_not_fucked
try_msgspec
prehardkill
windows_bi_streaming
docs_revamp
new_docs_polish
wip_fix_asyncio_gen_streaming
drop_run
mp_teardown_hardening
stream_contexts
drop_sync_funcs
pub_connect_msg
sync_cancel
stream_clones
first_pypi_release
single_func_example
readme_pump
kinda_drop_run
mp_hang_search
eg_worker_poolz
sync_breakpoint
actor_state_via_messages
we_aint_got_zombie_shields
deprecate_rpcmodpaths
implicit_runtime
drop_tractor_run
py3.9
denoise_logging
func_refs_always
fix_debug_tests_in_ci_again
stream_channel_shield
pdb_madness
advanced_debugger_testing
clean_log_header
debug_refine
debug_refinements
drop_warn
multiproc_debug
debugger_on_windows
bug_in_debug
debug_tests
native_debugging
matrix
dereg_on_channel_aclose
ensure_deregister
start_up_sequence_trickery
fix_win_ci_again
stin_char_relay
flaky_tests
drop_cloudpickle
reorg_entry_points
drop-trip-update-trio
init_sphinx_docs
example_tests
implicit_rpc
fix_examples_in_docs
try_trip
log_task_context
drop_event_clear
more_thorough_super_tests
pip_ci_fix
windows_support
rename_forkserver_mod
user_update
win_ci
stream_functions
propagate_loglevel
ipc_iternals_renaming
close_mem_chans
docs_example_fixes
spawn_method_support
trio_memchans
contexts
remote_module_errors
remote_task_cancelling
fix_46
loglevel_to_tractor_tests
expose_tractor_test
improved_errors
self_register
multi_program_tests
tests_reorg
type_annotations
py3.7_tweaks
reliable_cancel_tests
attrs_it_up
wait_for_actor
draft_readme
init_docs
reg_with_uid
forkserver_singleton
drop_main_kwarg
asyncgen_closing_fix
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: goodboy/tractor#8
There is no content yet.
Delete Branch "%!s(<nil>)"

Deleting a branch is permanent. Although the deleted branch may exist for a short time before cleaning up, in most cases it CANNOT be undone. Continue?