►
From YouTube: Node.js Diagnostics WG meeting August 11, 2021
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
B
B
Shall
we
point
the
to
the
ui
dev
tools,
documentation
or
write
it
by
ourselves,
because
the
the
dev
tools
documentation
for
enabling
enable
debugging
or
black
box
in
devtools
is
pretty
clear.
But
currently
it's
not
it's
not
updated.
So
it's
not
up
to
date.
B
I
have
opened
a
issue
there,
but
I
didn't
receive
any
reply
or
any
suggestion
to
make
appear.
So
I
think
that
it
could
take
some
time
and
perhaps
better
to
to
write
the
the
ui
documentation
by
ourselves.
So
I
just
want
to
to
know
from
from
you
guys.
What
is
that
the
best
approach
that
we
should
follow.
A
So
just
trying
to
understand
a
little
by
black
box
feature
what
we
mean
is
the
whole
of
the
node.js
core.
Apis
core
code
will
not
be
visible
by
default
when
we
actually
navigate
through
the
source
in
the
debug
mode.
A
There
there
could
be
ways
to
break
that
to
change
the
default,
but
the
the
current
current
behavior
is
not
according
to
that
expectation.
Is
that
the
problem
we
are
trying
to
address.
B
No,
it's
different.
It's
a
different
problem.
This,
the
the
this
problem,
is
about
how
to
document
how
to
make
a
tutorial
for
for
end
users
to
enable
the
black
box,
because
from
the
ui
is
pretty
simple,
but
by
cli
is
not
is
not
most
of
the
user
is
not.
You
know
is
not
aware
of
how
to
enable
it
passing
some
rejects
to
ignore
some
files,
the
cli
documentation,
the
tutorial
I
created,
but
the
ui.
I
tried
to
point
to
to
dev
tools,
documentation,
but
the
dev
tools.
A
B
Exactly
yeah
the
the
idea
is
just
to
create
a
tutorial
how
to
enable
the
black
box,
regardless
of
the
the
platform
like
ui
or
cli.
B
Yeah
I
just
asking,
because
I
I
was
thinking
to
so
in
our
documentation
when
we
will
talk
about
enabling
black
box
drug
with
ui.
We
will
just
redirect
the
user
to
dev
tools
documentation,
but
since
they
don't
answer
in
a
time
like
some
suggestion
to
make
a
prayer,
perhaps
better
to
write
in
this
document,.
A
Okay,
then,
moving
on
to
486,
which
is
inactive
branches.
Indirectly,
we
discussed
in
the
last
meeting
raphael
suggested
for
enabling
a
specific
option
called
automatically
delete
head
branches.
Thank
you
for
that.
I
have
enabled
that
in
the
project
settings
and
for
the
existing
stale
branches,
I
alerted
all
the
owners
who
have
created
these
steel
branches
and.
A
B
I
think
that
it
could
be
closed
right.
You,
you
haven't,
you
have
been
at
everyone
who
have
opened
branches,
but
I
think
mostly
are
okay
to
delete
no.
A
I
take
it
as
a
no,
so
that's
pretty
much
the
list
of
tagged
agenda
items
as
we
were
discussing
yesterday.
We
would
also
want
to
spend
some
time
discussing
on
the
best
practice
documentation
progress.
A
A
A
So
anything
else
on
that
front,
documentation
front
any
anything
else
that
we
missed
because
michael
wanted
to
switch
to
another
meeting,
and
we
did
we
did
not
have
enough
time.
So
were
there
any
topics
that
we
wanted
to
discuss
on
that
front,
any
pointers
or
anything.