►
From YouTube: 2022-11-09 meeting
Description
cncf-opentelemetry@cncf.io's Personal Meeting Room
B
A
A
A
A
Essentially
once
we
bumped
the
API
version
to
1.3,
the
bootstrap
process
looks
in
the
peer
dependencies
of
any
of
the
SDK
modules,
which
appear
depend
on
the
API
and
actually
look
for
that.
Look
for
it
in
npm
does
not
link
it
within
Warner,
so
the
bootstrap
step
fails.
A
The
solution
to
that
is
to
release
the
1.0
or
the
1.3
of
the
API
separately
before
releasing
the
rest
of
the
SDK.
So
that
said,
please
review
this
PR.
It
is
very,
very
small,
and
should
be
very
easy
to
understand.
What's
going
on
here
and
hopefully
this
afternoon
we
can
get
these
releases
through.
A
A
A
So
maybe
we
can
take
some
of
your
some
of
what
you
learned
and
apply
it
to
the
main
repo
I.
Don't
know
if,
if
the
things
you've
applied
have
been
very
browser
specific
and
won't
work,
a
node
or
if
it
should
I
assume,
probably
just
work,
but.
C
Yeah,
it
should
work
yeah,
it
is
mainly
browser,
focused,
sorry,
I
said
roll
it
I
started.
Rush
is
the
fixes
up
the
dependencies.
Roll
Up
is
what
we
use
to
generate
the
browser
bundles
got
it
yeah
in
terms
of
the
sandbox
I.
Have
a
PR
out
at
the
moment
to
effectively
fix
up
the
merge
to
bring
the
history
over
I
still
have
to
go
and
re-implement.
A
Yeah
I
mean
they're
short
term
I
think
we
should
just
get
through
this
release
with
two
PR's
long-term
I
think
we
definitely
need
to
address
this
I,
don't
like
making
these
PRS
for
the
releases,
because
it's
such
a
manual
process
and
there's
so
much
that
can
go
wrong
it
should
it
should
definitely
be
automated.
So
once
we
get
through
this
release,
I
think
that's
going
to
be
my
next
big
project.
A
A
Riley
Yang
completed
the
review
for
us.
There
were
seven
issues,
open,
they're,
all
linked
at
the
bottom
of
that
Community
issue.
If
you're
interested
five
of
them
have
already
been
resolved
and
two
of
them
were
moved
to
after
ga,
that
would
be
the
console
exporters
supporting
Delta
and
cumulative,
which
is
a
non-breaking
change
and.
A
B
Embarrassing
so
the
second
one
should
also
be
in
the
Milestone.
It's
the
scope,
attributes
one.
A
Optional
scope,
attributes
that
made
your
creation
I
just
didn't,
have
the
respect,
review
name!
That's
why
I
didn't
see.
A
Two
were
created
out
of
the
spec
review
and
neither
of
them
are
breaking
changes,
so
they
will
be
handled
after
the
release.
A
The
rest
of
the
issues
are
all
fairly
self-explanatory.
Some
of
them
were
just
Riley
misunderstanding
and
were
closed
immediately,
and
some
of
them
were
easy
fixes
like
documentation,
fixes
and
things
like
that.
A
Please
review
the
the
API
release
and
hopefully
I
can
get
that
merged
in
the
next
hour
or
so
after
this
meeting,
and
then
the
main
release
this
afternoon.
So
keep
your
eyes
open
for
that,
because
waiting
on
reviews
to
release
those
is
one
of
the
more
difficult
parts.
For
me
all
right.
Next
issue.
I
wanted
to
talk
about
was
the
span
timing
fix.
So
just
to
recap:
what's
been
going
on
here.
A
Sometimes
the
performance
timer,
which
we
use
to
gather
timings
can
be
paused,
particularly
when
somebody
sweeps
their
computer
and
they're
in
a
browser.
It
can
also
happen
in
Lambda.
A
We
made
a
fix
for
this
originally
which
used
what
we
called
an
anchored
clock
to
shift
times
to
the
more
correct
time
and
it
does
work,
but
it
only
works
if
the
start
and
end
of
the
span
are
automatically
generated,
it
turns
out,
in
some
cases
in
particularly
the
browser,
the
performance
timing,
API
is
used
to
get
span
end
times
and
those
are
provided
directly,
which
means
they're
not
shifted
to
the
correct
time.
A
So
we
were
getting
negative
span
times.
We
still
do
on
a
currently
released
version.
A
A
A
There
is
also
a
PR
which
implements
this
solution
and
I
would
encourage
people
to
please
go
review
that.
D
E
Yeah
I
just
wanted
to
ask
if,
if
I
could
get
a
few
more
eyes
on
this
PR
to
see,
if
anybody
else
has
feedback,
it's
pretty.
It's
done.
I
just
couldn't
test
a
few
things,
and
it
made
some
comments
at
the
bottom
of
the
pr
about
it.
A
Okay
yep,
so
please
review
that.
I
will
try
to
review
that
if
I
have
time
later,
but
I'm
focusing
on
the
release
right
now,
but
hopefully,
if
we
can
get
through
with
that,
I
will
take
a
look
at
that
this
afternoon.
D
So
I
did
open
a
draft
PR
right
now.
It
still
needs
a
lot
of
work,
but
it's
basically
just
I'm.
Looking
for
early
feedback
for
just
the
structure
of
the
API
or
the
SDK
like
classes
interfaces
I
had
to
make
a
few
updates
from
what
I
had
from
last
week,
based
on
the
latest
Vlogs
SDK
spec,
it's
been
evolving
over
the
last
month
or
so,
but
yeah
like
I'm,
just
asking
like
for
anyone.
D
Anyone
interested
if
you
can
just
take
a
quick
look
at
the
kind
of
the
structure
of
the
SDK
and
before
I
start
writing
tests
and
finishing
the
whole
PR.
Then
that
would
be
useful.
D
D
A
Well,
that
was
all
the
agenda
topics,
so
I
guess
I'll
move
on
to
the
triage.
If
anyone
has
a
topic,
you
can
feel
free
to
add
it
we'll
come
back
after
we
do
the
triage.
A
There
is
not
much
here
Mark
you
opened
this
issue,
but
I
believe
this
is
actually
mostly
resolved
at
this
point.
When
we
merged
the
the
metrics
API
into
the
main
API,
we
added
tests
that
ensure
that
tree
shaking
works.
Those
tests
only
work.
They
only
pass
if
you've
compiled
the
esm
version.
A
So
if
you
just
clone
the
repo
and
run
an
npm
install,
the
tests
won't
pass
unless
you
run
npm
run,
compile
in
the
web
or
in
the
API
package
specifically,
which
is
a
little
bit
weird
I
know,
but
we
don't
compile
the
esm
normally
during
development
because
it
takes
significantly
longer
to
do
the
full
build
and
it's
a
long-term
fix
for
this
will
be
in
the
post,
install
script
to
just
run,
npm
run,
compile
in
the
in
the
API
directory
or
something
along
those
lines
for
now.
I.
B
Yeah
I'm
I
just
find
it
as
a
bug.
Initially,
as
I
was
just
trying
to
go
through
my
normal
workflow
of
opening
a
PR,
and
then
the
tests
would
fail
on,
on
my
part,
with
I
I,
just
thought
that
it
would
like
generally
make
all
the
tests
pass.
But
we.
A
B
A
A
A
So
I
guess
there's
two
ways
to
solve
this.
One
would
be
to
run
the
esm,
build
in
the
API
every
time
and
the
other
would
be
to
have
the
tree
shaking
tests
be
their
own.
B
You
can
make
it
up
for
grabs.
I
will
pick
it
up
if
I
see
that
I
have
some
time
to
work
on
it.
Okay,.
D
A
A
A
Okay,
that's
it
short
meeting
today.
Please
keep
your
eyes
open
for
the
the
release,
PR's
approve
them
and
we
will
try
to
get
them
released
as
quickly
as
possible
so
that
we
can
move
on
to
new
things,
and
you
want
to
have
a
question
or
comment
before
we
close
the
meeting
today.
A
All
right:
well,
thanks
everybody
for
your
time
and
I
will
talk
to
you
next
week.