►
From YouTube: 2022-01-27 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).
B
B
I
just
have
a
quick
question
on
the
calendar
actually
hold
on
a
second
on
the
calendar
details
there's
a
link
to
getter
yeah.
C
A
A
B
C
E
Hello,
nina
nina
is
my
colleague
at
splunk
and
she's
interested
in
contributing
to
open,
telemetry
and
python.
So
I
invited
her
to
the
thank
jesus
hai.
C
A
C
All
right,
I
think
we
should
start
now
welcome
everybody.
It's
another
edition
of
the
presidency.
Please.
A
A
Okay,
cool:
let's
just
get
started
as
usual.
Please
add
your
name
to
the
attendees
list,
any
prs
or
issues
that
you
wanna
point
out
or
kind
of
streamline.
Please
add
them
to
those
sections.
Does
it
look
like?
We
have
a
lot
of
topics
today.
A
First
thing
we
had
our
release
out.
I
think,
sometime
yesterday
or
the
day
before,
thanks
always
for
handling
that
any
difficulties
doing
that
this
time
or
it's
pretty
straightforward.
As
usual,.
E
There's
a
bug
in
in
this
new
script
and
the
prepare
release,
script
for
country
missed
one
of
the
instrumentation
packages
and
the
version
wasn't
bumped,
and
then
we
I
had
to
manually
release
that
later
is
that.
E
Yeah
for
buttercore
also
related
issue.
It
also
bumps
the
packages
that
we
deem
stable
and
that
we
think
their
own
maintenance
release
like
the
aws
sdk
extensions.
So
there's
some
metal
work
involved
in
that
I'm
planning
to
spend
some
time
on
that
and
fix
the
bug
and
also
add
a
feature
that
excludes
those
packages
from
the
process.
A
E
A
Okay
sure
sounds
good
yeah.
I
think
there
was
a
issue
with
stable,
like
I
had
to
manually
leave
stable
versions
to
be
to
be
bummed.
I
don't
remember
the
details
for
that,
but
yeah
thanks
for
thanks
for
handling
that,
but
we'll
take
a
look
when
you
create
the
issue
cool.
A
Verify
that
I'm
trace
slash
meter,
instrumentation
scope.
Has
anyone
else
taken
a
look
at
this
spec
pr?
I
I
personally
haven't
seen
this
before.
A
Okay,
if
that's
the
case,
then
we'll
just
leave
this
until
until
aaron
either
joins
or
for
next
week.
A
Cool
all
right
straight
on
to
the
oh
wait:
does
anyone
have
any
other
issues
or
topics
they
want
to
talk
about?
That's
not
directly
related
to
an
issue
or
pr.
A
Not
then
we
can
just
get
right
into
it.
Okay,
ego:
one
of
your
prs.
C
Yes,
so
this
is
a
matrix
pr
that
that's
the
checks
for
duplicate
instrument
names.
I
wanted
to
mention
it
here,
because
it's
not
only
related
to
metrics,
but
also
to
error
handling.
This
is
I
mean
the
issue
that
it
aims
to
solve
is
marked
as
as
necessary
for
our
first
mattress
release.
So
I
guess
we
have
to
find
a
solution
for
this.
C
I
am
pretty
much
following
the
plan
that
I
would
have
with
the
future
slash
hypothetical
implementation
of
error
handling,
which
is
pretty
much
to
add
this
checks
into
the
api
and
raise
exceptions
there
intentionally
erasing
exceptions
so
that
this
can
later
be
handled
by
yeah
by
the
error
handling
mechanism,
while
using
proxies
and
everything
else.
C
So
I,
if,
if
people
want
to
take
a
look,
it'll,
be
great
because
it's,
I
think
it
needs
more
people
commenting
on
this,
because
it's
a
topic
that
of
course
broader
than
metric,
so
at
least
the
gluten
recommends
also,
I
have
in
the
in
other
pr
of
the
error
handling
mechanism.
In
case
you
need
more
information.
A
As
for
this
pr
itself,
it's
relatively
simple
right,
like
regardless
of
whether,
like
we're
implementing
the
error
handling
mechanism
or
not
like
it's
necessary
yeah,.
C
Yeah
correct
yeah,
because
I
think
the
error
handling
mechanism
is
a
rather
topic
that
I
mean
will
hold
us
back
if
we
try
to
solve
that
before.
Matrix
is
pleased
right
right.
A
C
The
comments
regarding
early
yeah
yeah,
it's
a
it's
a
good
idea
to
keep
things
separate.
Yes
right,
but,
but
even
so,
this
is
so
thick.
Look
at
this
really
neat.
Oh.
A
Yeah
100,
I'm
just
saying
I
don't
want
to
like
pollute
this,
but
not
like,
like
just
like
span
this
pr
with
I
like
or
block
it,
because
people
have
questions
on
error
handling
so.
A
A
Well,
it
doesn't
seem
like
we
have
any
other
topics
on
the
agenda.
Does
anybody
else
have
anything
pressing?
They
want
to
discuss.
A
All
right,
well,
that
sounds
good,
then
short
meeting
today.
Well,
if
that's
all,
I
will
see
you
guys
so.
C
A
C
Yeah,
in
fact,
if
you
could
open
in
a
new
tab
the
issues
please
select
the
the
ones
that
are
with
the
filter
label,
metrics.
C
Correct,
thank
you
all
right,
so
I
wanted
to
point
out
that
pretty
much
of
that
list
there
are
only
a
few
issues
that
have
not
yet
been
assigned
the
those
two
at
the
beginning.
Then
competition
for
matrix
mode
mechanism-
I
think
most
of
them
are
assigned
to
me,
but
of
all
those
that
are
assigned
only
one
of
them.
That's
not
a
pr
I'm
working
on
the
first
one,
the
rest
of
them
already
have
prs
open
for
them.
C
I
guess
that
this
is
quite
promising
in
the
sense
that
most
of
them
have
people
working
on
them
already.
So
I
wanted
to
know
if
well
it's
too
bad,
that
iron
is
not
here
anyways.
I
wanted
just
to
ask
of
all
the
people
who
are
assigned
if
they
need
any
help,
I'm
pretty
much
looking
for
issues
to
solve.
B
C
Okay,
I
guess
we
can
go
with
the
standard.
I
have
5brs
open
and
waiting
for
reviews.
I've
been
trying
to
comment
and
approve
and
give
absolute
priority
to.
D
C
So
if
anyone
has
anything
that
they
want
me
to
review,
please
bring
me
directly
try
to
do
it
as
soon
as
I
can,
and
I
think
so
I
started
yesterday
for
this
case.
That's
failing
randomly
so
think
in
ci
should
be
back.
C
C
I'm
just
kind
of
confused,
maybe
I'm
not
yes,
I
I
was
looking
in
the
in
the
data
model
and
I
mean
the
the
points
that
you
make
in
that
comments
make
sense
right.
C
The
aggregate
we
have
a
concept
name
aggregation,
temporality
right
and
that
should
of
course,
belong
to
the
aggregation
right.
There
is
nothing
named
instrument,
temporality.
C
So
maybe
the
name
aggregation
temporality
is
it's
not
very
precise,
because
it's
a
concept
that
may
also
apply
to
something
else,
and
it
won't
be
the
first
time
that
we
have
non-descriptive
names
in
the
in
our
open
film,
free
project,
right,
anyways,
I'll
I'll,
still
try
to
take
a
look
at
it
because
I
see
temporality,
it's
something
that
could
affect
instruments
aggregations
and
data
points.
C
So
I
I'll
try
to
provide
the
sensor
that
I
can
I'll
try
to
do
that
today,
so
that
maybe
you
can
close
this
comment
and
hopefully.
A
Yeah,
that's
great.
This
is
like
my
preliminary
understanding
like
I
know
what
this
is.
I
just
didn't
specifically
see
if
this
belongs
to,
like
which
component
yeah
so
like.
A
Originally,
I
always
thought
that
my
understanding
was
that,
like
the
aggregation
is
the
one
that
like
holds
the
temporarily
property-
and
I
don't
know
what
the
specs
says-
I
haven't
taken
a
deep
look
at
it,
but
if
we
take
a
step
back
and
just
like
try
to
like
analyze
what
people,
how
people
use
the
instruments
right,
like
normally
did
they
record
like
an
ongoing
like
for,
for
example,
like
a
counter
right?
They
did.
They
accumulate
the
value
themselves
or
do
they
like
just
you
know,
like
record
individual
measurements.
C
Yeah,
I
think
that's
a
good
point.
C
As
far
as
I
know,
we
don't
have
anything
implemented
that
kind
of
checks
that
right
that,
as
far
as
I
know,
our
our
instruments
will
just
receive
some
number
from
someone
else
and
whether
that
number
is
being
accumulated
or
is
the
difference
with
the
previous
number
there's
nothing
that
we
can
do
about
it
right.
We
will
just
be
fed
up
fed
something.
Maybe
there
is
an
assumption
that
the
user
knows
about
the
nature
of
the
aggregation
that
corresponds
to
the
instruments
and
picks
the
right
one.
C
I
think
that's
the
case,
because
I've
seen
this
situation
being
relevant,
for
example,
to
the
to
even
the.
C
A
Nice
but
yeah
other
than
that
yeah
we'll
take
a
look
at
the
rest
of
your
prs.
Just
just
curious.
Also,
this
I
think
view
instrument
matches
is
the
only
one
that
is
not
necessarily
needed
for
1.10.
Is
that
correct.
C
Yeah
there
is,
I
added
my
my
recent
cd
in
that
comment
that
we
are
yeah.
C
Our
error
replied
but
but
yeah,
that's
that's
you.
That's
also
known
as
new
storage,
so
so
yeah.
Without
that
there's
no
view.
Okay
sounds
good.
A
All
right,
nice
is
that
it
yeah.
C
A
Nice,
I
think,
okay,
it's
cool.
I
haven't
worked
on
metrics
too
much
this
week,
just
been
doing
the
respective
reviews
for
the
prs
that
are
out.
I
will
be
working
on
the.
What
is
it
where?
Is
it
the
invalid
instrument?
Creation
validation
sometime
next
week?
That's
pretty
much!
It.
D
Yeah
sure
so
I
got
the
gauge
done
earlier
this
week
and
I'll
probably
be
tackling
the
histogram
next.
D
I
don't
know
if
I'll
be
able
to
wrap
that
up
this
week
or
not
because
I
started
looking
at
updating
the
proto
to
0.12.0,
just
because
it
deprecates
a
bunch
of
old
data
structures
that
are
no
longer
relevant
in
metrics.
So
I'm
going
to
try
and
maybe
wrap
this
one
up,
because
it's
pretty
straightforward
nice.
D
Yeah,
basically,
they
a
they
took
out
all
of
the
int
like
into
histograms
and
theater
engages
and
lots
of
in
v12.
So
it
simplifies
the
data
that
we
have
in
the
photo
that
generated
photo.
Do
they
just
merge.
D
Yeah,
so
histogram
can
have
number
data
points
that
are
ins
or
doubles
so
yeah.
That's
how
it
yeah.
A
All
right,
I
think,
that's
pretty
much
it
aaron
isn't
here
today,
so
we'll
just
leave
them
any
more
metrics
discussion
the
next
week
cool
all
right.
So
that's
that
anybody
else
has
anything
else.
They
want
to
talk
about.