►
From YouTube: Node.js Diagnostics WG Meeting - 2018--06-27
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
You
know
I,
don't
know
what
to
make
of
this
I
kind
of
just
feel
like
we
should
just
let
you
know
if
things
materialize,
then
it
materializes.
If
not,
then
it
doesn't
and
I
kind
of
feel
like
that's
what
we
should
do.
I
don't
know.
If
anybody
has
any
other
comments
there.
It
sounds
pretty
scattershot,
though
yeah.
C
A
D
B
E
A
I
agree:
I
mean
we
can
certainly
come
up
with
an
agenda.
I,
don't
know
that
everybody's
schedule
is
gonna
work
I,
don't
know
that
I
feel
like
cat
herding,
people's
schedules
and
that,
but
again,
I
think
it's
like.
We
should
see
if
there's,
if
there's
a
slot
that
works
during
the
conference
as
we
can
get
together
and
talk
about
these,
you
know
things
in
a
more
formal
setting.
A
I
think
that's
great
I'm
gonna
be
there,
and
you
know
I'm
in
particular,
I
wanted
to
talk
about
some
of
this
Aysen
contact
stuff
and
do
any
face-to-face
conversations
that
I
need
to
do
to
just
sort
of
explain
any
of
this
stuff
with
anybody.
So
and
that's
kind
of
my
primary
goal
for
being
there
so
I'll
be
available
for
that.
I
suspect
that
other
people
are
gonna
have
specific
agendas
that
they
want
to
drive.
I.
Imagine
like
you
know,
I'm,
just
gonna.
A
A
A
A
A
A
A
Like
there's
an
azure
team,
that's
doing
something
and
somebody
comes
up
with
hey.
We
should
plug
in
on
XYZ
and
somehow
I
get
looped
in
on
the
thread
and
I'm
like
hey.
This
is
kind
of
where
we're
thinking
about
things
right,
which
has
been
what
we've
described
in
that
issue.
180
on
and
you
know,
and
usually
these
are
different
product
teams
that
have
some
need
for
it
right
so
and
I'd
then
I
try
and
you
know
pitch
them,
hey
if
you
want
to
get
involved.
A
B
A
It's
like
they
have
more
immediate
concern,
right,
yeah
and-
and
it's
like
you
know,
unless
somebody's
actually
tasked
to
be
like
hey,
we
need
to
nail
this
for
node
and
we
want
to
do
it
in
a
way
that
you
know
we
want
to.
We
want
to
make
an
investment
that
we
can
sort
of.
You
know
their
cruise
to
a
bunch
of
other
things,
and
you
know
there's
also
a
contribution
back
into
the
community
right,
it's
kind
of
hard
to
get.
You
know
time
to
do
that
kind
of
stuff.
E
A
I
agree
and
we've
got
a
bed
on
open
sense
as
well
and
I
believe
that
it's
like
we've
got
folks
on
our
end.
Talking
to
folks
on
your
end,
at
Google,
about
this
and
I
know
that
you
know
like
we
were
in
one
meeting
where
they're
you
know
they
were
talking
about
Java
org.net
support,
I,
think
node
came
up
briefly.
A
So
if
you
are
making
progress
with
open
sin
to
some
node
like
ping
me
because
I
know
that
there's
people
that
are
specifically
interested
in
that
and
you
know
but
trying
to
align
or
trying
to
sell
them
that
you
know
hey
this,
you
know
Diagnostics
channel,
enables
open
census
in
a
more
scalable
insane
way.
A
F
F
A
A
I
mean
I
think
the
the
the
use
case
as
I
understand
it
is
you
have
a
cloud
application
that
is
comprised
of
multiple
services
and
what
you
need
to
be
able
to
do
is
you
need
to
be
able
to
correlate
log
data
across
multiple
services
and
open
census
provides?
Is
a
mechanism
to
sort
of
do
that?
Correlation
and
Calvin
correct
me
if
this
is
wrong,
yeah.
F
F
But
the
idea
is
having
an
open
standard
in
the
form
of
open
census,
the
standard
and
also
open
libraries
that
are
available
for
every
language,
all
right
that
are
yeah.
So
there's
a
spec
opposite
respect
that
they're
on
the
github
repo
they're,
a
given
organization
called
open
census,
and
then
there's
also
concrete
in
and
Asian's
available
for
rias
languages
right.
B
C
A
Yeah
and
I
believe
that
you
guys
are
trying
like
Google
is
making
a
bet
on.
It
is
sort
of
the
de-facto
tracing
stuff
and
I'm
I
believe
as
sure
as
well,
so
that
most
services,
mr.
Nasser,
will
eventually
produce
messaging
data
consistent
in
this
format.
So
there
seems
to
be
some
and
I
don't
know
if
Amazon's
hook
like
if
they're
signed
up
as
well.
A
Okay,
so
the
diagnostic
deep
dives
know
up,
they
have
I
do
want
to
schedule
one.
Maybe
after
the
summit
on
you
know
for
the
async
contact,
stuff,
I.
Think
there's
you
know,
as
we
discussed
previously
there's
a
few,
probably
one-on-one
conversations
that
need
to
happen
to
just
start
bringing
people
up
to
speed
on
some
of
that
stuff.
I,
don't
think,
there's
any
other
updates.
There.
D
B
A
A
F
No
update
so
as
far
as
stable
API
I
think
that
one
is
fairly
far
off
at
the
discussed
at
the
collaborator
summit
but
map.
But
that
may
be
a
moot
point
anyway,
because
people
are
using
it,
but
from
from
from
the
things
that
are
happening
perspective,
a
thing
cooks,
there's
a
there's,
a
pull
request
that
Matteo
open.
That
I
think
is
currently
blocked,
which
is
a
good
current
resource.
And
then
there
is
another
one
get
active
handles
that
Jeremiah
opened
the
plate.
A
Okay,
okay,
so
the
async
context,
formalization
stuff,
so
there's
a
PR
I
did
an
update
to
the
PR
I
added
some
examples
for
generator
functions
and
I
added
an
example.
Simple
example
for
async
await
I
believe
everything
still
holds
like
after
you
go
through
that
DFC
Kuwait
stuff
gets
a
little
complex.
A
You
know,
I
think
the
best
way
to
sort
of
explain
that
or
think
through
that
in
terms
of
what's
happening,
is
looking
at
what
the
spec
says
and
then
translating
the
async/await
syntax
into
the
actual
promise
operations,
as
defined
by
the
current
atmospheric
spec
and
then
just
sort
of
looking
at
where
these
various
transitions
happen
on
and
I
still
think.
Generally
things
hold
in
going
through
the
staff.
A
I
think
that
it's
becoming
I
think
pretty
clear
to
me
that
what
I've
gone
in
the
dog
maps
pretty
nicely
into
the
spec,
and
that
is
I,
think
there's
a
few
places
inside
of
the
ACMA
script
spec,
where
we
need
to
go
in
and
modify
some
definitions
and
add
some
things.
They
already
have
a
concept
of
what
they
call
an
execution
context
in
FM
script,
spec
that
is
effectively
a
stack
frame
and
so
I
think
there's
some
update
to
that
to
say
like
hey,
there
is
an
execution
context
and
then
we've
got
this.
A
A
F
Can
give
an
update
on
this
one?
So
there's
a
few
things
happening
on
on
this
one.
He
is
working
on
a
change
in
v8,
which
adds
some
intrinsics
to
be
it
that
that
will
let
us
check
if
a
trace
of
category
is
enabled
and
do
a
trace
from
JavaScript,
so
that
basically
an
evil
tracing
to
be
exposed
to
javascript
in
a
performant
way.
I
think
he's
currently
working
through
issues
on
on
that
v8
change
on
unknown
itself.
F
So
the
other
point
I
think
there
is
some
roughness
around
the
edges
that
I'm
hoping
that
we
can
resolve
and
I'm
working
on
it
and
love
you
and
you
team,
is
also
working
right
and
then
there's
some
follow-on
changes
around
metadata
events
that
I
want
to
put
in.
So
this
work
happening
and
the
objective
I
have
is
that
maybe
we
can
wrap
this
up
in
time
for
node
level.
F
A
F
A
F
A
A
B
D
F
So
the
so,
if
you
want
to
reproduce
the
issue,
is
the
notice
issued
21
3,
3
5?
So
that's
the
patch.
You
want
that
basically
fixes
the
shutdown
choreography
bug,
so
it's
not
actually
fixes
shut
down
like
pointers.
Getting
really
out
of
order
on
that
progressed
itself
leads
to
more
crashes
that
are
hard
to
be
in
how
to
debug.
It
is
121
335.
So.
A
F
A
A
Okay,
anything
else
from
anybody.