►
From YouTube: Node js Tracing WG Meeting 2015-11-19
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
Alright,
this
is
the
no
Jas
tracing
work
group
meeting
on
november
nineteenth
2015.
We
have
some
of
the
regulars
here
and
I
guess.
What
we'll
do
is
the
word
I
actually
did
go
through
the
kind
of
did
a
quick
review
yesterday
and
tried
to
get
some
agenda
items
up.
So
let's
go
through
those
just
roll
quick.
There
was
by
the
time
I
got
there.
A
Somebody
had
put
in
I
think
this
might
have
been
Andre
us
a
note
under
a
sink
wrap,
an
open
question
about
error
recovery
on
this
worth,
Chris
whoreson,
hate,
Orson
and
then
the
other
things
I
listed.
There
were
some
issues
that
were
open
up,
so
so
that's
good.
You
know
having
having
these
issues
opened
up
kind
of
gives
us
something
to
cut.
You
know
more
concretely
talked
about
so,
and
I
think
I
just
listed
all
of
them.
A
B
I
I
put
it
in
the
ad
india
sure
and
so
in
the
pews
racing
version
of
acing
rap
was
called
tracing.
That
was
like
some
air
handling
facilities
and
me
and
trevor
and
some
point
discuss
it
in
an
issue
or
regarding
something
else,
and
but
now
one
of
us
really
need
that
kind
of
error
handling.
So
it's
just
an
open
question.
This
is
something
we
want
to
implement
and
and
what
should
involve.
A
B
C
Present
the
original
purpose,
for
it
was
to
give
us
a
path
to
remove
domain
or
domains,
because
it's
totally
just
so,
but
we
need
a
mechanism
to
replace
it.
If
we're
going
for
remote
domains,
end
I
figured
this
would
be
a
good
place
for
it,
since
it
also
handles
that
kind
of
asynchronous
scenario.
The
problem
was
since
a
sand
crab
Forks
at
the
lower
level
there
were
places
where
it
missed,
because
domains
works
at
the
JavaScript's
stretch,
this
level
right
and
in
the
end
it
just
became
a
huge
mess.
A
A
That's
issue
29
async,
wrap
issues
da
chá
group,
you
alright,
so
moving
on
under
the
open
issues,
I
actually
listed,
one,
that's
under
the
node
foundation,
slides
the
slide
deck
for
the
node
foundation
has
a
list
of
all
the
or
some
of
the
working
groups
in
kind
of
a
brief
description.
So
I
had
kinda
put
something
up
there.
A
I'm
stephen
had
provided
a
kind
of
an
alternate
thing,
so
the
the
current
statement
that
we
would
have
for
for
this
tracing
work
group
is
mission,
is
to
provide
portable
tools
and
hooks
to
access
high-performance
tracing
capabilities
and
nodejs.
So
super
generic
doesn't
give
you
a
whole
lot
of
detail,
but
that's
fine,
because
everything
else
is
just
kind
of
a
one-sentence
thing.
A
I'm
going
to
go
with
that.
Unless
folks
have
any
other
issues
with
it,
and
so
we
can
forgot
some
real
quick
bring
it
up
now.
Otherwise
that
is
in
the
know,
Jas
foundation,
slides
repo.
It's
issue
number
seven,
there's
a
link
to
it.
The
github
are
in
the
google
doc
and
then
I'll
plan
on
I
guess
finalizing
that
PR
and
and
get
it
into
the
slides
all
right
all
right
now.
A
Okay,
so
now
we're
on
the
async
wrap
issues
from
andreas,
and
that
is
all
the
rest
of
these
are
in
the
tracing
work
group,
tracy
and
SW
GG
repo.
This
is
issued
29,
so,
like
I
said,
Andre
is's
has
done
a
good
job
of
creating
some
chunky
bits
here
and
some
kind
of
concrete.
That's
here
so
I
guess
once
you
maybe
you
can
just
give
us
a
quick
status
of
the
sundress
and.
B
Sure
yeah
so
I
guess
we
are
working,
multiplied
France.
So
that's
the
general
like.
Sometimes
we,
your
hair,
is
the
hanging
context,
so
we
don't
know
where
and
asynchronous
thing
arena
that's
from
and
then
trevor
has
actually
implemented.
One
of
the
events
is
called
the
understructure,
so
you
know
when
an
async
thing
stops
being
active.
Like
a
tease,
p
socket
is
closed
and,
yes
is
anything
more
than
I
mean
there's
still
this
urban
issue
about
whether
or
not
the
process
that
binding
should
be
deprecated.
B
So
if
that
happens,
then
asing
web
is
not
going
to
work
and
also
because
of
this
understructure,
a
feature
that
was
added
and
some
more
other
features
like
Nick
ID,
so
II
tasing
think
it's
an
ID
the
year.
Documentation
is
also
a
bit
out
of
date,
but
I
think
like
the
familiy
is
the
primary
issues
these
this
handle
context
as
missing.
So,
for
instance,
this
is
a
promise
issue
which
was
also
discussed
last
time.
B
C
So,
as
far
as
the
promise
thing,
it
was
just
v8
hasn't
given
any
response.
I,
don't
think
they're
much.
If
that's
going
to
happen
where
we
will
haven't,
contributed,
I
believe
I,
don't
see,
debate
team
having
much
interest
to
spend
time
doing
it
as
for
the
native
module
integration
feud
or
has
wanted
to
make.
D
D
A
A
There's
a
bunch
of
links
in
that
in
that
issue,
there's
a
bunch
of
links
back
in
the
know
Jas.
So
if
we
find
the
VA
tissue
for
that
one
that
you're
talking
about,
let's
go
ahead
and
just
reference
eyes.
It's
super
useful
to
have
these
links
in
here,
at
least
for
me.
So
that's
cool
and
I'll
just
mention
the
there
is
a
link
to
I
think
it's
the
same
thing
yeah!
It's
the
node
issues
669
for
the
on
error
that
we
had
mentioned
previously.
So
that's
that's
good!
A
So
it's
good
to
you
know
this
is
actually
I
kind
of
like
the
structure
of
how
we
have
you
done
this
and
under
eighth
of
the
you
know,
it's
a
bunch
of
items
and
they're
kind
of
trunked
in
that
in
a
useful
way.
So
you
know
at
least
gives
us
kind
of
a
view
of
work
that
has
to
has
to
be
done
and
that
perhaps
people
could
could
pick
off.
So
this
is
great
anything
else
on
on
this
particular
issue,
issue
29,
where
you
move
on.
A
Right
so,
let's
move
on
to
30
and
that
one
is
trace
underscore
of
NH
tracking
issue,
and
this
was
created
by
Stephen
and
the
the
gist
of
here
as
near
as
I
can
tell.
Is
that
let's
get
the
trace
of
nth
stuff
in
to
node
and
so
there's
some
discussion
of
sort
of
how
we
should
do
that
and
I
guess
Steven
it
or
somebody
else
minutes
to
provide
some
additional
update
on
that.
That
would
be
good,
I.
E
Had
not
really
any
updates
on
my
parts.
I
mostly
just
put
this
together
as
a
tracking
issue.
I
might
try
and
get
on
to
doing
something
about
this
stuff
myself
at
some
point,
but
just
haven't
got
to
it
yet.
A
Cool
good
enough,
it's
nice
to
have
it
at
least
tracked
in
here
so
yeah
I,
guess
if
we
can
find
somebody
to
actually
take
a
whack
at
this
would
be
it
would
be
cool.
Since
you
know
I
suspect
everybody
can
has
a
general
idea
of
how
this
thing
is
going
to
work,
but
actually
seeing
a
code.
It'll
be
super
useful.
Even
if
it's
not,
you
know
complete
just
to
start
to
get
a
sense
of
it.
So
maybe,
if
I
have
some
free
time,
I
I
might
take
a
look.
D
Learned
a
quick
update
on
the
on
the
least
I.
Don't
press
event
is
so
there
been
a
lot
of
changes
that
have
gone
into
the
CL
and
a
for
landing
trace
event
into
v8.
There
were
some
design
changes
that
the
via
team
wanted
and
all
the
things
that
were
needed,
so
lots
of
activity
has
happened
to
it
and
there
should
be
a
lot
of
issues
you
might
have
seen
on
the
v8.
The
previews
nameless
for
this,
but
yeah
it's
being
actively
worked
on.
We
hope
to
get
this
line
in
to
be
its
own
ish.
A
D
To
live
in
lots
of
coding
changes
recently
yeah,
so
we're
working
through
the
issues
that
we
need
to
resolve
and
when
I
say,
if
V
I
mean
Fadi
in
his
team
to
get
this
line,
meaning
to
be
it
great.
D
A
Is
a
link
to
chromium
code
review?
That's
okay!
It's
created
eight
months
ago,
I'm
looking
at
right!
Now,
I'm
sorry!
It's
in
that
issue,
30
of
the
tracing
work
group,
but
it's
a
linked
into
a
chromium
code
review
and
I
was
opened
eight
months
ago,
but
modified
last
eight
hours
ago.
So
I
assume
this
may
be
kind
of
the
most
relevant
thing
for
people
to
watch.
A
Yeah,
let's
see
follow
me
listed
on
there
as
well
as
been
in
some
discussion:
great
okay,
let's,
let's
move
on
issue,
31
tracing
use
cases
in
interface,
so.
A
Luca
had
created
this
one
and
is
not
on
I.
Think
I
really
wanted
to
get
I
can't
remember
full
name,
but
you
you
non
or
you
own,
had
had
thinking.
I
think
he
works
at
Netflix
had
specifically
mentioned,
like
wanting
to
have
a
continuous
tracing
interface
and
so
I
thought
that
would
actually
kind
of
be
good
to
kind
of
outline
as
one
of
them.
But
I
don't
see
that
in
here.
So
this
perhaps
this.
A
A
A
So
this
I'm
sorry,
it's
issue,
34
LTT,
ng
tracing
improvements,
so
this
doesn't
have
anything
to
do
with
the
be
the
new
tracing
stuff
coming
into
VA
near
as
I
can
tell.
This
is
more
somebody
who
wants
to
improve
the
existing
ltte,
ng
trace
points
and
there's
actually
some
discussion
about
why
some
of
those
those
trace
points
or
probes,
whatever
you
my
column,
are
the
way
they
are
so
this
one
isn't.
This
is
sort
of
more
of
a
I
see.
This
is
more
of
a
current
issue
and
probably.
A
Is
the
background
here
may
be
relevant
for
where
we
end
up
putting
trace
probes
eventually
into
node
and
why
we
would
put
them
in
certain
places,
but
we
haven't
quite
gotten
there.
I
guess.
Maybe
that's
that's
another
issue
that
we
could
actually
kind
of
open
up
and
have
some
discussion
about.
Is
what
sort
of
trace
points
probes.
A
Whatever
do
we
actually
want
to
put
in
because
I
don't
know
that
we've
really
had
that
much
of
a
discussion
of
that,
but
we
might
as
well
go
ahead
and
start
listing
those
and
we
can
get
people
at
least
thinking
about
all
right,
so
that
was
it
for
the
current
open
issues.
I
guess
I
I
love
to
continue
to
kind
of
work.
A
A
A
A
All
right,
you
have
spoken
I'm
going
to.
Let
you
all
go
so
thanks
for
everyone
or
for
making
the
call,
hopefully
we'll
get
a
little
more
activity
in
the
actual
sort
of
content.
We're
going
down
I'll,
do
a
a
minutes
and
maybe
I'll
try
to
kind
of
outline,
or
I
think
people
were
looking
to
contribute
places.
They
could
start
poking
around
and
we'll
see
you
all
in
january.
I
did
just
get
a
question:
Jeff
Lewis,
so.