►
From YouTube: 2023-03-08 meeting
Description
cncf-opentelemetry@cncf.io's Personal Meeting Room
A
B
A
All
right,
I
think
we
can
get
started
then
so
I
will
share
my
screen.
A
Thank
you
all
right,
so
I'll
be
moderating
the
meeting
again
today,
Dennis
at
the
Hotel
GC
on-site,
so
he
won't
join
today
right
getting
started.
The
first
topic
on
the
list
is
we
have
a
release,
PR
open
for
a.
C
A
Api
SDK
and
experimental
packages
released
so
yeah.
If
you
want
to
see
what
will
be
in
there
just
head
on
over
to
the
pr
and
yeah
that
is
it
for
death.
A
Moving
on
this
is
a
carry
carried
over
item
from
last
week.
The
blogs
SDK
PR
is
ready
for
review.
So
basically
the
author
addressed
some
of
the
of
the
comments
there
and
the
pr
has
been
sitting.
I
haven't
gotten
around
to
reviewing
that
one
myself
yet
but
yeah.
Hopefully
we
can.
We
can
move
this
along.
So
if
you
have
some
time,
it
would
be
would
be
great
if
you
would
head
on
over
and
and
review
that
one.
So
we
can
get
as
many
as
possible
on
it.
A
All
right,
if
there's
any
questions,
always
feel
free
to
just
interrupt
me.
A
So
basically,
I
have
this
PR
out
there
deprecating
the
instrument
type
in
the
instrument
descriptor.
This
is
especially
interesting
for
anyone
working
on
the
on
on
an
exporter
on
a
custom
exporter.
A
Basically,
there
is
this
instrument
instrument
descriptor
in
the
exported
type
for
for
the
Matrix
exporter,
and
that
one
basically
made
it
in
there
by
accident.
It's
the
original
type
of
the
instrument
that
produced
the
metric,
which
yeah
shouldn't
be
in
there.
So
I
applied
some
some
things
there
to
deprecate
it
and
replace
it
and
rename
a
bunch
of
stuff
so
yeah.
It
would
be
great
to
have
some
ice
on
it,
just
making
sure
that
it's
not
breaking
anything
and
that
we
didn't
miss
anything
there.
A
Legend
has
already
reviewed
it,
and
yeah
would
love
to
get
some
more
ice
on
that.
One.
A
Okay,
so
if
there
are
no
other
questions.
A
Then
we
can
move
on
to
next
point
on
the
list
this
is
also
carried
over,
have
have
been
carrying
over
this
one
for
a
for
a
long
time
already
is
the
different
parts
of
the
exponential
histogram
implementation
that
met
I'm,
not
sure,
if
he's
in
the
car
today,
I
don't
think
so
mate.
So
basically,
the
part
two
is
now
already
approved.
Both
Dan
and
I
had
a
look,
and
we
will
merge
this
rather
soon.
A
So
if
you
want
to
give
it
another
look
now,
it's
now
is
the
chance.
I
will
probably
merge
it
after
the
next
release,
because
it's
adding
it's
exposing
some
some
types
that
we
would
want
part
three
to
to
be
around
for
so
yeah
also,
if
that
one
merges
feel
free
to
head
on
over
to
that
PR
and
review
this.
A
Right,
if
there
are
questions
concerns
about
this
one
nope,
then
we
can
move
on
to
the
next
Point
here
by
nav
Nev.
Do
you
want
to
say
a
few
words
about
this?
One.
B
Sorry,
it
helps
if
I
mute
myself
from
thing
as
well,
not
just
my
microphone
thanks
Mark
for
looking
at
this
earlier
today.
This
effectively
is
just
fixing
some
typing
issues.
The
sandbox
uses
well
I've,
now
upgraded
to
use
typescript
4.9.5
and
it
Buffs.
B
On
a
couple
of
these
variations
because
they're
typescript,
the
later
version
is
a
little
bit
more
strict,
so
this
is
just
making
it
so
they're
compatible
Mark
left
a
comment
on
the
the
one
there
that's
on
screen
for
the
is
listener
with
my
local
testing.
B
The
reason
for
the
394
is
node
specific
so
effectively
in
the
later
version
of
typescript
arg0
for
fetch
can
be
a
request,
a
string
or
a
URL
object,
which
is
a
node
URL
object.
So
that's
why
I
have
to
cast
it
to
a
string
to
keep
typescript
happy.
The
other
way
to
do
it
is
to
cast
that
as
any
or
cast
as
a
string
I'm
just
wrapping
as
a
string,
so
it
coerces
any
object.
B
B
I
need
this
to
unlock
this
inbox.
That's
that's
what
that's
happened:
I'm,
hoping
hoping
hoping
hoping
to
get
the
sandbox
going
by
the
end
of
the
week
with
the
basic
stuff
we
need
for
web.
B
A
It
thank
you.
Yeah
I've
I've
already
had
a
look
at
that
one,
and
it
looks
good
as
far
as
I
can
tell
I
will
merge
this
tomorrow
if
somebody
else
doesn't
doesn't
get
to
it
first
and
and
merges
it
so
yeah.
Thank
you
one
more
question
about
the
sandbox.
Were
you
able
to
resolve
the
issue
that
you
brought
up
last
week?
I
had
a
look
over
at
the
repo
and
couldn't
find
what
you
were
talking
about.
There.
B
Yeah,
so
it's
it's
a
little
bit
esoteric.
It's
it
turned
out
to
be
a
typescript
issue
with
the
npm,
alias
so
in
the
resources
test
and
the
trace
based
test.
It
introduces
an
alias
for
resources
as
resources
underscore
190
using
npm
colon
blah
blah
blah,
because
the
sandbox
renames
all
the
packages
to
sandbox
Dash
and
it
also
uses
rush
rush-
has
a
has
a
minor
issue
there
at
the
moment
that
fails
when
it
hits
typescript
it
typescript
says:
I
can't
find
resources.
190.
B
I
have
ended
up
working
around
that.
So,
instead
of
doing
the
package.json
as
saying
imported
as
resources
underscore
190,
because
I'm
already
re
naming
all
the
local
things
to
sandbox,
Dash
I
just
leave
that
as
resources,
and
that
makes
everything
happy
and
it
still
has
the
npm
colon
as
the
Alias
for
importing
it
in
so
yeah
I
have
finally
got
a
workaround
for
it.
It's
just
painful
yeah.
So
this
line
on
the
the
screen
here,
where
it
says
at
open,
Telemetry
resources
underscore
190
colon
npm.
B
A
So
the
the
script
is
now
able
to
to
handle
this,
or
is
there
anything
that
we
could
apply
in
the
in
the
core
repo
to
make
your
life
easier?
There.
B
No
script
now
handles
this
right,
so
it's
only
an
issue.
I
think,
because
I
rename
all
the
as
I
bring
the
packages
over
I,
effectively
rename
resources
to
sandbox
Dash
resources
and
API
to
sandbox
API
so
effectively,
I
put
a
prefix
on
it
so
that
it
doesn't
somehow,
if
we
end
up
publishing
any
of
this
inadvertently
pollute
the
real
stuff,
because
the
gold
Master
is
JSM
concrete.
B
I
do
have
a
PR
App
to
fix
that
at
the
moment
it's
currently
the
Builder's
breaking
so
I
need
to
fix
up
a
few
bits
and
pieces
so,
but
I
need
the
JS
code
fix
in
there
first
before
I
can
merge
it
all
in
I've,
already
merged
the
Json
concrets
into
the
merge
Branch
as
of
yesterday.
So
it's
just
you
know,
munging
it
from
the
merge
branch,
which
is
how
we
get
all
the
history
into
the
sandbox
into
the
the
format
that
gets
compiled
for
the
web
stuff.
A
A
B
Yeah
yeah
do
we
want
to
change
that
to
any,
because
at
the
moment,
it's
out
of
date
anyway,
so
I'll.
A
Do
that
I
I
guess
we
can
change
it
to
NES
that
it
would
be
my
preferred
thing
because
it
has
this
yeah.
It
has
any
in
it
anyway.
A
All
right,
thank
you.
Are
there
any
more
questions
or
topics
to
bring
up?
A
If
no
one
has
anything,
then
we
can
move
on
to
the
back
triage.
If
anything
comes
up
during
the
bacteria.
Just
let
me
know,
and
we
can
go
back
to
the
agenda
there-
all
right
so
Andreas
box
in
core.
A
You
have
this
first.
One
here
include
protest
fires
in
the
bundle
directly
someone
seems
to
be
using
the
grpc
export
and
having
problems,
because
the
protests
are
not
in
the
bundle.
A
I
have
been
looking
at
another
issue
that
was
similar
to
this
I
think
it
was
that
one
and
that
one
is
already
a
duplicate,
so
I
will
yeah
I
will,
after
the
meeting
just
write
a
comment
there
and
ask
them
if
that's
the
same
problem
and
and
Mark
it
there
I
think
you
don't
need
to
do
it.
Do
it
in
this
meeting
the
next
one
is.
A
It
has
already
a
bunch
of
discussion
in
there
there's
also
a
bug
report
on
require
in
the
middle.
A
The
person
here
is
suggesting
that
there
will
be
a
workaround
I.
Think
I
will
also
get
back
to
this
one.
It's
a
bit
hard
to
get
all
the
context
for
for
this
one
by
just
reading
reading
through
it
here.
A
And
or
the
others
I
think
we
have
already
touched
on
before
this
one
has
some
information
requested
and
still
nothing
new.
This
one
I
think
I
already
asked
them
and
provided
a
background,
I
added
that
is
still
issued,
that
it
duplicates
its
since
we
don't
support
bundling
the
grpc
exporter.
Yet
this
is
a
margin,
as
a
feature
request.
So
I
need
to
duplicates
would
probably
be
the
same.
A
A
Because
there's
some
wrong.
A
Already
being
this
person
here,
I
think
ever
being
the
op
as
well.
A
All
right,
and
that
should
be
it
for
Country
this
way
all
right.
If
there
are
no
more
topics,
then
thank
you.
Everyone.
C
Hi,
hey
Mark,
I
I
had
one
quick
question,
all
right:
yeah
yeah!
So
there's
this
issue
implement
the
span
exporter
for
Force
wash
I
can
drop
you
a
link
in
the
zoom
chat.
If
you
like.
C
Yeah,
so
I
was
looking
at
this
issue
because
I
was
going
through
some
of
the
up
for
grabs,
I'm.
Sorry,
a
good
first
issue,
tagged
issues
and
I
looked
through
some
of
the
conversations
that
happened.
I
think
there
was
something
in
the
old
repos
well
and
it
looks
like
there
hasn't
been
any
activity
on
it
in
a
while.
I
did
reach
out
to
damn
here,
but
I
didn't
get
an
answer
and
I
just
was
curious.
If
I
could
pick
this
up,
given
that
I
haven't
seen
any.
A
A
A
If
not,
then
I
guess
we
had
a
rather
short
meeting
today.
So
thank
you,
everybody
and
see
you
next
week.