►
From YouTube: Node.js Diagnostics WG Meeting - 2018-09-05
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
B
The
HTTP
is
case,
HTTP
the
use
cases
you
just
had
tweeted
about
it
a
couple
times
and
try
to
get
the
community
feedback,
but
it
doesn't
look
like
anyone's
said
anything
so
far,
not
too
sure
what
to
do
about
that.
A
B
A
D
E
A
Okay,
next
thing
is
Diagnostics
issue
q11.
This
is
just
best
practices
guide,
we're
just
talking
about
some
of
this,
which
is
that?
How
do
we
get
you
know?
Can
we
have
some
stuff
in
here
around
doing
leak,
analysis,
I,
don't
have
any
updates
here.
Despite
my,
you
know,
best
intentions.
Someone
was
on
the
call
last
time
he
wanted
to
get
involved.
I
never
know
what
his
name
was:
Michael
Mike,
maybe
from
no
source
yeah.
E
A
A
A
E
E
A
A
A
E
You
know
in
terms
of
some
of
the
others.
I
think
we
should
like
choose.
You
know
one
or
two
as
a
team
that
we
think
we
should
champion
and
then
figure
out.
You
know
look
at
we've
got
the
tiers,
it's
like
okay.
So
if
it's
unclassified,
what
do
we
have
to
do
to
actually
make
it
move
up
from
unclassified
to
one
of
the
upper
tiers.
A
So
is
there
something
that's
like
a
good
first
or
start
here?
Is
node
report
classified
as
something
that
in
in
one
of
these
they're
all
not
yet
classified
ones
right,
all,
not
yet
classified
yeah,
and
so
this
PR
that's
opening
node
report
should
have
something
that
moves.
That
up
is
that
right.
Well,.
E
You
know
at
least
move
it
up
to
two
three,
and
you
know
we
can
have
the
discussions
around
to
and
and
one
like,
we've
got
a
bunch
of
requirements,
so
we'd
have
to
go
through
and
say:
okay
have
we
met
all
those
requirements
right,
you
know,
so
some
of
them
are
like
the
two
must
be
heavily
dependent
upon.
So
you
know,
we'd
have
to
make
the
arguments,
but
the
first
one
would
be
like
okay,
Tier
three
we're
gonna
run
it
at
least
nightly.
E
F
F
C
E
E
A
B
A
D
B
D
G
A
A
A
So
we'll
see
how
that
shakes
out
over
the
next
I.
Don't
know,
I
think
what
we
were
shooting
for
was
that
we,
if,
if
it
makes
sense-
and
we
had
the
right
level
of
you-
know
at
least
support
that
there's-
we
would
get
it
as
tc39
proposal
and
we
would
do
that
for
the
September
meeting.
I,
don't
know
that
that's
gonna
get
done
given
a
September
5th
I,
don't
know
when
the
meeting
is
which
is
39
this
month
on,
but
it's
on
our
radar,
it's
not
at
the
top
of
the
stack
so.
A
E
H
E
A
Like
there's
a
bunch
of
check
boxes
here
and
I
think
some
of
them
are
like
can
go
away
and
I
think
some
of
them
need
to
be
updated.
Like,
for
example,
I
think.
A
couple
weeks
ago,
gang
was
talking
about
the
trace
event.
Buffer
implementation-
that's
used
currently
inside
a
node,
is
I.
Don't,
like
a
you
know,
a
toy
implementation
right.
Why
there's
a
number
of
stability
issues?
I,
don't
know
where
that's
being
tracked
at
what
we
need
to
do
is
get
sort
of
solid
implementation.
I
would
expect
that
would
get
tracked
here.
A
E
G
So
I
kept
been
working
on
it
off
and
on
I.
Think.
The
summary
that
one
mentioned
is
really
accurate.
The
JavaScript
API
is,
is
there
but
there's
an
implementation,
rough
edges,
especially
around
the
buffer
and
how
the
code
is
she
between
v8
and
and
node,
and
then
there
have
been
some
bugs
that
actually
have
been
fixing
in
meat
and
it's
just
a
long
process
to
get
them
back.
Ported
all
the
way
to
node,
so
so,
I,
I
and
I
think
the
issue
is
fairly
out-of-date.
G
There's
a
second
thing,
I've
been
discussing
with
the
VA
team
and
which
is
the
this
current
right
now.
The
way
the
implementation
is
shared
between
d8
and
node,
so
node
has
a
subclass.
It
overrides
some
of
the
functionality
in
v8,
but
the
process
for
fixing
a
bug
is
very
complicated
because
first,
you
have
to
fix
it
in
a
superclass
and
then
implement
some
related
fixes
in
subclass.
I.
G
I
think
there
are
some
bug
fixes
that
we
need
to
put
in
so
that
the
implementation
gets
functional
in
apps
to
be
useful.
It's
already
useful
just
that
there's
some
rough
edges,
the
public
API
shouldn't
change,
but
I
think
we
should
work
with
the
be
18
to
get
them
moved
over
to
this
library
that
we
can
just
use
and
provide.
Do
we
it
as
opposed
to
like
complicated,
build
system
that
we
currently
have
I'll
I
can
write
this
up
in
in
the
issue.
Okay,.
G
Right
right,
it's
yeah,
it's
it's
the
same
thing,
but
as
a
separate
library,
same
thing
from
a
user
interface
point
of
view,
the
the
macros
are
the
same.
So
it's
designed
to
be
a
replacement
of
the
tracing
mechanism
in
chrome,
okay,
yeah
I
would
encourage
people
to
take
a
look
at
the
federal
and,
let
me
know
if
you
have
any
thoughts
or
comments
on
you
on
this.
C
E
H
So
I'm
trying
to
find
a
a
new
way
to
analyze
card
ups,
Oh
No,
because
today,
both
ll
node
and
m
DB
basically
have
to
re-implement
some
of
the
v8
internals
to
be
able
to
inspect
Gardens,
and
this
is
in
the
heart,
and
it
also
makes
both
tools
very
hard
to
maintain.
For
example,
at
the
past
or
v
v8
upgrades
node
broke
and
we
had
to
go
through
commits
from
v8
and
try
to
find
out
what
change
then
what
we
have
to
change
on
note.
H
This
is
a
very
time-consuming
process
and
since
v8
already
knows
how
to
navigate
the
hip
I'm
trying
to
find
a
way
that
the
eight
can
help
the
bugger
to
navigate
it.
Instead
of
implementing
all
the
methods,
the
first
prototype
I
develop,
it
is
not
usable.
It
has
a
huge
performance
impact,
but
yang
suggested
another
approach
which
I'm
going
to
try
to
and
you're
going
to
see
if
it
works.
So.
E
I
E
H
To
find
something,
that's
usable
for
the
VA
team,
because
I
have
to
code
on
the
edge
sometimes
and
debugging
tools
or
working
or
if
it's
internals
is
I'm,
not
great
I
mean
you
have
to
use
LOD,
but
then
there
are
a
lot
of
cheat
code
and
basically
all
objects
are
accomplished
by
offset
and
not
using
C++
classes.
So
11
TB
doesn't
know
how
to
to
look
at
those
objects.
A
E
Done
that
for
Java
and
takes
some
interesting,
tooling
and
stuff
to
just
you
know,
generate
structures,
and
even
if
you
can
automatically
generate
a
lot
of
the
structures
from
the
code,
you're
all
you're
still
left
with
there's
usually
more
to
that
than
just
the
structures.
There's
like
algorithms.
You
have
to
understand
as
well
for
how
to
walk
between
structures
and
stuff
and
how
to
make
sense
and
those
you
often
end
up
having
to
have
duplicate
code
for.
E
A
A
Okay,
he's
got
everything
anything
else.