1. 12 8月, 2020 1 次提交
  2. 15 7月, 2020 1 次提交
  3. 02 6月, 2020 1 次提交
  4. 30 5月, 2020 1 次提交
  5. 23 4月, 2020 1 次提交
  6. 20 4月, 2020 1 次提交
  7. 10 4月, 2020 1 次提交
  8. 04 4月, 2020 1 次提交
  9. 25 2月, 2020 1 次提交
  10. 24 2月, 2020 1 次提交
    • B
      refactor: use OpError instead of ErrBox for errors in ops (#4058) · 4e1abb4f
      Bartek Iwańczuk 提交于
      To better reflect changes in error types in JS from #3662 this PR changes 
      default error type used in ops from "ErrBox" to "OpError".
      
      "OpError" is a type that can be sent over to JSON; it has all 
      information needed to construct error in JavaScript. That
      made "GetErrorKind" trait useless and so it was removed altogether.
      
      To provide compatibility with previous use of "ErrBox" an implementation of
      "From<ErrBox> for OpError" was added, however, it is an escape hatch and
      ops implementors should strive to use "OpError" directly.
      4e1abb4f
  11. 11 2月, 2020 1 次提交
    • B
      workers: basic event loop (#3828) · 79b3bc05
      Bartek Iwańczuk 提交于
      * establish basic event loop for workers
      * make "self.close()" inside worker
      * remove "runWorkerMessageLoop() - instead manually call global function 
        in Rust when message arrives. This is done in preparation for structured clone
      * refactor "WorkerChannel" and use distinct structs for internal 
        and external channels;  "WorkerChannelsInternal" and "WorkerHandle"
      * move "State.worker_channels_internal" to "Worker.internal_channels"
      * add "WorkerEvent" enum for child->host communication; 
        currently "Message(Buf)" and  "Error(ErrBox)" variants are supported
      * add tests for nested workers
      * add tests for worker throwing error on startup
      79b3bc05
  12. 09 2月, 2020 1 次提交
  13. 05 2月, 2020 1 次提交
  14. 04 2月, 2020 1 次提交
    • R
      refactor: Use Tokio's single-threaded runtime (#3844) · 161cf7cd
      Ryan Dahl 提交于
      This change simplifies how we execute V8. Previously V8 Isolates jumped
      around threads every time they were woken up. This was overly complex and
      potentially hurting performance in a myriad ways. Now isolates run on
      their own dedicated thread and never move.
      
      - blocking_json spawns a thread and does not use a thread pool
      - op_host_poll_worker and op_host_resume_worker are non-operational
      - removes Worker::get_message and Worker::post_message
      - ThreadSafeState::workers table contains WorkerChannel entries instead
        of actual Worker instances.
      - MainWorker and CompilerWorker are no longer Futures.
      - The multi-threaded version of deno_core_http_bench was removed.
      - AyncOps no longer need to be Send + Sync
      
      This PR is very large and several tests were disabled to speed
      integration:
      - installer_test_local_module_run
      - installer_test_remote_module_run
      - _015_duplicate_parallel_import
      - _026_workers
      161cf7cd
  15. 25 1月, 2020 1 次提交
  16. 22 1月, 2020 1 次提交
  17. 21 1月, 2020 1 次提交
    • B
      refactor: split worker and worker host logic (#3722) · 7966bf14
      Bartek Iwańczuk 提交于
      * split ops/worker.rs into ops/worker_host.rs and ops/web_worker.rs
      
      * refactor js/workers.ts and factor out js/worker_main.ts - entry point for WebWorker runtime
      
      * BREAKING CHANGE: remove support for blob: URL in Worker
      
      * BREAKING CHANGE: remove Deno namespace support and noDenoNamespace option in Worker constructor
      
      * introduce WebWorker struct which is a stripped down version of cli::Worker
      7966bf14