Update async-kernel installation command due to changes in async-kernel version 0.19.0.

[fleming79]

The command to install in async-kernel has been changed in v0.19.0.

[rgbkrk]

Thanks @fleming79!

[github-actions]

Kernel Conformance Matrix

Kernel	Protocol	Tier 1	Tier 2	Tier 3	Tier 4	Total
almond	5.4	6/11	4/7	1/4	1/5	12/27
ark	5.4	11/11	7/7	3/4	5/5	26/27
deno	unknown	0/1	0/0	0/0	0/0	0/1
evcxr	5.3	10/11	3/7	2/4	3/5	18/27
gonb	5.4	6/11	1/7	1/4	3/5	11/27
ijulia	5.4	10/11	6/7	3/4	5/5	24/27
ipykernel	5.3	11/11	7/7	4/4	5/5	27/27
ocaml-jupyter	5.2	9/11	4/7	2/4	1/5	16/27
xeus-cpp	5.6	11/11	6/7	2/4	5/5	24/27
xeus-lua	5.6	11/11	7/7	4/4	5/5	27/27
xeus-octave	5.6	11/11	6/7	0/4	5/5	22/27
xeus-python	5.6	11/11	7/7	4/4	5/5	27/27
xeus-r	5.6	11/11	7/7	3/4	5/5	26/27
xeus-sql	5.6	8/11	5/7	0/4	4/5	17/27
xeus-sqlite	5.6	8/11	6/7	0/4	4/5	18/27

---

almond (scala) - 15 failures, 0 skipped

Language: scala | Protocol: 5.4

Failures

Test	Message Type	Likely Source	Reason
execute_reply_ok	execute_request	harness_error	Protocol error: Error deserializing content for msg_type execute_reply: invalid type: string "\u{1b}[36mx\u{1b}[39m: \u{1b}[32mInt\u{1b}[39m = \u{1b}[32m1\u{1b}[39m", expected internally tagged enum ExpressionResult
status_busy_idle_lifecycle	status	unknown	Protocol error: Error deserializing content for msg_type execute_reply: invalid type: string "\u{1b}[36mx\u{1b}[39m: \u{1b}[32mInt\u{1b}[39m = \u{1b}[32m1\u{1b}[39m", expected internally tagged enum ExpressionResult
execute_input_broadcast	execute_input	unknown	Protocol error: Error deserializing content for msg_type execute_reply: invalid type: string "\u{1b}[36mx\u{1b}[39m: \u{1b}[32mInt\u{1b}[39m = \u{1b}[32m1\u{1b}[39m", expected internally tagged enum ExpressionResult
history_request	history_request	unknown	Protocol error: Error deserializing content for msg_type history_reply: missing field history
error_handling	execute_request	unknown	Protocol error: Error deserializing content for msg_type error: missing field traceback
execute_result	execute_result	unknown	Protocol error: Error deserializing content for msg_type execute_reply: invalid type: string "\u{1b}[36mid\u{1b}[39m: \u{1b}[32mString\u{1b}[39m = \u{1b}[32m"620ae6f0-4e5c-4237-9c99-ea2134ffcdd0"\u{1b}[39m", expected internally tagged enum ExpressionResult
rich_execute_result	execute_result	unknown	Protocol error: Error deserializing content for msg_type execute_reply: invalid type: string "\u{1b}[36mres11\u{1b}[39m: \u{1b}[32mInt\u{1b}[39m = \u{1b}[32m2\u{1b}[39m", expected internally tagged enum ExpressionResult
stdin_input_request	input_request	harness_error	Timeout waiting for iopub idle (stdin test)
comms_lifecycle	comm_open	harness_error	Kernel unresponsive after comm: Timeout waiting for iopub idle
interrupt_request	interrupt_request	unknown	Protocol error: Error deserializing content for msg_type interrupt_reply: missing field status
execution_count_increments	execute_request	unknown	Counts didn't increment: 12 -> 0
shutdown_reply	shutdown_request	unknown	Protocol error: Error deserializing content for msg_type shutdown_reply: missing field status

ark () - 1 failures, 0 skipped

Language: R | Protocol: 5.4

Failures

Test	Message Type	Likely Source	Reason

deno (unknown) - 1 failures, 0 skipped

Language: typescript | Protocol: unknown

Failures

Test	Message Type	Likely Source	Reason
kernel_startup	kernel_info_request	protocol_error	Protocol error: Error deserializing content for msg_type kernel_info_reply: data did not match any variant of untagged enum CodeMirrorMode

evcxr (evcxr_jupyter) - 6 failures, 3 skipped

Language: Rust | Protocol: 5.3

Failures

