deno 2.1.6 panics

[e-kwsm]

Describe the bug

Deno 2.1.6 has panicked.

Deno states that it is a bug in deno itself, but I’m not sure how to reproduce it without nvim, so am reporting here; deno task test gives 36 failures but messages seem different from that of nvim.
Thank you.

Provide a minimal vimrc with less than 50 lines to reproduce

Install deno 2.1.6 and clone denops under /tmp.

let g:denops#deno = '/tmp/deno-2.1.6'
set runtimepath+=/tmp/denops.vim

How to reproduce the problem from Vim startup

nvim -u minimal.vim

Expected behavior

Works without error.

Actual behavior

[denops] ============================================================
[denops] Deno has panicked. This is a bug in Deno. Please report this
[denops] at https://github.com/denoland/deno/issues/new.
[denops] If you can reliably reproduce this panic, include the
[denops] reproduction steps and re-run with the RUST_BACKTRACE=1 env
[denops] var set and include the backtrace in your report.
[denops] 
[denops] Platform: linux x86_64
[denops] Version: 2.1.6
[denops] Args: ["/tmp/deno-2.1.6", "run
[denops] ", "-q", "--no-lock", "-A", "/tmp/denops.vim/denops/@denops-private/cli.ts", "--quiet", "--identity", "--port", "0"]
[denops] 
[denops] thread 'worker-1' panicked at /home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/deno_core-0.330.0/gotham_state.rs:74:3:
[denops] required type deno_os::ops::signal::SignalState is not present in GothamState container
[denops] stack backtrace:
[denops]    0: rust_begin_unwind
[denops]    1: core::panicking::panic_fmt
[denops]    2: deno_core::gotham_state::missing
[denops]    3: deno_os::ops::signal::op_signal_bind::op_signal_bind::call
[denops]    4: deno_os::ops::signal::op_signal_bind::op_signal_bind::slow_function_impl
[denops]    5: deno_os::ops::signal::op_signal_bind::op_signal_bind::v8_fn_ptr
[denops]    6: Builtins_CallApiCallbackGeneric
[denops] note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
[denops] Server stopped (1). Restarting...
[denops] ============================================================
[denops] Deno has panicked. This is a bug in Deno. Please report this
[denops] at https://github.com/denoland/deno/issues/new.
[denops] If you can reliably reproduce this panic, include the
[denops] reproduction steps and re-run with the RUST_BACKTRACE=1 env
[denops] var set and include the backtrace in your report.
[denops] 
[denops] Platform: linux x86_64
[denops] Version: 2.1.6
[denops] Args: [
[denops] "/tmp/deno-2.1.6", "run", "-q", "--no-lock", "-A", "/tmp/denops.vim/denops/@denops-private/cli.ts", "--quiet", "--identity", "--port", "0"]
[denops] 
[denops] thread 'worker-1' panicked at /home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/deno_core-0.330.0/gotham_state.rs:74:3:
[denops] required type deno_os::ops::signal::SignalState is not present in GothamState container
[denops] stack backtrace:
[denops]    0: rust_begin_unwind
[denops]    1: core::panicking::panic_fmt
[denops]    2: deno_core::gotham_state::missing
[denops]    3: deno_os::ops::signal::op_signal_bind::op_signal_bind::call
[denops]    4: deno_os::ops::signal::op_signal_bind::op_signal_bind::slow_function_impl
[denops]    5: deno_os::ops::signal::op_signal_bind::op_signal_bind::v8_fn_ptr
[denops]    6: Builtins_CallApiCallbackGeneric
[denops] note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
[denops] Server stopped (1). Restarting...
[denops] ============================================================
[denops] Deno has panicked. This is a bug in Deno. Please report this
[denops] at https://github.com/denoland/deno/issues/new.
[denops] If you can reliably reproduce this panic, include the
[denops] reproduction steps and re-run with the RUST_BACKTRACE=1 env
[denops] var set and include the backtrace in your report.
[denops] 
[denops] Platform: linux x86_64
[denops] Version: 2.1.6
[denops] Args: 
[denops] ["/tmp/deno-2.1.6", "run", "-q", "--no-lock", "-A", "/tmp/denops.vim/denops/@denops-private/cli.ts", "--quiet", "--identity", "--port", "0"]
[denops] 
[denops] thread 'worker-1' panicked at /home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/deno_core-0.330.0/gotham_state.rs:74:3:
[denops] required type deno_os::ops::signal::SignalState is not present in GothamState container
[denops] stack backtrace:
[denops]    0: rust_begin_unwind
[denops]    1: core::panicking::panic_fmt
[denops]    2: deno_core::gotham_state::missing
[denops]    3: deno_os::ops::signal::op_signal_bind::op_signal_bind::call
[denops]    4: deno_os::ops::signal::op_signal_bind::op_signal_bind::slow_function_impl
[denops]    5: deno_os::ops::signal::op_signal_bind::op_signal_bind::v8_fn_ptr
[denops]    6: Builtins_CallApiCallbackGeneric
[denops] note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
[denops] Server stopped (1). Restarting...
[denops] ============================================================
[denops] Deno has panicked. This is a bug in Deno. Please report this
[denops] at https://github.com/denoland/deno/issues/new.
[denops] If you can reliably reproduce this panic, include the
[denops] reproduction steps and re-run with the RUST_BACKTRACE=1 env
[denops] var set and include the backtrace in your report.
[denops] 
[denops] Platform: linux x86_64
[denops] Version: 2.1.6
[denops] Args: 
[denops] ["/tmp/deno-2.1.6", "run", "-q", "--no-lock", "-A", "/tmp/denops.vim/denops/@denops-private/cli.ts", "--quiet", "--identity", "--port", "0"]
[denops] 
[denops] thread 'worker-1' panicked at /home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/deno_core-0.330.0/gotham_state.rs:74:3:
[denops] required type deno_os::ops::signal::SignalState is not present in GothamState container
[denops] stack backtrace:
[denops]    0: rust_begin_unwind
[denops]    1: core::panicking::panic_fmt
[denops]    2: deno_core::gotham_state::missing
[denops]    3: deno_os::ops::signal::op_signal_bind::op_signal_bind::call
[denops]    4: deno_os::ops::signal::op_signal_bind::op_signal_bind::slow_function_impl
[denops]    5: deno_os::ops::signal::op_signal_bind::op_signal_bind::v8_fn_ptr
[denops]    6: Builtins_CallApiCallbackGeneric
[denops] note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
[denops] Server stopped 4 times within 10000 millisec. Denops is disabled to avoid infinity restart loop.

Screenshots (if need)

Your environment

• OS: EndeavourOS
• Deno version: 2.1.6
• Vim/Neovim version: NVIM v0.11.0-dev-7c652242579b
• Denops version: 4ff8f35

Additional context

[Shougo]

Reproduced. But it is not denops bug.
It is deno bug instead. Please report it in deno issue.

[lambdalisue]

Workaround would be

deno upgrade 2.1.5

[lambdalisue]

I think this will be resolved when Deno 2.1.7 is released.

[e-kwsm]

I built the latest deno (denoland/deno@4e0bf4b) by myself and confirmed that the issue is fixed.
Thank you.

[Shougo]

Deno 2.1.7 is released and it works.