delta/node-new.git/src/node_platform.h, branch try_Python3_on_macOS

src: unimplement deprecated v8-platform methods

2019-05-30T13:51:37+00:00

This removes the implementations of NodePlatform::CallOnForegroundThread
and NodePlatform::CallDelayedOnForegroundThread and updates the
test_platform cctest to stop using them.

PR-URL: https://github.com/nodejs/node/pull/27872
Reviewed-By: Gus Caplan 
Reviewed-By: Refael Ackermann 
Reviewed-By: Rich Trott 
Reviewed-By: Anna Henningsen 
Reviewed-By: Colin Ihrig

src: apply clang-tidy rule modernize-use-equals-default

2019-04-24T17:32:43+00:00

PR-URL: https://github.com/nodejs/node/pull/27264
Reviewed-By: Refael Ackermann

src: enable non-nestable V8 platform tasks

2019-04-18T10:50:52+00:00

We never execute tasks in a nested fashion, so enabling them should
be as simple as forwarding tasks to the existing `Post*` methods.

PR-URL: https://github.com/nodejs/node/pull/27252
Reviewed-By: Ben Noordhuis 
Reviewed-By: James M Snell 
Reviewed-By: Daniel Bevenius

src: clean up MultiIsolatePlatform interface

2019-03-13T00:12:56+00:00

- Since this was introduced, V8 has effectively started requiring
  that the platform knows of the `Isolate*` before we (or an embedder)
  create our `IsolateData` structure; therefore, (un)registering it
  from the `IsolateData` constructor/destructor doesn’t make much
  sense anymore.
- Instead, we can require that the register/unregister functions
  are only called once, simplifying the implementation a bit.
- Add a callback that we can use to know when the platform has
  cleaned up its resources associated with a given `Isolate`.
  In particular, this means that in the Worker code, we don’t need
  to rely on what are essentially guesses about the number of event
  loop turns that we need in order to have everything cleaned up.

PR-URL: https://github.com/nodejs/node/pull/26384
Reviewed-By: Daniel Bevenius 
Reviewed-By: James M Snell 
Reviewed-By: Matteo Collina 
Reviewed-By: Joyee Cheung

src: extra-semi warning in node_platform.h

2019-03-04T01:37:37+00:00

https://clang.llvm.org/docs/DiagnosticsReference.html#wextra-semi

PR-URL: https://github.com/nodejs/node/pull/26330
Reviewed-By: Anna Henningsen 
Reviewed-By: James M Snell 
Reviewed-By: Colin Ihrig 
Reviewed-By: Luigi Pinca 
Reviewed-By: Beth Griggs 
Reviewed-By: Ruben Bridgewater

src: apply clang-tidy rule modernize-use-override

2019-02-18T04:43:22+00:00

PR-URL: https://github.com/nodejs/node/pull/26103
Reviewed-By: James M Snell 
Reviewed-By: Anna Henningsen

src: reduce platform worker barrier lifetime

2018-10-13T05:30:53+00:00

Minor cleanup in the lifetime for the platform worker initialization
synchronization barrier.

PR-URL: https://github.com/nodejs/node/pull/23419
Reviewed-By: Anna Henningsen 
Reviewed-By: Benjamin Gruenbaum 
Reviewed-By: Sakthipriyan Vairamani 
Reviewed-By: Ben Noordhuis 
Reviewed-By: James M Snell 
Reviewed-By: Denys Otrishko 
Reviewed-By: Colin Ihrig

src: trace_event: secondary storage for metadata

2018-10-12T21:12:31+00:00

Metadata trace-events should be held in secondary storage so that they
can be periodically reemitted. This change establishes the secondary
storage and ensures that events are reemitted on each flush.

PR-URL: https://github.com/nodejs/node/pull/20900
Reviewed-By: James M Snell 
Reviewed-By: Anna Henningsen

trace_events: destroy platform before tracing

2018-10-06T13:05:17+00:00

For safer shutdown, we should destroy the platform – and background
threads - before the tracing infrastructure is destroyed. This change
fixes the relative order of NodePlatform disposition and the tracing
agent shutting down. This matches the nesting order for startup.

Make the tracing agent own the tracing controller instead of platform
to match the above.

Fixes: https://github.com/nodejs/node/issues/22865

PR-URL: https://github.com/nodejs/node/pull/22938
Reviewed-By: Eugene Ostroukhov 
Reviewed-By: James M Snell 
Reviewed-By: Matteo Collina

src: ready background workers before bootstrap

2018-10-06T04:31:09+00:00

Make sure background workers are ready before proceeding with the
bootstrap or post-bootstrap execution of any code that may trigger
`process.exit()`.

Fixes: https://github.com/nodejs/node/issues/23065

PR-URL: https://github.com/nodejs/node/pull/23233
Reviewed-By: James M Snell 
Reviewed-By: Anna Henningsen