►
From YouTube: Diagnostics WG meeting March 8, 2022
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).
B
A
C
A
D
Yeah,
I
think
that
I
don't
know
why
it
was
added,
but
I
think
it's
just
too
I
I
don't
see
anybody
disagreeing
on
that,
so
maybe
the
it
was
added
to
the
agenda
just
to
make
sure
that
we
we
all
agree
with
this
movement.
A
B
D
Actually,
we
already
have
a
channel
in
the
node.js
is
like
channel,
but
this
is
this
channel
is
public
and
is
not
paid,
so
we
don't
have
some
features
that
is
like
has
in
the.
C
D
League,
so
I
think
that
when
we
move
to
the
openjs
foundation,
server
will
be
able
to
to
have.
C
B
B
C
I
think
we're
free
to
do
wherever
we
want,
but
it's
easier
from,
if
a
bunch,
if
a
bunch
of
people
are
already
using
it
and
it's
got
the
extra
features
it
seems
like
the
right
place
to
be,
and
unless
somebody
has
an
issue,
I
think
it'd
be
right.
Harish,
it's
like.
Unless
anybody
objects
we
should
just
do
it.
A
A
A
Then
we
zeroed
down
on
to
alternate
tuesdays,
and
then
we
reopened
the
issue
to
gather
the
time,
because
the
current
time
was
inconvenient
to
many
folks
now
I've
opened
a
doodle
to
gather
the
convenient
times
for
many
folks,
just
testing
the
doodle
link.
Here,
if
you
want
to
have
a
look,
I
just
reviewed
it,
and
my
impression
is
that
it's,
it's
still
pretty
complex
mathematically.
A
A
I
think
the
root
cause
being
we
have
participations
from
the
west
coast,
east
coast,
europe,
asia
and
australia,
and
covering
all
these
time
zones
looks
nearly
impossible.
B
A
That's
possible,
but
I
mean
looking
at
the
agenda
items
we
are
thinning
out
on
the
agenda.
So
just
wondering,
is
it
really?
A
B
A
E
Yeah,
I
I
don't
think
it
matters
quite
so
much
though,
if
like
it,
if
we
try
to
keep
like
decision
making
to
be
more
of
an
async
process,
and
just
have
this
as
more
like
a
discussion
call
then
like.
If
we
had
like
a
rotating
time
like,
I
think
it
would
be
fine,
if,
like
a
bunch
of
people,
can't
make
it
to
particular
times.
E
C
I
think
we
should
do
that
anyway,
like
basically,
there
should
always
be
an
issue
for
any
kind
of
decision,
we're
making
so
that
everybody
can
chime
in,
because
I
don't
I
don't
know
that
we've
had
too
many
votes
or
anything.
C
The
meetings,
like
you
said,
are
a
good
place
to
like
have
a
higher
bandwidth
discussion
on
something
to
help
people
come
up
to
speed
and
form
opinions,
so
you
know
maybe
the
I
don't
it's
you
know
finding
one
time
slot
is
probably
going
to
be
impossible,
as
jarish
was
saying
so
maybe
rotating
does
is
the
only
way
to
make
it
so
that
you
can
have
some
of
those
discussions,
even
if
it's
not
the
full
group.
Every
time.
B
A
A
Because
between
then
and
now,
I
think
that
isn't
changed
much
people
express
their
convenience
as
such,
the
only
person
missing
is
tony
tony.
A
A
E
Yes,
still,
nothing
really
changed
there.
We
got
some
user
feedback
like
a
while
ago,
but
not
too
much
recently.
E
I
just
need
to
start
building
stuff
to
satisfy
some
of
the
things
people
have
asked
for
the.
D
Guy
in
the
last
discussion
we
I
took
the
task
to
take
a
look
in
the
clinic.js
usage
of
async
rooks
to
to
check
if
we
can
use
diagnostic
channel
or
other
stuff.
D
But
in
fact
I
have
seen
that
most
of
my
concerns
about
migrating,
the
think
hooks
usage
from
from
from
klingjs
was
discussed
previously
by
mateo
in
the
issue.
So
I
haven't
added
anything
in
there
in
the
issue
because
most
of
my
concern
is
there
as
well
so.
E
Yeah
and
I
matteo
was
suggesting
as
well-
that's
like,
rather
than
like,
particularly
aiming
for
like
marking
guessing
hooks
as
like
deprecated
or
legacy.
We
could
also
consider
marking
it
as
internal
eventually.
B
E
We're
basically
telling
people
like
this
is
an
internal
thing.
You
shouldn't
use
this,
but
yeah
yeah,
we've,
we've
kind
of
had
like
a
bit
of
uncertainty
about
like
what
to
call
it
exactly
because,
like
just
due
to
due
to
like
usability
concerns
around
it
and
like
there's
security
implications
of
it
and
like
it's,
it's
really
difficult
to
do
any
sort
of
make
any
sort
of
changes
to
it
to
try
and
improve
the
performance
or
anything
like
it's,
just
not
an
api
that
we
can
recommend
using,
but
there's,
unfortunately,
just
not
really.
E
Not
not
really
anything
that
fills
all
of
the
same
use
cases
yet
just
like
what,
where
this
issue
came
from,
trying
to
gather
use
cases
and
we
can
build
just
purpose,
focused
things,
and
hopefully
people
will
migrate
away
from
it.
But
it's
it's
difficult
for
us
to
just
straight
up.
Remove
it
because
we'll
break
people
if
anyone
is
still
using
it.
D
Oh
yeah,
I
I
don't.
I
don't
think
that
it
would
be
easy,
or
at
least
would
be
possible
to
to
to
support
the
usage
of,
for
instance,
in
the
bubble
graph.
We
just
need
to
to
capture
all
the
the
sync
resource.
All
the
async
types.
Actually,
that
is,
is
bumping
in
the
application.
So
I
don't
think
that
it
will
be
ever
supported
by
a
single
local
storage
in
some
moment
without
exposing
it
internals
or
even
without
doing
things
better
than
the
sync
rooks
right
now.
D
So
I
I
see
this
issue
open
for
a
long
time
and
we
are
discussing
it
a
long
time
so,
but
I
don't
see
some
actionable
or
something
like
this
or
something
that
we
can
help.
You
know
we
have
shared
what
what
is
the
use
case
and
still,
I
think
glucose
doesn't
support,
and
maybe
we
can
think
about.
You
know
way
to
support
it
without
using
rooks
right.
C
I
think
that
was
the
plan
right,
like
async.
Local
storage
covers
some
portion
of
the
use
case,
but
for
the
other
ones
steven
you
know
was
we
were
trying
to
gather
input
to
understand
what
the
other
ones
were,
and
they
may
be
other
apis
that
are
needed
to
cover
them.
So
it's
figuring
out
what
api
do?
We
think
we
could
support,
which
would
cover
that?
Other
use
case,
I
think,
is.
E
Yeah
yeah,
that's
right.
I
know
like
one
of
the
main
ones
that,
like
a
fairly
large
number
of
people
use,
is
long
stack,
traces
which
we
like.
We
need
to
have
a
solution
for
that.
I
think
yeah,
the
tracking
resource
lifetime
there's
a
few
people
that
want
that,
but
I
I
I'm
not
sure
exactly
how
we
should
do
that
or
like
what
it
like.
What
the
shape
of
that
should
be.
Like
there's,
there's
questions
I
have
around
that
one
in
particular
about
like.
E
Do
we
actually
need,
like
the
exact
events
when
things
happen,
or
is
this
just
like
a
like
statistical?
We
we
want
to
know
like
at
this
time,
there's
this
many
things
of
these
types
or
do
we
need
to
like
know
that
exactly
this
thing
was
just
created
right
now.
This
thing
was
just
destroyed
right
now,.
D
E
A
A
D
I
would
like
to
to
just
draw
a
question:
the
diagonal
repository
is
kind
out
of
date,
for
instance,
if
you
go
to
the
readme,
we
see
a
lot
of
initiatives
that
most
of
them
is
done,
or
is
this
stupid?
For
some
reason
I
want
to
know
what
is
the
exact
exactly
path
that
we
follow
to
to
update
those
initiative?
D
I
mean
how
we
can
create
some
some
new
initiative
or
discuss
in
a
way
of
brainstorming,
some
possible
initiatives
or
for
us
I
mean
I
see
that
the
last
meetings
of
the
diagnostic
working
group
is
only
there
is
only
one
or
two
issues
and
we
are
not
moving
to.
We
are
not
moving
forward
with
it.
You
know,
so
I
would
like
just
to
to
to
ask
how
we
can
bring
some
other
discussions
or
other
initiatives
to
to
to
this
group.
A
So
if
I
take
a
stab
on
that,
the
two
major
book
items
which
this
working
group
can
focus
on
or
comes
under
the
purview
of
this
working
group
is
number
one.
The
user
journey
and
best
practice
documentation,
which
you
are
already
aware
of.
A
The
second
one
is,
if
you
look
at
the
tools
that
this
project
endorses,
or
this
ecosystem
user
is
quite
vast,
and
the
state
of
the
maturity
level
of
these
tools
are
at
different
stages.
For
example,
we
have
we
have
classified
the
tools
in
terms
of
tier
1,
tier
2,
tier
3,
etc,
based
on
the
maturity
level
based
on
the
adoption
in
the
field
based
on
the
capability
that
they
are
exporting,
and
things
like
that.
A
So
one
of
the
thing
that
I
propose
is
to
look
at
the
state
of
the
affairs
of
the
tools
and
see
make
look
at
a
as
a
collective
intelligence
and
see
what
we
can
do
over
there
to
improve
in
terms
of
the
capabilities,
better
documentation
or
adding
newer
features
based
on
new
use
cases,
new
workloads
and
newer
deployment
targets
such
as
cloud
and
things
like
that.
That
would
be
a
good
exercise
to
do.
I
was
planning
to
open
an
issue
for
that,
but
good
that
you
talked
about
that.
A
C
C
If
so,
those
are
the
best
places
to
start
on
the
proposal
right,
you
know,
if
you
don't
have
specific
things
you
want
to
propose
and
work
on,
then
you
know
like
the
the
one
we
were
just
talking
about
about.
Looking
for
how
and
what
the
api
would
look
like
to
cover
that
other
requirement.
That's
not
covered
by
async
local
storage,
I
think,
would
be
one
of
the
higher
priority
things
to
look
at
from
my
from
my
perspective
anyway,.
C
It's
less
about
like.
Is
there
some
process,
it's
more
like?
If
you
have
something
that
you
think
you
want
to
propose,
you
can
open
an
issue
and
say
hey.
We
should
do
this,
here's
what
I'm
thinking
and
then
you
know
the
rest
of
the
that'll
help
other
people
sort
of
chime
in,
but
it
comes
down
to
like
what
are
you
looking
to
help
lead
because
that's
where
we
usually
end
up
with
the
we
need
somebody
who
has
got
like
enough
time
and
initiative
to
push
it
forward
and
then
other
people
kind
of
help
out.
D
Yeah,
actually,
I
was
thinking
something
related
right
now.
I
I
working
a
lot
with
diagnostic
tools
and
also
profilers,
and
I
feel
that
there
is
a
gap
that
with
node.js
doesn't
cover
this.
This
section-
and
I
would
would
be,
would
be
glad
to
move
some
initiative
forward,
but
I
don't
have,
I
don't
know
one
key
initiative
to
share.
You
know
just
would
like
to
to
have
some
brainstorming
with
the
with
the
thing
and
then
we
come
up
with.
C
Here's
where
we
don't
have
a
good
answer,
and
then
you
know
if,
if
it's
just
that,
we're
not
sure
we,
if
there's
an
answer
or
not
that's
a
great
time
to
set
up
like
a
brainstorming
meeting
to
say,
let's
talk
about
this
particular
area
and
get
people's
knowledge
and
share
the
knowledge
and
all
that
you
know
or
or
if,
if
you
know
it
or
if
it's
like
the
steps
before
that,
you
know
you
could
set
up
an
like
a
an
issue
and
in
one
of
the
meetings
or
a
special
meeting,
talk
about
like
okay,
here's,
the
problem
we
want
to
tackle.
D
Yeah
yeah
yeah
good
point
I
mean
I
would
think
about
something
I
I
will
try
to
create
a
map
of
my
understanding.
What
is
missing
the
node.js,
the
like
diagonal
land
and
then
I
can
share
in
some
issue
we
discuss
and
then,
if
we
decided,
if
it's
a
real
gap,
we
can
do
a
brainstorming
and
then
come
up
with
a
possible
initiative
right
yeah.
That
sounds
good.
Okay
sounds
good
to
me
as
well.
Thank
you.