►
From YouTube: 2021-11-17 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
A
C
Good
yeah
everything
is
good.
I
hope
to
be
able
to
carve
out
some
time
to
come
here
and
maybe
even.
C
So
no
promises
just
yet
but
trying
to
make
that.
B
I
think
we
can
probably
get
started
like
most
people
are
here.
I
don't
have
much
on
the
agenda
today,
so
if
anybody
has
anything
that
they
would
like
to
add
to
the
agenda-
and
now
is
today
is
the
day
on
the
screen
here.
B
Okay,
the
first
thing
I
wanted
to
talk
about
here
is
the
the
yeager
client
sunset,
some
of
you
probably
already
know,
but
the
jaeger
clients
for
all
languages,
not
just
js,
are
being
sunset
or
deprecated
or,
however,
it
is
that
they
termed
it
and
we
actually
depend
on
the
jager
client
in
our
exporter.
B
So
we're
going
to
be
moving
the
relevant
pieces
of
code
from
the
jaeger
code
base
into
our
code
base
and
retaining
their
copyright
notice
I'll
be
working
on
that
today.
I
just
thought
that
just
want
to
let
people
know
they
assume
that
nobody
probably
has
any
objection
to
that.
So
I'll
just
move
right
on
talking
about
metrics
again,
this
seems
like
we
always
do.
B
B
Legendicus
can't
make
this
meeting
because
of
time
zone
issues,
but
he's
been
fairly
active
and
I
linked
a
few
prs
below
here,
particularly
the
views.
Bootstrap
pr
is
rather
big
and
it
affects
a
lot
of
things.
So
it
would
be
nice
if
we
could
get
some
eyeballs
on
it
and
get
it
merged,
because
it
is
difficult
to
work
on
other
things
before
it
gets
merged,
because
the
rebase
would
be
difficult.
B
Speaking
of
a
rebasing,
I
want
to
consider
removing
the
metrics
exporters
from
the
repo
the
same
way
we
removed
the
old
sdk.
B
D
I,
I
think,
legendary
legend,
I
don't
know
the
right
pronunciation,
but
I
really
already
responded
on
the
issue
and
I
think
I
agree
with
him.
I
think
we
tried
to
to
remove
the
sdk
directly
because
there
was
too
much
braking
change,
but
it's
not
really
the
case
for
the
exporter,
because
I
don't
think
as
well
as
him.
That's
really
there's
really
a
lot
of
blocking
change
for
for
the
exporters.
B
Okay,
so
the
reason
that
I
that
I
did
this
is
actually
because
I
was
trying
to
make
a
change
and
the
tests
were
failing
in
the
exporter,
because
I
was
removing
some
of
the
metrics
options.
B
D
B
D
B
Like
skips
to
them,
that's
probably
an
easier
easier
way
to
do
it.
Okay,
that
makes
sense.
So
I
guess
I'll
I'll
close
this
pr
for
now
and
if
we
have
problems
later,
we
can
always
revisit
it
later.
D
Yeah,
I
think
we
can.
We
can
skip
them
with
the
with
the
scope
of
learner
tests
in
the
ci
directly,
but
I
it
might
be
a
little
bit
complicated
because
there
are
quite
few
of
them,
but
yeah
as
you
were.
As
always.
I
think
it
should
be
better
for
now.
D
B
I
will
I'll
look
into
into
ways
to
skip
them
when
we're
doing
learning,
straps
and
stuff
like
that
too,
okay,
okay,
I
added
a
couple
of
prs
here.
It's
like
the
the
views
bootstrap
like
I
said
this
is
a
fairly
big
pr.
It
affects
a
lot
of
things
so
the
earlier
we
can
get
it
reviewed
and
merged
the
easier
it
will
be
to
continue
working
on
the
metrics
sdk,
the
async
instruments.
One
is
a
little
bit
less
impactful,
but
we
still
need
reviews
on
it.
So
just
please
take
a
look.
B
Metrics
exemplars
is
currently
an
issue,
there's
no
pr
open
for
it
yet,
but
this
user
lone
wolf,
who
I
believe
is
actually
on
the
call
today
I
volunteered
to
to
take
this
on.
So
thank
you
for
that
again
to
those
that
don't
know
if
you're
looking
for
something
to
do,
you
can
always
look
in
the
metrics
api
and
sdk
projects
and
find
open
tasks.
There's
a
lot
of
them
and
metrics
are
the
current
area
of
focus
for
us.
B
There's
a
lot
of
to
do
tasks
in
there.
So
if
people
are
bored
of
looking
for
stuff
to
do
that's
the
place
to
go,
are
there
any
questions,
comments
or
concerns
on
that.
C
Just
out
of
curiosity,
like
I
know,
there's
a
few
metrics
implementations
in
the
wild,
like
I'm
wondering
if
there's
any
any
of
them,
that
the
js
implementation
is
kind
of
drawing
some
inspiration
from
or
if
it's,
if
we're
just
all
kind
of
reading,
through
the
spec
and.
B
So,
yes,
the
the
work
in
progress,
sdk
that
we
have
currently
in
the
repository
is
inspired
by.
I
guess
the
python
implementation,
mostly
a
little
bit
of
java,
but
mostly
python
the
views
api
that
legendicus
has
opened.
B
I
know
java
has
a
at
least
what
they
claim
to
be
fully
spec
compliant
metrics
sdk
now,
so
that's
a
good
place
to
go
for
for
inspiration
if
you're
not
sure
how
the
specification
is
is
interpreted,
but
also.
I
know
that
the
spec
would
appreciate
issues
and
prs
if
something
is
not
clear
in
the
specification
itself.
C
E
Thanks
with
the
with
respect
to
the
python
thing,
we
kind
of
gutted
it
as
well
sort
of
like
you,
like
you,
just
did
with
the
work
in
progress
one.
So
I
don't
know
when
it
was
based
on
that.
Did
you,
because
I
it's
based
on
this.
B
E
Yeah,
I
I
actually
put
together
a
doc
with
like
a
proposal
for
the
for
the
python
sdk
like
internals,
and
I
also
did
look
through
the
like.net
and
java
implementations
and
put
a
little
bit
of
a
like
background
somewhere
together.
I'm
happy
to
share
that.
B
Yeah
I'd
be,
I
would
be
really
grateful
to
see
that.
Do
you
mind
just
posting
it
in
a
document
here,
so
that
everybody
can
take
a
look
at
it.
B
Okay,
I
guess,
if
that's
it,
we'll
move
on
to
the
next
item
here,
I'm
not
sure
who
added
this.
D
I
added
it
just
because
it's
a
quick
pr
on
the
api,
just
adding
source
maps
to
the
to
the
build,
and
I
just
wanted
people
to
look
around,
especially
because
it's
adding
size
to
the
bundle-
and
I
see
never
really
reviewed
it.
So
since
it's
a
guy
is
a
guy
about
bundling
size,
I
think
it's
fine
to
to
to
go
ahead
with
it.
F
B
This
is
the
same
thing
we
did
on
the
the
core
real
also.
I
can't
remember
if
we
did
it
in
trib
also,
but
we
should
probably
should
just
be
consistent
across
all
of
our
repositories.
B
Yeah,
so
this
one
upcoming
holiday
schedules-
this
was
something
that
I
was
already
thinking
about.
So
thank
you.
Whoever
put
this
in
here,
11
24
is
next
week.
B
I
will
be
working
that
day.
I
don't
know
who
else
will
be.
I
think
that
a
lot
of
people
will
have
the
day
off
it's
the
wednesday
before
thanksgiving.
F
E
F
B
So
I
yeah
okay,
I
assume
you
won't
be,
then
I
guess
you
know
thanksgiving
is
an
american
holiday.
I
don't
know.
Is
it
canadian
also?
I
suspect
not
in
terms
of
who
would
actually
be
here
if
we,
if
we
did
not
cancel
for
thanksgiving
for
next
week,
because
I'm.
D
Yeah
yeah
in
france,
we
don't
we
don't
have
anything.
So
that's
fine.
B
I
think
for
next
week,
I'll
plan
on
still
holding
the
meeting-
it
might
just
be
short
I'll
at
least
join
the
meeting
and
see
if
anybody
has
if
anybody
joins
I'll
hold
it
like
office
hours.
Basically,
if
that's
okay
with
everyone.
B
For
the
week
of
christmas
and
the
new
years,
I
think
more
people
are
more
likely
to
be
out,
so
I
think
probably
we
will
want
to
cancel
those,
but
we,
I
think,
we'll
talk
about
that
when
we
get
closer
to
it.
B
Silence,
I
assume
people
are
okay
with
that.
So
I
guess
that's
the
end
of
the
agenda.
Thank
you,
aaron
for
adding
this
python
design
proposal
I'll,
take
a
look
through
it
and
we
may
want
to
do
something
similar
for
javascript
or
if
it's
not
different
enough,
then
it
might
be
useful
for
us
to
just
keep
in
mind.
E
I
have
a
quick
question
on
the
jager
client
yep.
I
don't
know
if
you've
taken
a
look
yet,
but
I
think
it
uses
like
thrift
internally
right
it
does.
Yes,
okay,
I
I
don't
know
if
what
like
the,
how
the
thrift
code
generator
works
for
for
javascript,
but
if
it
generates
like
classes
and
stuff
with
like
a
kind
of
like
protobuf,
are
we
planning
to
also
copy
over
like
the
regeneration
code,
so
that
so
that
the
generated
code
won't
rot
or
anything
like
that.
B
E
B
B
B
So
it
does
look
like
we're
using
the
thrift
details.
Yeah
I'll
have
to
look
into
it
a
little
bit
more.
We
can.
We
can
discuss
it
asynchronously
on
the
issue.
Perfect
yeah,
but
I'm
not
like.
As
far
as
I
know,
jager
actually
depends
on
an
external
library
for
their
thrift,
serialization,
which
we
would
probably
also
just
do.
If
they
don't,
then
we'll
need
to
copy
the
code
and
in
terms
of
maintaining
it,
you
know
we'll
just
have
to
we'll
have
to
maintain
it
moving
forward.
B
Anyone
else
have
anything
that
they'd
like
to
bring
up.