Test	Message Type	Likely Source	Reason
inspect_request	inspect_request	unknown	Timeout waiting for shell reply
history_request	history_request	unknown	Timeout waiting for shell reply
comm_info_request	comm_info_request	unknown	Timeout waiting for shell reply
interrupt_request	interrupt_request	unknown	Protocol error: Error deserializing content for msg_type interrupt_reply: missing field status

Skipped (Not Implemented)

• display_data: Kernel can produce display_data messages for rich output
• update_display_data: Kernel can update existing displays via update_display_data
• stdin_input_request: Kernel can request input from frontend via stdin channel

gonb (gonb) - 15 failures, 1 skipped

Language: go | Protocol: 5.4

Failures

Test	Message Type	Likely Source	Reason
execute_stdout	execute_request	unknown	No stdout containing 'hello'
execute_stderr	stream	unknown	No stderr containing 'error'
execute_reply_ok	execute_request	kernel_error	execute_reply status: Error
complete_request	complete_request	unknown	Timeout waiting for shell reply
inspect_request	inspect_request	unknown	Expected inspect_reply, got "execute_reply"
is_complete_complete	is_complete_request	unknown	Expected is_complete_reply, got "inspect_reply"
is_complete_incomplete	is_complete_request	unknown	Timeout waiting for shell reply
history_request	history_request	unknown	Timeout waiting for shell reply
comm_info_request	comm_info_request	unknown	Timeout waiting for shell reply
execute_result	execute_result	unknown	No execute_result on iopub
stdin_input_request	input_request	unexpected_content	No input_request received on stdin channel
interrupt_request	interrupt_request	unknown	Timeout waiting for control reply
shutdown_reply	shutdown_request	unknown	Timeout waiting for control reply

Skipped (Not Implemented)

• rich_execute_result: Expression evaluation produces execute_result with rich MIME types (HTML, images, etc.)

ijulia (ijulia) - 2 failures, 1 skipped

Language: julia | Protocol: 5.4

Failures

Test	Message Type	Likely Source	Reason
comm_info_request	comm_info_request	unknown	Timeout waiting for shell reply

Skipped (Not Implemented)

• update_display_data: Kernel can update existing displays via update_display_data

ocaml-jupyter (ocaml-jupyter) - 9 failures, 2 skipped

Language: OCaml | Protocol: 5.2

Failures

Test	Message Type	Likely Source	Reason
history_request	history_request	unknown	Protocol error: Error deserializing content for msg_type history_reply: missing field status
comm_info_request	comm_info_request	unknown	Timeout waiting for shell reply
stdin_input_request	input_request	unexpected_content	No input_request received on stdin channel
interrupt_request	interrupt_request	unknown	Timeout waiting for control reply
execution_count_increments	execute_request	unknown	Timeout waiting for iopub idle
parent_header_correlation	parent_header	unknown	Timeout waiting for iopub idle
shutdown_reply	shutdown_request	unknown	Timeout waiting for control reply

Skipped (Not Implemented)

• update_display_data: Kernel can update existing displays via update_display_data
• rich_execute_result: Expression evaluation produces execute_result with rich MIME types (HTML, images, etc.)

xeus-cpp (xeus-cpp) - 2 failures, 1 skipped

Language: C++ | Protocol: 5.6

Failures

Test	Message Type	Likely Source	Reason
execute_result	execute_result	unknown	No execute_result on iopub

Skipped (Not Implemented)

• rich_execute_result: Expression evaluation produces execute_result with rich MIME types (HTML, images, etc.)

xeus-octave (xoctave) - 2 failures, 3 skipped

Language: Octave | Protocol: 5.6

Failures

Test	Message Type	Likely Source	Reason
execute_result	execute_result	unknown	No execute_result on iopub

Skipped (Not Implemented)

• display_data: Kernel can produce display_data messages for rich output
• update_display_data: Kernel can update existing displays via update_display_data
• rich_execute_result: Expression evaluation produces execute_result with rich MIME types (HTML, images, etc.)

xeus-r (xr) - 1 failures, 0 skipped

Language: R | Protocol: 5.6

Failures

Test	Message Type	Likely Source	Reason

xeus-sql (xsql) - 7 failures, 3 skipped

Language: MySQL | Protocol: 5.6

Failures

Test	Message Type	Likely Source	Reason
execute_stdout	execute_request	unknown	No stdout containing 'hello'
execute_stderr	stream	unknown	No stderr containing 'error'
execute_reply_ok	execute_request	kernel_error	execute_reply status: Error
execute_result	execute_result	unknown	No execute_result on iopub
stdin_input_request	input_request	unexpected_content	No input_request received on stdin channel

Skipped (Not Implemented)

• display_data: Kernel can produce display_data messages for rich output
• update_display_data: Kernel can update existing displays via update_display_data
• rich_execute_result: Expression evaluation produces execute_result with rich MIME types (HTML, images, etc.)

