You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
I want to report the following bug found while using defineProperty on Deno's built-in "Object":
Details:
Platform: macos x86_64
Version: Deno 1.43.3
============================================================
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.
thread 'main' panicked at /Users/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/deno_core-0.280.0/runtime/jsruntime.rs:1866:3:
internal error: entered unreachable code: Expected at least one stalled top-level await
stack backtrace:
0: _rust_begin_unwind
1: core::panicking::panic_fmt
2: deno_core::runtime::jsruntime::JsRuntime::poll_event_loop
3: deno_core::runtime::jsruntime::JsRuntime::run_event_loop::{{closure}}
4: deno_runtime::worker::MainWorker::run_event_loop::{{closure}}
5: deno::worker::CliMainWorker::run::{{closure}}
6: deno::tools::run::run_script::{{closure}}
7: deno::spawn_subcommand::{{closure}}
8: <deno_unsync::task::MaskFutureAsSend as core::future::future::Future>::poll
9: tokio::runtime::task::raw::poll
10: deno::main
note: Some details are omitted, run with RUST_BACKTRACE=full for a verbose backtrace.
How To Reproduce:
Run the following line of code to trigger Deno Panic:
$ target/debug/dcore /tmp/test.ts
🛑 deno_core binary is meant for development and testing purposes.
Run /tmp/test.ts
thread 'main' panicked at core/runtime/jsruntime.rs:1866:3:
internal error: entered unreachable code: Expected at least one stalled top-level await
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Fixes: #742Fixes: #743
`pending_mod_evaluation` is set before calling Module::Evaluate, and
unset in the promise handlers for the promise returned by evaluate. If
setting up those promise handlers fails for some reason, we can end up
in a case where evaluation has finished but we haven't unset
`pending_mod_evaluation`, which makes the core event loop assume that
there is a pending stalled tla message, and it ends up panicking.
Hi,
I want to report the following bug found while using
defineProperty
on Deno's built-in "Object":Details:
Platform: macos x86_64
Version: Deno 1.43.3
How To Reproduce:
Run the following line of code to trigger Deno Panic:
The text was updated successfully, but these errors were encountered: