deno has panicked

[uriva]

============================================================
Deno has panicked. This is a bug in Deno. Please report this
at https://github.com/denoland/deno/issues/new.
If you can reliably reproduce this panic, include the
reproduction steps and re-run with the RUST_BACKTRACE=1 env
var set and include the backtrace in your report.

Platform: linux x86_64
Version: 2.1.4
Args: ["deno", "test", "-A", "src/parse.test.ts"]

thread 'main' panicked at cli/tsc/diagnostics.rs:219:57:
called `Option::unwrap()` on a `None` value
stack backtrace:
   0:     0x5cd7bc399cca - <std::sys::backtrace::BacktraceLock::print::DisplayBacktrace as core::fmt::Display>::fmt::h304520fd6a30aa07
   1:     0x5cd7bc3caf7b - core::fmt::write::hf5713710ce10ff22
   2:     0x5cd7bc3934d3 - std::io::Write::write_fmt::hda708db57927dacf
   3:     0x5cd7bc39b4d2 - std::panicking::default_hook::{{closure}}::he1ad87607d0c11c5
   4:     0x5cd7bc39b13e - std::panicking::default_hook::h81c8cd2e7c59ee33
   5:     0x5cd7bc9e9df4 - deno::setup_panic_hook::{{closure}}::hec8573ef9875d32a
   6:     0x5cd7bc39be02 - std::panicking::rust_panic_with_hook::had2118629c312a4a
   7:     0x5cd7bc39ba83 - std::panicking::begin_panic_handler::{{closure}}::h7fa5985d111bafa2
   8:     0x5cd7bc39a1a9 - std::sys::backtrace::__rust_end_short_backtrace::h704d151dbefa09c5
   9:     0x5cd7bc39b744 - rust_begin_unwind
  10:     0x5cd7bc3c7f33 - core::panicking::panic_fmt::h3eea515d05f7a35e
  11:     0x5cd7bc3c7fbc - core::panicking::panic::h102d65dbfa674afe
  12:     0x5cd7bc3c7e99 - core::option::unwrap_failed::hfd32652cc6017653
  13:     0x5cd7bc9ad2c7 - deno::tsc::diagnostics::Diagnostic::fmt_stack::h19edcfa9de95c91e
  14:     0x5cd7bc4dde32 - <&T as core::fmt::Display>::fmt::hfecaeb861da1d128
  15:     0x5cd7bc3caf7b - core::fmt::write::hf5713710ce10ff22
  16:     0x5cd7bc9ad5c4 - <deno::tsc::diagnostics::Diagnostics as core::fmt::Display>::fmt::hdb6540f6ea521097
  17:     0x5cd7bc3caf7b - core::fmt::write::hf5713710ce10ff22
  18:     0x5cd7be969c31 - anyhow::fmt::<impl anyhow::error::ErrorImpl>::debug::h6d5fa7b6b3c7ce29
  19:     0x5cd7bc3caf7b - core::fmt::write::hf5713710ce10ff22
  20:     0x5cd7bc3bf02b - alloc::fmt::format::format_inner::he4e5360ab424817d
  21:     0x5cd7bc5ca916 - alloc::fmt::format::h324d80325dc84573
  22:     0x5cd7bc9ea0df - deno::exit_for_error::h2ce6f2b239a13d55
  23:     0x5cd7bc9eb502 - deno::main::hc3e92832e49d991f
  24:     0x5cd7bc4ceba1 - std::sys::backtrace::__rust_begin_short_backtrace::h52a7b42c1177580b
  25:     0x5cd7bc4ce900 - std::rt::lang_start::{{closure}}::h40a6b50898982cd3
  26:     0x5cd7bc387c90 - std::rt::lang_start_internal::h4d90db0530245041
  27:     0x5cd7bca6d615 - main
  28:     0x7fde16229d90 - <unknown>
  29:     0x7fde16229e40 - __libc_start_main
  30:     0x5cd7bacde029 - _start
  31:                0x0 - <unknown>

[bartlomieju]

Can you please provide the code that caused this panic?

[uriva]

I'm afraid I don't have it anymore
I thought the debug command provided you with all needed information to debug
It was something related to a typing error

[marvinhagemeister]

I see. In that case I'll close it as we don't have enough information to proceed further. Feel free to open a new issue if you run into this again with the code snippet that caused it.