xeus-sqlite (xsqlite) - 5 failures, 4 skipped

Language: sql | Protocol: 5.6

Failures

Test	Message Type	Likely Source	Reason
execute_stdout	execute_request	unknown	No stdout containing 'hello'
execute_stderr	stream	unknown	No stderr containing 'error'
execute_reply_ok	execute_request	kernel_error	execute_reply status: Error
execute_result	execute_result	unknown	No execute_result on iopub

Skipped (Not Implemented)

• display_data: Kernel can produce display_data messages for rich output
• update_display_data: Kernel can update existing displays via update_display_data
• rich_execute_result: Expression evaluation produces execute_result with rich MIME types (HTML, images, etc.)
• stdin_input_request: Kernel can request input from frontend via stdin channel

---

Test Results by Message Type

Test	Message Type	almond	ark	deno	evcxr	gonb	ijulia	ipykernel	ocaml-jupyter	xeus-cpp	xeus-lua	xeus-octave	xeus-python	xeus-r	xeus-sql	xeus-sqlite
comm_info_request	comm_info_request	✅	✅	-	❌	❌	❌	✅	❌	✅	✅	✅	✅	✅	✅	✅
comms_lifecycle	comm_open	❌	✅	-	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅
complete_request	complete_request	✅	✅	-	✅	❌	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅
display_data	display_data	✅	✅	-	⏭️	✅	✅	✅	✅	✅	✅	⏭️	✅	✅	⏭️	⏭️
error_handling	execute_request	❌	✅	-	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅
execute_input_broadcast	execute_input	❌	✅	-	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅
execute_reply_ok	execute_request	❌	✅	-	✅	❌	✅	✅	✅	✅	✅	✅	✅	✅	❌	❌
execute_result	execute_result	❌	✅	-	✅	❌	✅	✅	✅	❌	✅	❌	✅	✅	❌	❌
execute_stderr	stream	✅	✅	-	✅	❌	✅	✅	✅	✅	✅	✅	✅	✅	❌	❌
execute_stdout	execute_request	✅	✅	-	✅	❌	✅	✅	✅	✅	✅	✅	✅	✅	❌	❌
execution_count_increments	execute_request	❌	✅	-	✅	✅	✅	✅	❌	✅	✅	✅	✅	✅	✅	✅
heartbeat_responds	heartbeat	✅	✅	-	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅
history_request	history_request	❌	✅	-	❌	❌	✅	✅	❌	✅	✅	✅	✅	✅	✅	✅
inspect_request	inspect_request	✅	✅	-	❌	❌	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅
interrupt_request	interrupt_request	❌	✅	-	❌	❌	✅	✅	❌	✅	✅	✅	✅	✅	✅	✅
iopub_welcome	iopub_welcome	⚠️	✅	-	⚠️	⚠️	⚠️	✅	⚠️	✅	✅	✅	✅	✅	✅	✅
is_complete_complete	is_complete_request	✅	✅	-	✅	❌	✅	✅	⚠️	✅	✅	✅	✅	✅	⚠️	✅
is_complete_incomplete	is_complete_request	⚠️	✅	-	⚠️	❌	✅	✅	✅	⚠️	✅	⚠️	✅	✅	⚠️	⚠️
kernel_info_has_language_info	kernel_info_request	✅	✅	-	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅
kernel_info_has_protocol_version	kernel_info_request	✅	✅	-	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅
kernel_info_reply_valid	kernel_info_request	✅	✅	-	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅
kernel_startup	kernel_info_request	-	-	❌	-	-	-	-	-	-	-	-	-	-	-	-
parent_header_correlation	parent_header	✅	✅	-	✅	✅	✅	✅	❌	✅	✅	✅	✅	✅	✅	✅
rich_execute_result	execute_result	❌	✅	-	✅	⏭️	✅	✅	⏭️	⏭️	✅	⏭️	✅	✅	⏭️	⏭️
shutdown_reply	shutdown_request	❌	✅	-	✅	❌	✅	✅	❌	✅	✅	✅	✅	✅	✅	✅
status_busy_idle_lifecycle	status	❌	✅	-	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅
stdin_input_request	input_request	❌	✅	-	⏭️	❌	✅	✅	❌	✅	✅	✅	✅	✅	❌	⏭️
update_display_data	update_display_data	⚠️	⚠️	-	⏭️	⚠️	⏭️	✅	⏭️	✅	✅	⏭️	✅	⚠️	⏭️	⏭️

[rgbkrk]

Odd. https://github.com/runtimed/kernel-testbed/actions/runs/26427651852/job/79963087197?pr=87

Not sure where that came from. I'm going to merge this but you'll want to do a follow up PR.

[fleming79]

I think it looks like a timeout. Would it be possible to run the testbed locally and with logging outputs to see what it is waiting for?