►
From YouTube: 2022-09-20 - Diagnostics WG meeting
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
A
A
No
okay
by
the
way,
just
said
that
in
the
chat,
the
minutes-
so
please
add
your
name
there
going
to
the
directly
to
our
list.
We
have
the
issue.
A
Five,
eight
three
discuss
possible
agenda
items
for
the
collab
Summit
I
think
that
we
can
remove
it
from
the
agenda
because
we
have
already
defined
it.
What
we
are
going
to
discuss
so
yeah
I
think
Stephen
submitted
the
proposal,
so
all
good
hope
to
see
everybody
there
and
I
will
remove
the
agenda.
Okay
and
also
close
the
issue,
because
it's
done.
A
Great
going
to
the
next
item,
the
LL
node
current
status,
the
issue
576,
please
Anton,
can
you
give
some
feedback.
B
Yeah,
just
let
me
spin
this
up
yeah
so
release
Spore
version,
16
version
8
from
Ken,
so
happy
enough
with
that
we
lost
I.
Think
the
key
aspect
of
that
release
is
we
lost
the
rudimentary
support
that
we
had
for
promises.
B
Don't
know,
what's
involved
in
reinstating
that
at
the
moment,
so
just
just
calling
that
out
put
everything
else
and
sort
of
minor
minor
drops
in
a
couple
of
tests,
but
not
nothing
huge
I,
think
the
promises
and
with
really
the
really
the
big
one
need
to
write
up
the
write
that
up
and
then
we
also
I
think,
judging
by
some
of
the
work
that
Tony
has
done,
I'm
on
Mac
I
think
we've
lost
support
for
some
architectures
as
well.
B
I
think
we've
lost
support,
Prime
we've
probably
lost
support
for
arrests,
390
and
and
power
as
well.
So
I,
don't
know
Michael
what
the
view
is
on
that
because
they're
they're
IBM
architectures,
but
just
a
heads
up,
but
the
action
is
to
write
that
up
and
then
do
a
blog
post
on
it.
Basically
that
still
outstanding
so.
B
Don't
know
need
some
investigation,
but
my
hunch
is
that
we
will
have.
A
B
Like
I
said,
the
big
one
that
I'm
calling
out
is
is
promises,
but
there's
probably
other
things
in
there,
but
I'm
just
flagging
it
that
there's
okay,
that
might
be
a
thing
yeah,
okay,
yep
good
to
know
yeah
and
yes,
part
of
that.
Then
there's
the
announcement
to
reestablishing
the
tool
tier
list
I
think
we
should
have
that
support
features.
What
we
have
today
lined
up
and
then
we
can.
We
can
do
an
announcement
in
terms
of
what
we
have
for
the
hard
yards
in
terms
of
getting
a
build
that
passes.
B
Tests
on
16
and
18
is
out
there.
Okay,
so
I
was
planning
to
automate
the
deployment
but
I'm
not
sure
I'm,
not
sure
how
that
will
play
into
the
signing
and
verification
process.
So
I
noticed
that
Mary
was
the
previous
releases
were
all
signed.
I,
don't
know
how
release.
Please
will
work
with
that
so,
rather
than
hold
back
the
release,
I
I
did
it
manually
and
assigned,
but
I've
done
them
manually,
but
we
can
distill
a
ticket
open
for
that
and
we
can
pick
it
up
again.
Yeah.
B
A
B
Okay,
14
16
and
18
yeah
and
we
dropped
so
what
I
did
actually
what
I
should
have
mentioned
as
well
for
8,
10,
12
and
14.
I
did
a
release
3.3.0,
which
was
compatible
with
llvm
8
to
14
and
release
that
as
an
as
a
3.3.0
and
tagged
it
and
then
the
day
after
I
published
4.0,
which
is
14,
16
and
18..
B
So
if
people
need
if
people
need
all
the
unsupported
versions
of
node,
for
whatever
reason,
we
have
a
build
there,
that
has
better
llvm
integration,
but
it's
not
going
to
be
supported,
but
we're
not
good.
A
B
A
A
B
A
Yeah
we
have
an
issue
open,
they
show
571,
that
is
alternatives
to
LL
node,
so
I
believe
that
once
actually
Ellen
know
this
officially
supported.
Actually
we
need
also.
We
have
another
action
that
is
in
your
diagnostic,
tooling,
support,
tiers
or
something
like
that.
We
need
to
bring
back
our
node
against,
but.
B
A
B
There
is
a
debug
tool
that
comes
the
V8
team
have
released
that
we
could
possibly
look
to
to
leverage
instead
of
having
the
problems
with
all
the
symbols
changing
all
the
time.
There's
there's
a
lot
of
work
to
do
there
and
I
was
hoping
to
capture
it
as
part
of
the
collaboration
Summit.
There's
no
plan
immediately
in
place
to
look
at
developing
that,
but
it's
not
I
think
initially
it
was
the
conversation
there
was.
Are
we
going
to
do
that?
B
Rather
than
get
six
get
16
and
18
support
up
in
the
current
code
base,
and
we
made
the
choice,
okay
and
basically
made
the
choice
and
said
yeah?
Do
you
know
it's
probably
not
that
much
of
a
lift
to
get
what
we
have
to
16
and
18
and
then
do
and
integrate
the
diagnostic
report
as
part
of
sorry,
not
diagnostic
report,
the
debug
helper
sorry
wrong
wrong
tool,
so
debug
helper
to
integrate
our
LL
node
into
into
debug
helper,
which
is
the
V8
library
or
component.
A
Okay,
okay,
so
it's
fair
to
rename
the
issue
to
including
the
book
helper
to
LL
node
instead
of
alternatives.
B
A
Okay,
so
yeah
I'm,
not
a
part
of
that.
So
what
is
the
action
that
these
this
issue
would
require
it's
something
from
V8
side
or
we
need
to
do
something
in
the
LL
node.
B
So
we
need
to
understand
the
Gap
analysis
between
what
currently
debug
helper
gives
us
the
capabilities
in
LL
node
and
what
we
need
to
do.
Okay,
so
the
guts
of
it
in
terms
of
the
object,
my
understanding
is
and
I
haven't
looked
at
this
closely,
but
medicine
is
the
the
there's
a
reasonable
amount
of
the
object
identification
in,
but
there's
all
the
sort
of
find
objects,
blah
blah,
etc,
etc.
B
All
the
utilities
that
we
have
in
LL
node
isn't
included
in
that
or
needs
to
be
wrapped
or
augmented
in
there,
and
so
we
can
have
the
same
capabilities,
not
a
clue.
What's
involved
in
that
at
all,
and
given
the
like
say,
given
the
fact
of
that,
we
didn't
know,
and
we
did
know
what
work
was.
On
the
other
side,
we
decided
to,
we
decided
to
just
keep
the
architecture
of
the
ears
and
the
implementation
as
it
is,
but
this
is
basically
open
for
anybody
who
wants
to
have
a
go.
I.
B
Think
what
we're
saying
is.
We
were
interested
in
accepting
this
I
think
when
Kane
put
the
initially
paid
hard
this
initially
opened
up.
The
issue
he
wanted
to
have
is
this
something
we're
interested
in
doing
or
not
type
conversation
and
I.
Think
where
we
landed
is
that
yeah?
It
probably
is
something
that
we
want
to
land
on
and
so
I
think
that
that's
definitely
one
one
decision.
Point
that's
been
made
around
this,
but
in
terms
of
actual
work,
nothing.
A
Okay,
so
I
will
remove
the
label
the
egg
agenda
because
we
have
already
discussed
we
have
also
you
understand.
We
have
to
understand
that
this
is
a
good
feature
indeed,
so
yeah
I
will
include
the
label,
onions
mentor
and
that's
it.
So
let
me
comment
there.
A
C
A
Yes,
anybody
wants
all
right.
Click
on
that.
D
A
Amazing,
okay,
the
next
one
is
re-evaluate,
ebpf
tracing
tool
list
yeah
this
one
I
I
took
the
lead
to
to
move
one
with
it
and
yes
that
we
we
did
a
good
progress.
I
have
a
proposal.
A
Actually,
we
I
have
a
an
open
issue
to
discuss
to
bring
the
support
back,
but
I
still
need
to
do
some
research,
because
it's
not
just
actually
it's
not
just
me
I'm
waiting
for
some
answers,
and
perhaps
Michael
can
also
provides
some
feedback
that
the
problem,
the
the
trade
support,
was
dropped
because
frequently
it
was
stacking.
A
The
the
build
and
the
maintenance
for
that
was
was
not
something
acceptable
at
some
point,
because
nobody
seems
to
use
it
like
for
different
factor
for
different
reasons,
but
we
are
in
terrorists
interested
in
bringing
the
support
back,
but
before
I.
Before
doing
that,
we
need
to
understand
what
what
is
what
is
the
pain
points
of
making
this
or
bringing
the
support
the
trace
back?
So
one
of
them
is
the
maintenance,
but
what
we
still
need
to
know
what
kind
of
maintenance
is
it
like?
A?
A
Let
me
show
the
the
issue
here
which
we
are
discussing.
It
bring
this
Trace
support
back
just
set
the
chat,
so
basically
Ben
told
that
it
was
removed
because
nobody
seems
to
use
it,
but
it
is
not
a
fair
indicator
because
perhaps
nobody
is
using
it
because
we
provide
no
content
about
it.
We
didn't
spread
any
kind
of
resource
about
it
and
they
they
just
don't
use
because
they
don't
know
that
these
exist,
and
this
is
still
a
a
good
Improvement,
but
I
just
need
we.
Actually.
A
We
are
in
the
point
that
we
need
to
collect
all
the
contact
that
we
have
to
to
measure
the
the
work
that
we
need
to
do
before,
bringing
the
support
back
in
a
stable
way.
So
the
first
thing
will
be
at
least
the
pain
points
of
this
support.
How
can
we
do
to
to
to
to
to
to
make
it
cute
again
and
the
second
one
is
create
content
around
that
right,
so
I
think
Mike
Michael
just
dropped,
so
I
will
not
repeat,
but
that's
it.
A
So
we
are
just
waiting
for
an
answering
that
in
that
issue.
So.
A
Actually,
I'm
planning
to
to
show
actually
to
discuss
this
issue
in
the
collab
Summit
and
showing
the
proposal
I
have
sent
to
you.
So
basically,
that's
my
my
objective
in
my
collab
Center.
B
I
think
the
million
dollar
question
that
the
important
point
is
I,
think
somebody
I
think
Ben
says
it,
but
it's
like
be
careful
what
you
be
careful,
what
you're
volunteering
for
yeah!
It
is
then
be
careful.
What
you're
volunteering
for
go
over
the
V8
node
V8
repo
to
see
what
a
massive
pain
every
upgrade
is
like.
That
is
a
hundred
percent.
What
that's
what
you
need
to
document,
because
that's
that's
where
the
challenge
is
I,
think
for
for
keeping
this
in
core
yeah,
yeah
and
I.
B
Think
like
there's
a
couple
of
things
there
he
mentioned
in
a
no
D
Trace
provider.
We
spot
we've
spoken
about
that,
but
the
there's
no
Linux
support
in
that
note.
D
Trace,
provided
it
could
be
added,
but
it
isn't
there
right
now,
which
is
something
I
forgot
to
mention
to
you
actually,
when
we're
on
that
call,
but
yeah
there's
yeah
that
I
think
once
you
have
that
I
was
surprised,
actually
not
surprised.
B
A
Yes,
okay,
so
I
don't
have
much
much
nothing
else
to
to
share
about
it.
B
C
A
Okay,
the
next
one
is
the
user
tracking
documentation.
This
is
our
root
issue
for
the
documentation
in
the
node.js
Repository.
A
There
is
one
question
there
actually
I
said
was
actually
directly
to
you
and
that
we
have
a
mentioned
when
diagnosing
abnormal
termination
with
lld
llbb,
but
we
have
also
another
accountant
that
Tony
is
doing
is
creating.
That
is
using
LL
nodes
right
once
LL
node
is
like
a
lldb
plugin
I.
Don't
think
that
we
need
both
contents
right,
I
mean
once
done
once
20
finish.
It's
it's
document,
I!
Don't
think
that
we
need
the
using
lldb.
B
Yeah,
okay,
great
yeah,
so
they
are
really.
They
are
the
same
thing.
B
I,
there's
nothing
in
for
lldb
at
the
moment.
Is
there?
No?
No,
so
fundamentally,
if
you
were
to
use
lldb
you'd
run
lldb
and
load
the
V8
plugin
an
LL
node,
just
automates,
all
that,
so
you
don't
have
to
know
the
the
magic
in
order
to
get
lldbe
configured.
So,
yes,
your
point
is
correct.
We
will
replace
and
it
will
be
the
same
report.
I.
Think
in
terms
of
this,
though
I'm
trying
to
understand
what
the
difference
is
between
an
abnormal
termination
and
a
crash.
C
I
think
in
the
past,
discussions
of
normal
abnormal
termination
could
cover
things
like
there's
an
exception
to
them,
and
so
you
know
the
the
no
process
terminates
because
of
that
exception
or
an
unhandled
promise.
But
it's
not
necessarily
a
crash
right.
So
crash
is
a
very
specific
case
of
unhandled
term
or
unexpected
termination
or
whatever.
B
Yeah
yeah
yeah:
these
are
implicit
and
explicit
failure;
modes.
That's
what
they
are:
yeah
yeah,
okay,.
C
Yeah
sorry
I
I
I
was
having
Zoom
problems
earlier.
I,
don't
know
where
you
landed
in
in
the
tracing
side,
but
you
know
I
think
you
were
asking
about
the
context
and
the
context
definitely
was
that
the
the
maintainers
were
having
enough
trouble
maintaining
and
there
was
no
Advocates
or
people
who
could
show
like
hey.
This
is
used
by
somebody
else.
B
B
C
C
B
Past
discussions
really
really
good
point
Michael.
We
know
that
the
folks
over
at
Triton,
which
is
I'm,
going
to
go
with
the
project
name
now
it's
over
the
Triton
Data
Center
and
folks,
because
they
seem
to
be
selling
it
every
other
day,
but
they
we
need
to
hook
up
with
those
folks,
because
they've
said
that
they're
going
to
give
some
smart
OS,
there's
gonna
be
folks
from
smart,
smart,
OS,
Elite,
slash
illumos
that
are
going
to
get
involved
again
to
flag
them
into
that
conversation
and
ask
them.
B
C
B
B
A
Yeah
so
yeah,
actually
the
thing
that
we
need
I'm
trying
to
do
well.
That
issue
is
like
collecting
all
the
the
all
the
all
the
efforts
you
need
to
do
before
bring
the
support
back
yeah
yeah.
We
can
keep
the
discussion
in
the
collab
Summit,
which
will
be
the
next.
The
next
diagnosed
working
group
will
be
at
the
collab
Summit
I'm
right
right.
A
Let
me
see
absolutely
yes,
yes,
okay!
So
that's
the
last
one
removed!
Yes,
okay!
So
going
again
to
our
user
Journey,
expecting
implementation
I
have
removed
the
using
lldb
in
the
abnormal
termination,
which
means
that
the
abnormal
termination
is
ready
to
go.
So
if
someone
wants
to
to
to
make
a
pull
request
to
the
node.js
Diagnostics
guides,
you
can
do
it
so.
B
That's
what
we
were
saying
so
use
the
journey.
You
know
it
needs
a
review,
In,
Summer,
Challenge.
Sorry.
What
I
was
thinking
was
that
the
Journey
that
Tony's
documenting
yeah.
A
But
that.
B
Will
add
a
map
to
the
abnormal
termination
or
a
crash,
and
then
we
probably
need
to
do
something
for
the
other
or
not
I,
don't
know
it's
okay,.
A
You
are
saying
that
they're
using
our
node,
that
is
the
document
Tony,
is
creating.
It
was
actually
it
will
be
created
for
the
crash,
but
can
be
used.
I
think
the
abnormal
termination
too
right.
B
B
A
Actually,
just
wondering
I
mean
even
knowing
that
abnormal
termination
and
crash
are
different.
Behaviors
I,
don't
think
that
we
are
going
to
have
document
specifics
for
each
one
of
those
behaviors
I
mean
we.
A
I
I
believe
that,
like
using
node
report
can
can
work
either
for
crash
or
abnormal
termination,
and
the
same
goes
for
like
using
a
zip,
stacked,
tracers,
stacked
traces
or
something
like
that.
So
I
think
it
is
reasonable,
reasonable,
a
place
to
merge
both
talks.
Don't
you
think.
B
A
B
A
What
terms
what.
A
D
A
B
So
so
crash
to
me
feel
like
as
Michael
was,
was
describing.
Crestamine
feels
like
you've,
basically
run
out
of
resources
like
you've
run
out
of
memory,
or
you
run
out
of
you
run
out
of
disk
or
something
like
that,
and
your
system.
D
B
It
crashed,
whereas
abnormal
termination
is
an
error
has
happened.
You've
got
a
a
method
that
it
doesn't
exist
or
a
function.
It
doesn't
exist
that
type
of
thing
yeah,
but
it's
very
great.
It's.
C
C
A
Yeah
yeah
I
can
only
see
one
approach
that
wouldn't
I
mean
when
you
have
abnormal
termination.
That
is
not
directly
a
crash.
The
only
way,
at
least
my
point
of
view
to
to
check
that
is
by
just
including
some
process
hooks
like
on
cult
exceptions
or
something
like
that
and
intercept
that
with
the
debugger.
That's
all
us,
ES
I
might
be
wrong,
but
I
don't
see
it.
B
Is
that
in
the
actual
documentation?
That's
the
question.
B
Sorry
so,
when
yeah,
so
all
this
context
that
we're
discussing
here
is
discussed
actually
in
as
in
the
introduction
for
the
for
the
session
for
the
documentation
for
abnormal
termination,
there's
a
whole
description
around
what
it
is
and
introducing
what
they
are,
etc,
etc.
Well,
I
think
we're
we're
good.
B
A
B
See
what
they've
done
actually
what
they?
The
reason
why
LL
note
is
in
both
areas
is
because
one
is
around
using
basically
using
V8,
fine
JS
objects
and
the
other
is
around
understanding,
probably
an
unfair
method,
or
something
like
that,
whatever
Tony,
whatever
Tony
lands
on.
B
A
D
A
I
was
just
reasoning
that
the
name
of
the
document
is
using
lldb
but
is,
in
fact
our
node.
Yes,
so.
A
D
Yeah
then
I
can
extract
the
fines
to
your
subject
from
the
other
one.
If
it's
not
doesn't
really
matter
or
two
diagnostic
crash,
you
will
see
yeah
and
also
why
this
part
of
the
dog
will
be
ready
to
be
extracted
and
put
in
the
other
one.
So
I
will
try
to
make
the
full
article
with
more
content
that
I
could
and
then
we
could
extract
few
parts
from
there
and
create
a
new
PR.
A
manager
merge
it
at
the
same
time,.
D
B
D
D
B
D
B
B
A
D
A
A
Let's
go
to
the
or
last
item
that
is
the
report.
Version
semantics
are
not
defined
at
day.
Two
three,
four
nine
but
I
believe
that
the
one
who
holds
all
the
the
the
context
of
this
issue
is
Jewish
and
oh,
let
me
see
if
we
have.
B
B
Could
you
so
I
had
from
the
not
the
last
diagnostic
medium
but
the
the
diagnostic
means
in
prior
to
that?
A
month
ago,
I
said
I'd
have
a
review
because
it
felt
like
there
was
only
quresh
who
had
a
handle
on
it.
So
I
said:
I'd
have
a
have
a
read
of
it
and
get
a
point
of
view,
and
we
can.
We
can
share
from
from
that
point
onwards
yeah.
B
So
it
looks
to
me
like
the
as
their
The
Proposal
from
garesh
to
move
forward
with
a
single
number
makes
sense,
because
and
fundamentally
yeah.
D
B
A
Basically,
the
the
action
or
we
are
ready
to
from
from
the
from
the
Diagnostics
side.
You
just
need
to
someone
just
need
to
to
create
a
request
or
actually
make
a
a
document
saying
that
we
are
not
the
the
report
will
not
follow
those
symbolsomatics
right,
correct.
B
A
A
B
A
B
B
B
C
D
C
Review
at
the
collaborator
Summit
in
a
few
weeks.