►
From YouTube: 2022-03-10 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).
A
B
Thank
you.
I
did
not
see
it
I'll
say
it
after
the
card
all
right.
A
A
A
Here
today
I
think
he
mentioned
something
about
him.
No.
C
He's
no,
he
said
he's
having
a
hard
time
joining
a
meeting
says
the
host
has
another
meeting
in
progress.
C
D
Yeah,
I
guess
it
is
five
after
so
I
guess
we
can
get
started.
D
Yeah
man
cause
we've
been
on
so
on
point
with
things
man,
wow,
hey
yeah.
I
gotta
keep
it
positive
man
if
you're
positive
yeah.
So
I
guess
everyone
just
gonna
write
your
names
in
the
ten
sheets.
I
think
topics
for
today
we
can
go
over.
Like
yeah,
we
have
the
announcement.
C
C
Contrib
repo
there's
this
actually
brought
up
a
good
point.
The
instrumentation
is
only
at
least
the
whiskey
instrumentation,
wasn't
testing
with
non-recording
spans
and
that's
obviously
creating
some
issues.
C
But
I
see
I,
I
suspect,
there's
other
bugs
that
we
would
uncover
if
we
ensure
that
all
the
instrumentations
have
to
test
against
like
a
default
api
without
any
like
a
no
api
or
whatever
right.
C
The
instrumentations
yeah
I
mean
the
problem-
is
this
particular
issue
only
got
caught
because
of
the
trace
context,
integration
test,
which
only
gets
run
from
the
core
and
only
gets
run
from
the
core
when
the
contrib
repo
sha
is
updated,
which
obviously
we
didn't
do
until
the
release
that
diego
was
working
on.
So
I
gave
a
bunch
of
time
for
this
bug
to
kind
of
live
on.
I
mean
this
is
only
three
days
ago
or
whatever,
but.
D
No,
it
was
cut
now
because
we
had
that
that
change
in
the
whiskey
instrumentation
right,
like.
D
C
B
B
But
I
think
this
one
is
new
anyway,
I
think
we
should.
We
should
have
a
test
without
sdk.
D
D
D
C
D
Would
it
do
you
alex
yeah
thanks
for
slamming
this?
Do
you
want
to
maybe
create
an
issue,
so
we
can
investigate
the
other
instrumentations.
C
Sure
yeah,
I
just
by
the
way
I
just
tested
this
with
the
check
for
is
recording
and
it
fails.
So
I
guess
I
see
so
it's.
C
D
C
B
It
will
not
have
not
just
kind,
there
won't
be
anything
any
other
properties
right
yeah
many
many
properties
would
be
missing
on
that.
D
Yeah
see
like
the
thing
is
like
the
instrumentations
only
do
depend
on
the
api
and
I
think,
like
you
said,
like
even
borrowing
from
the
record.
Sorry,
the
the
chime
property
right.
We
might
rely
on
other
sdk
attributes
as
well
right
and
other
instrumentations.
D
I
think
we
were
we've
been
kind
of
not
as
diligent
with
enforcing
this,
so
it
would
be
good
to
like
just
you
know
in
iteratively,
go
through
the
instrumentations
and
just
make
sure
that
we
do
some
sanity
checks
there.
You
know
okay,.
D
Sorry,
I'm
pretty
sure
oh
also
alex
you
put,
is
recording
and
it
doesn't
work
yeah.
I
know
I'm
also
shocked.
Is
that
possible
because
is
recording
literally
returns
false
for
non-recording
span.
C
So,
instead
of
looking
for
is
instance,
I
check
to
see,
if
is,
recording
and
the
span
kind,
and
it
it
the
test
failed.
So
I'll
have
to
investigate
a
little
bit
more.
But
it's
jesse.
C
A
C
Sec,
okay,
okay,
that's
it
that's
you're
right!
I
think
I
I
gave
it
as
an
attribute
and
didn't
call
the
method.
Sorry
no
worries
yeah
yeah.
This
is
the
problem
of
trying
to
do
things
quickly:
yeah
yeah,
it's
okay,
yeah,
yeah!
Good!
Thank
you
for
double
checking
me
on
this
because
yeah,
it
wouldn't
make
sense.
Otherwise,.
D
Yeah
I
was
like
like
then
what's
the
point
of
the
is
recording
like
what
does
that
even
do
right,
man,
cool
yeah,
so
yeah,
if
you
could
create
an
issue
to
like
kind
of
sanity
check.
Everything
for
like
accessing
attributes.
C
Yeah,
I
kind
of
feel
like
we
I'll
just
create
an
issue
with
like
a
checklist
to
all
the
instrumentations,
because
I
do
feel
like
we're.
Gonna
have
to
audit
all
the
instrumentation
to
make
sure
that
it
is.
D
Check
that
we
did
for
like
metrics
as
well
or
the
traces
as
well
cool
awesome
that
looks
good
to
me
so
diego
this
was
the
only
thing
that
kind
of
was
blocking
the
release.
C
Oh,
I
think,
he's
still
on
the
phone
he
said
yeah.
He
said
he
was
coming
right
back,
but
yeah
that
that
was
the
thing
that
was
blocking
the
release
of
the
trace
context
was
the
only
thing
that
was
failing
with
the
all
right
sounds
good.
D
Yeah,
nice,
so
that's
the
release,
obviously
with
the
four
people
here.
I
think
we
all
know
that
we're
trying
to
get
metrics
as
part
of
this
release,
so
in
terms
of
I
don't
think
we
have
to
make
any
announcements
or
anything
regarding
it,
because
it
is
still
in
preview
or
like
experimental,
but
we
did
talk
about
in
the
in
the
threads
a
little
bit
about
like
trying
to
get
like
testers
and
like
users
of
it.
D
I
am
sharing
like
this
news
with
like
internal
microsoft
folks,
so
it
would
be
it'd
be
welcome.
You
know
if
everyone
can
kind
of
like
spread
the
word
and
try
to
get
more
people
to
use
it,
because
the
only
like
kind
of
bug,
testing
and,
like
you
know,
stress
testing
that
we
have
is
like
the
implementers
just
using
different
instruments
and
like
just
finding
bugs
like
that,
so
it'd
be
great
to
get
more
users
on
this.
D
D
I'm
not,
I
don't
know
if
diego's
back,
I'm
not
sure
what
the
announcement's
about.
I
I
think
it's
anyways,
so
I
think
diego
and
I
were
talking
since
away-
is
stepping
down
as
a
maintainer
as
an
improver,
now
we're
thinking
about
filling
the
new
maintainer
positions.
So
obviously
we
were
talking
about
srikanth
and
aaron
being
great
candidates
for
that
and
we
paint
them
yesterday
and
this
morning
I
just
I
just
woke
up
to
that.
D
Zukant
is
interested
in
taking
up
that
role
and
aaron
is
a
to
be
determined.
So
you
know
so.
Content
is
doing.
Do
great
work,
especially
with
the
bug
triaging
you
know,
and
and
addressing
support
issues
so
and
has
great
work
in
spearheading
the
logging
effort
for
open
for
open
country
python,
so
yeah.
D
So
we're
we're
happy
to
announce
that,
like
shakant,
is
stepping
on
board
as
a
maintainer,
and
you
know
we're
really
glad
that
you're
on
this
team
and
looking
forward
to
working
with
you
still,
you
know,
you're
just
gonna
have
a
bit
more
responsibilities
now
so.
F
A
B
Thank
you
it's
I.
I
don't
know
how
to
articulate,
because
I
I
joined
like
I
was
I
was.
I
was
only
interested
in
fixing
the
typo
in
readme
and
today
I
have
a
chance
to
take
up
this
opportunity.
It
has
been
a
great
like
right.
Thank
you.
Thank
you.
Everyone,
I'm
looking
forward
to
contribute
more.
E
C
D
Thank
you
cool,
so,
like
maybe
for
the
the
next
release,
we'll
we'll
have
you
try
doing
it?
You
know
we
like
doing
this
as
like
a
it
indicting
you
into
maintainership,
to
see
how
easy
the
releases
are,
and
also,
if
they're
hard.
It's
actually
our
fault.
D
You
know
it's
actually
supposed
to
be
straightforward,
but
you
know
that's
something
that
we'll
probably
get
you
to
do
next
next
month,
so
yeah
cool
yeah,
so
oa
is
not
here
today,
but
yeah
like,
as
I
said
before,
he's
stepping
down
always
still
be
doing
some
great
work,
but
he,
I
think,
he's
kind
of
overloaded
on
his
hand,
so
he
has
to
give
up
some
of
that
time.
So
yeah
great
work
on
his
part,
diego.
That
was
the
announcement
right
like
I'm,
not.
D
I
wasn't
just
making
stuff
up.
Yes,
that
all
right,
nice,
any
other
topics.
Anyone
want
to
go
over
before
we
go
to
prs.
D
All
right,
so
I
haven't
taken
a
look
at
this
at
all.
C
Don't
put
the
pr
in
here.
This
is
just
folks
that
datadog
are
deprecating
the
exporter
and
they
just
wanted
to
update
the
readme
file.
I
figured
if
we
merge
this
in.
We
can
make
this
like
the
last
release
of
this
package.
D
Oh
easy,
okay,
cool
yeah!
This
looks
good.
Oh
also,
this
isn't
a
contrib
right.
So
any
idea,
if
like
these
guys,
are
interested
in
becoming
code
owners
for
them
or
it
doesn't.
C
Mean
they're
just
getting
the
package,
so
it
won't
yeah
they're
not
hitting
it.
So
it's
just
gonna
go
away
all
right!
That's
cool!
It's
cool
with
me
yeah!
In
fact,
after
this,
like
in
theory
after
this
release,
we
can
even
delete
the
package
from
the
repo
to
prevent
it
from
continuing
to
be
released.
D
D
Okay,
cool
I'll
run
just
right
after
like
once
this.
Once
this
build
passes,
watch
this
fail.
C
An
approver
I
mean
you're
joking,
but
that
that
actually
happened
in
the
last
right
now.
D
Yeah,
that's
that's
unfortunate
cool
yeah
that
looks
good
to
me
and
in
terms
of
like
any
other
prs,
we've
been
doing
pretty
well
with
the
issues
that
come
up
so
far,
especially
in
core.
D
D
All
right,
that's
weird,
so
I
think
it'd
be
good.
If
we
take
a
look
at
it
and
helps
your
count
out.
D
Yeah,
hey,
do
you
know
if
this
is
like
specked
out
or
anything.
B
So
I
mean
we
already
have
like
grpc
exporter.
Yes,
this
one
is
only
using
the
parts
which
are
specked
out
like,
for
example,
if
you
look
at
the
environment
variables
right,
there
are
no
underscore
logs
like
separate
environment
variables.
These
are
the
general
ones
that
are
already
there
in
the
specification
yeah.
So
this
is
only
we
are
only
the
implementation
only
considers
what's
already
specced
out
and
nothing
not
introducing
anything
new.
D
Cool
sounds
good
to
me
all
right,
all
right,
so
it
looks
it
doesn't
look
like
there's
any
more
pr's
or
issues
there.
Any
other
topics
that
people
want
to
talk
about
for
this
week.
D
All
right
cool,
if
not
then
short
meeting
today,
and
I
will
see
you
guys
next
week-
then
see
you
next
week.