mirror of
https://github.com/denoland/deno.git
synced 2025-07-31 00:54:18 +00:00
b7c2902c97
When `worker.terminate()` is called, the spec requires that the corresponding port message queue is emptied, so no messages can be received after the call, even if they were sent from the worker before it was terminated. The spec doesn't require this of `self.close()`, and since Deno uses different channels to send messages and to notify that the worker was closed, messages might still arrive after the worker is known to be closed, which are currently being dropped. This change fixes that. The fix involves two parts: one on the JS side and one on the Rust side. The JS side was using the `#terminated` flag to keep track of whether the worker is known to be closed, without distinguishing whether further messages should be dropped or not. This PR changes that flag to an enum `#state`, which can be one of `"RUNNING"`, `"CLOSED"` or `"TERMINATED"`. The Rust side was removing the `WorkerThread` struct from the workers table when a close control was received, regardless of whether there were any messages left to read, which made any subsequent calls to `op_host_recv_message` to return `Ok(None)`, as if there were no more mesasges. This change instead waits for both a close control and for the message channel's sender to be closed before the worker thread is removed from the table. |
||
|---|---|---|
| .. | ||
| 01_build.js | ||
| 01_errors.js | ||
| 01_version.js | ||
| 01_web_util.js | ||
| 06_util.js | ||
| 11_workers.js | ||
| 12_io.js | ||
| 13_buffer.js | ||
| 30_fs.js | ||
| 30_metrics.js | ||
| 30_os.js | ||
| 40_compiler_api.js | ||
| 40_diagnostics.js | ||
| 40_error_stack.js | ||
| 40_files.js | ||
| 40_fs_events.js | ||
| 40_http.js | ||
| 40_permissions.js | ||
| 40_process.js | ||
| 40_read_file.js | ||
| 40_signals.js | ||
| 40_testing.js | ||
| 40_tty.js | ||
| 40_write_file.js | ||
| 41_prompt.js | ||
| 90_deno_ns.js | ||
| 99_main.js | ||
| README.md | ||
Runtime JavaScript Code
This directory contains Deno runtime code written in plain JavaScript.
Each file is a plain, old script, not ES modules. The reason is that snapshotting ES modules is much harder, especially if one needs to manipulate global scope (like in case of Deno).
Each file is prefixed with a number, telling in which order scripts should be loaded into V8 isolate. This is temporary solution and we're striving not to require specific order (though it's not 100% obvious if that's feasible).
Deno Web APIs
This directory facilities Web APIs that are available in Deno.
Please note, that some implementations might not be completely aligned with specification.
Some Web APIs are using ops under the hood, eg. console, performance.
Implemented Web APIs
- Blob: for representing opaque binary data.
- Console: for logging purposes.
- CustomEvent,
EventTarget
and
EventListener:
to work with DOM events.
- Implementation notes: There is no DOM hierarchy in Deno, so there is no tree for Events to bubble/capture through.
- fetch, Request, Response, Body and Headers: modern Promise-based HTTP Request API.
- location and Location.
- FormData: access
to a
multipart/form-dataserialization. - Performance: retrieving current time with a high precision.
- setTimeout, setInterval, clearTimeout: scheduling callbacks in future and clearInterval.
- Stream for creating, composing, and consuming streams of data.
- URL and URLSearchParams: to construct and parse URLSs.
- Worker: executing
additional code in a separate thread.
- Implementation notes: Blob URLs are not supported, object ownership cannot be transferred, posted data is serialized to JSON instead of structured cloning.