►
From YouTube: 2022-08-10 meeting
Description
cncf-opentelemetry@cncf.io's Personal Meeting Room
A
Hello,
everybody,
I
guess
we
can
get
started
here.
Let
me
share
my
screen.
A
All
right,
as
usual,
please
add
any
agenda
items
that
you
have
first
item
on.
The
agenda
here
is
releases
so
hold
on.
B
Actually
happened
before
the
previous
meeting,
but
we
didn't
talk
about
them.
I
don't
think
at
the
meeting.
So
for
those
that
didn't
know
those
did
happen.
A
B
The
contrib
release
management
is
failing
entirely
now
it's
failing
in
a
different
way
than
it
was
failing
before
and
I'm
not
entirely
sure
why
it
does
not
appear
to
have
anything
to
do
with
rate
limiting
or
anything
like
that.
It's
just
it
creates
the
releases
on
github
and
then
never
goes
on
to
the
next
step.
So
I
have
to
figure
out
what's
going
on
there,
I
did
create
an
issue
in
release
please,
but
for
now
I'm
just
manually
releasing
them.
B
This
makes
two
changes,
one
it
deprecates
the
sampler
interface
in
favor
of
the
sampler
interface
in
the
sdk
trace
base
package.
It
does
not
remove
it
because
we
can't
remove
it
until
we
have
a
major
version.
It
just
adds
the
deprecated
eslint
tag,
and
it
also
adds
the
getactivespan
helper
method
to
the
trace
api,
which
does
exactly
what
it
sounds
like
looks
like
the
other
maintainers
have
reviewed
this,
but
I
wanted
to
bring
it
to
everyone's
attention
before
before
we
actually
merge
it.
A
B
Just
like
every
week,
we
still
have
this
same
metrics
ga
milestone
we're
actually
moving
along
pretty
well.
As
I
said
last
week,
I
don't
think
the
prometheus
one
is
actually
a
blocker.
So
there's
four
issues
left
here,
but
really
only
three
of
them
are-
are
very
important.
B
The
second
one
here
is
waiting
on
a
specification
pr,
but
I
believe
that
may
have
oh,
no,
it's
still
open.
So
I
was
I
was
talking
with
legendicus
about
this
last
week.
I
don't
remember
what
the
what
the
current
state
of
that
is,
but
that's
the
only
one
we're
waiting
on
like
a
spec,
for
I
did
talk
to
josh
mcdonald,
who
did
not
seem
to
think
that
it
was
a
blocking
issue,
but
I
think
legendicus
disagreed
there.
So
I'm
not
sure
what
the
resolution
is
he's
not
on
the
meeting
today.
B
So
I
can't
ask
him
but
I'll
reach
out
on
slack
this
metric
overflow
for
for
integers.
I
have
it
on
the
agenda
to
talk
about
today,
actually,
but
we
need
to
make
a
decision
on
what
to
do
here.
A
B
We
could
also
just
add
big
int
as
a
value
type
in
the
options
for
the
counter,
and
the
gauge
there's
been
quite
a
bit
of
discussion
on
on
the
issue
here,
on
which
one
you
know
on
the
the
pros
and
cons
of
each
solution.
I
don't
think
any
one
solution
is
the
obvious
correct
one,
but
we
do
need
to
make
a
decision
there.
A
B
B
So
anyone
have
questions
on
that
before
I
move
on,
I
kind
of
skipped
ahead
a
little
bit
here.
We.
B
Okay,
just
quick
update
on
the
browser
support
for
the
protobuf
exporters,
this
person
p
canal,
pervy
canal-
I
don't
know
if
they're
on
a
meeting
or
not
looks
like
no,
they
did
volunteer
to
handle
this
and
according
to
them
there
are
a
couple
of
base
packages
that
also
need
to
be
updated.
The
only
issue
is
that
in
the
base
package,
we
have
this
asynchronous
loading
of
the
util
library.
B
We
originally
did
this
to
prevent
loading
the
grpc
libraries
when
we
were
setting
up
the
sdk,
because
the
grpc
instrumentation
needed
to
be
set
up
before
the
before
it
was
required
here
since
then,
we
have
introduced
the
like
the
proxy
tracer
provider
and
the
proxy
meter
provider,
which
solve
these
issues
separately,
so
we're
actually
just
gonna.
Remove
this
dynamic
require
and,
like
lazy
loading
aspect,
entirely
not
much
to
go
over
there.
That's
just
the
current
state
of
that
of
that
project.
B
Last
week
about
renaming
the
metrics
based
package,
I
think
everybody
was
in
general
agreement.
I
just
haven't
had
time
to
do
this.
I
don't
know
if
anybody
wants
to
to
volunteer
to
have
this
assigned
to
them.
It
should
be
a
relatively
simple
task,
relatively
straightforward.
A
Okay,
I
don't.
B
Remember
what
the
state
of
the
logs
and
events
prototype
was
last
week
when
we
talked,
but
I
know
for
sure
it
is
now
ready
for
review.
Martin
figured
out
the
the
test
failures
and
it
looks
like
some
people
have
reviewed
it,
but
I
think
he's
still
looking
for
feedback
on
this.
If
I'm
not
mistaken,.
B
Okay,
yeah
he's
definitely
gotten
some
feedback,
some
feedback
on,
like
the
api
design,
some
feedback
on
the
actual.
Like
code
of
the
api,
I
think
he's
he's
looking
for
feedback
on
both
that
can
be
fed
back
into
the
specification,
but
that
can
also
be
used
to
improve
this
pr.
So.
B
As
it
will
form
the
basis
for
log
support
in
hotel
gis,
so
it's
a
fairly
important
one
for
anybody
that
cares
about
logs,
which
is
a
lot
of
people.
A
Okay,
so
last
week
we
talked
about
the.
B
The
failing
windows
builds,
there
was
a
pr
that
we
merged
which
fixed
the
build
for
for
people
on
windows,
but
I
guess
the
test
itself.
Just
adding
tests
on
windows
is
still
failing.
I
have
not
really
had
time
to
look
into
this,
but
it
does
appear
to
be
an
actual
test.
B
Failure
not
like
a
build
failure,
and
I
did
re-run
this
and
it
is
still
happening,
so
I'm
not
sure,
what's
different
about
windows,
that's
causing
that
I
have
not
had
time
to
look
into
it,
but
I
think
legendicus
is
and
that's
why
the
pr
is
a
draft.
B
A
A
So
when
you
run
the
tests
locally,
they
pass
that's
correct.
Okay,.
A
Can
you
also
comment
that,
on
the
on
the
issue
since.
B
Legendicus
the
person
who
the
maintainer
who
opened
this
issue
doesn't
have
a
windows
computer.
So
it's
probably
a
little
bit
difficult
for
him
to
to
debug
things
like
that.
That
are
differences
between
ci
and
local.
A
B
Thank
you,
and
similarly,
if
anyone
else
has
has
information
to
contribute
there.
Please
comment
on
that.
Pr.
B
B
I
would
add
the
link
here,
but
I
don't
think
anybody
else
here
actually
has
access
to
the
service
desk.
But
we
have
not
gotten
a
reply
on
that.
Yet
I
will
do
my
best
to
keep
everybody
updated
as
that
evolves,
but
I
guess
they
have
raised
the
rate
limit
for
other
projects
in
the
past,
so
this
is
sort
of
the
process
we
reach
out
to
the
cncf
and
the
cncf
can
reach
out
to
github
directly
and
have
them
raise
rate
limits
for
for
individual
projects.
B
A
The
current
status
similarly.
B
B
The
reason
I
asked
him
to
hold
that
was
because
I
wanted
to
make
sure
that
we
were
covering
ourselves
legally.
Adding
aws
owned
code
into
the
repository
is
something
that
I
am
nervous
about
to
say
the
least
it
is
apache
2.0
licensed.
So
I
think
it
should
be
okay,
but
I
opened
a
cncf
ticket
just
to
make
sure
that
we're
covering
all
of
our
bases
there
and
doing
everything
that
we
need
to
do.
B
I
don't
know
if
there
are
any
legal
experts
here
that
can
help
us
with
that,
but
I
get
I'm
gonna.
Wait
probably
either
way
on
the
answer
from
the
cnc
app
to
make
sure
that
make
sure
that
we're
not
doing
anything
that
will
get
anyone
in
trouble.
B
And
we
have
been
triaging
sort
of
on
the
fly,
so
we
don't
actually
have
any
untriaged
bugs
right
now,
these
both
I'm
looking
into
and
everything
else
we're
waiting
on
information
from
people.
B
A
All
right
well
sounds
like
nobody
has
anything
else
to
bring
up.