►
From YouTube: 2021-11-18 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
B
A
Edition
of
the
python
stick
as
usual.
Please
add
your
name
yet
on
this
list.
Let's
paste
it
there
in
chat,
so
you
can
leave
one
minute
for
other
people
join.
A
C
A
All
right
so,
let's
say
we
start
there's
this
document
that
aaron
added
here,
which
is
that
explains
the
design
for
sdk
matrix
or
maybe
you
should
have
metrics
in
this
here
somewhere
yeah
yeah.
C
C
Share,
do
you
wanna
drive
sure
I
mean
well,
I
was
gonna
ask:
did
anybody
have
a
chance
to
look
at
it?
Besides
diego?
I
know
you
had
a
look.
B
I
haven't
added
any
comments,
but
I
have
been
like
reading
trying
to.
You
know
understand
certain
disciplines
that
you
want
to
move
on
the
implementation
part.
I
I
also
you
know
just
reading
this
again.
B
Yeah,
so
I'm
so
I'm
still
reading
it
don't
have
any.
You
know
comments
to
add
at
this
point.
That's
what
I
will
say.
C
Oh
okay,
gotcha
cool
yeah.
I
mean
I
don't
know
if
there's
anything
specific
to
call
out
right
now,
but
it
would
be
good
if
everybody
took
a
look.
I
sort
of
went
through
like
the
java.net
implementations,
looked
at
what
they've
done
and
tried
to
write
down
a
design
for
how
we
can
implement
stuff
because,
as
strikeon
pointed
out,
it's
not
it's
not
completely
really
described
in
the
sdk
spec.
C
So
like
I'm,
proposing
everything
I'm
proposing
here
is
sort
of
internal
parts
of
the
sdk
things
that
wouldn't
necessarily
be
given
to
the
user.
Yet
is
sort
of
just
the
way
that
we
hold
an
aggregate
state
which
isn't
really
specified
so
yeah.
I
also
have
a
prototype
pr
with
some
code
that
you
can
run
and
you
can
see
it
working
there's
like
a
little
script.
You
can
run,
but
I
haven't
added
any
tests
or
anything
yet
yeah.
Just
please
take
a
look
and
yeah.
I
think
that's
all.
A
Perfect,
yes,
the
community's
great,
please
when
you
have
a
chance
to
take
a
look
at
it
with
your
comments,
so,
okay,
everyone
just
to
give
you
a
small
update.
I
emerged
a
few
years
ago,
the
aggregations
and
the
instruments,
pr
that
we
had
had
open.
Thank
you,
aaron
and
sign
for
your
reviews.
A
That's
in
next
thing
that
is
coming
is
the
views
pr
pretty
much.
The
plan
that
that
we
have
so
far
is
just
to
open
up
yours.
That
will
be
adding
components
and
then
I'll
be
taking
a
look
at
this
document
when
I
implement
them
mainly
to
integrate
the
ideas,
design
and
add
it
here,
the
appears,
but
just
to
give
you
some
update
on
that
anything
else.
Everyone
do
you
want
to
comment.
C
No,
I
think
that
sounds
good
and,
of
course,
feel
free
to
like
copy
paste
code
from
the
prototype,
because
I
don't
have
a
any
intention
to
merge
it
directly.
As
is,
I
was
gonna
just
split
parts
out
as
we
as
we
agree
on
this
document,
so
that
we
can
have
like
tests
and
more
easily
easy
to
review,
pr's
chunked
up
so
sure
I'll.
Allow
you,
as
a
co-author.
A
All
right
so
aaron
has
another
topic.
How
do
we
feel
about
better
classes.
C
Yeah
yeah,
so
in
in
the
prototype,
I
did
use
data
classes
a
lot
if
people
aren't
familiar
with
them
they're.
Basically,
it's
kind
of
like
it's
yeah,
it's
built
into
the
python
center
library
since
3.7
and
there's
a
back
port
for
3.6,
which
we
still
support,
and
it's
just
a
nice
way
to
make
these
simple.
Like
data
structs,
you
can
make
them
immutable
really
easily,
which
is
nice.
You
don't
have
to
implement
the
constructor
or
all
of
the
like
private
property,
getters
and
stuff,
like
that.
C
So
it
made
the
code
a
lot
simpler
and
I
noticed
we
haven't
used
it
at
all
in
our
in
our
code
anywhere
so
far,
probably
because
we
used
to
support
3.4
in
3.5,
but
at
this
point
since
since
3.6
is
well,
there
may
be
maybe
some
complications
with
getting
rid
of
3.6,
because
it's
still
not
end
of
life
and
I
believe
pi
pi,
as
in
py
py,
still
still
will
be
on
python
3.6
version
of
the
standard
library.
C
We
might
need
the
backboard
for
a
little
while,
but
it's
like
a
you
know,
semi-official
back
port.
I
think
it's
actually
in
the
pep.
They
they
link
the
the
backboard
package
or
something
but
yeah
I
don't
know.
Does
anybody
have
any
thoughts.
A
Yes,
I
do,
I
think
this
is
this
is
good
data
classes
are
pretty
much
a
simple
idea.
It's
just
a
decorator
that
automatically
adds
some
representation
for
some
some
methods,
so
it
saves
us
from
having
to
type
all
that
code
and
there
are
some
particular
classes
where
this
is
ideal,
because
there
are
classes
that
pretty
much
don't
have
any
working
methods
any
operations
that
they
do.
They
pretty
much
just
store
data
and
yeah.
This
is
the
ideal
feature
for
those
kind
of
situations.
Yeah
complete
importance.
A
Okay,
so
this
is
a
safety
prototype.
We
have
been
discussing
this
for
a
while
so
far,
which
always
was
here,
but
all
right.
Just
to
let
you
know
this
prototype
introduces
this
idea
of
the
the
user
only
having
contact
with
api
objects
and
these
api
objects
act
like
proxies.
A
B
A
It
will
be
caught
by
this
api
proxy
and
this
api
proxy
will
raise
a
warning
and
will
return
a
default
value
so
that
the
application
code
doesn't
crash
unless
it
is,
the
application
is
being
executed
with
this
option
that
converts
warnings
into
actual
exceptions.
So
I
had
some
feedback
from
aaron
and
from
always
about
not
implementing
this
safety
feature
in
this
way,
but
I
think
just
applying
the
decorator
that
will
make
code
safe
to
every
component
in
the
sdk
and
the
api.
I
guess
so
that
there
are
no
proxy
objects.
A
Just
everything
is
stamped
with
the
decorator,
so
it
makes
it
safe
and
an
arrow.
If
you
want
to
discuss
this,
this
approach.
A
Okay,
yes,
I
think
this
approach
may
also
work
or
can
also
work.
I
do
think
it's.
A
It's
just
more
code
and
it's
a
bit
fragile
because
it's
easy
to
forget
to
the
decorator
on
this,
but
that's
slightly
less
important
that
actually
adding
this
feature
some
somehow
right,
because
it's
a
specification
requirement
anyway
I'll
be
trying
to
implement
this
mechanism
the
safety
mechanism
into
into
tracing
and
yeah.
If
anyone
else
has
any
comments
or
ideas
that
you
want
to
discuss,
please
add
them
into
this
pr
as
well.
C
Yeah,
I
think
the
only
thing
I
would
say
it
in
like
a
prototype
for
tracing
that
I
would
want
to
see
is
I
want
to
understand,
because
I'm
not
super
familiar
with
the
warnings
class.
Sorry,
the
warnings
module
how
granular
we
can
make
it
so
that
you
know
people
can
maybe
choose
between
fail
fast,
always
fail,
and
you
know,
silence
everything.
C
So
so
always
fail
would
be
like
if
you
are
writing
a
unit
test,
and
you
want
it
to.
You
know
like
be
super
super
strict,
because
it's
just
a
test
you
would
be
able
to
like
make
it
so
that
something
like
a
invalid
spend
name
would
cause
an
exception
to
be
erased
like
an
empty
spin
name
or
something.
C
Right
right,
but
there's
also
like
we
discussed
the
fail
fast
mode
of
like
during,
for
instance,
when
you're,
creating
like
a
tracer
or
something
like
that.
Some
people
will
probably
want
that
to
cause
their
application
to
to
freeze
right.
C
Because
I'm
saying
sorry,
what
I'm
proposing
is
there's
like
three
different
levels
of
granularity
that
you
might
want
to
to
have
like
completely
catch
all
errors
and
silence
everything
one
where
the
sdk
will
fail
fast
and
cause
your
application
to
crash,
and
then
one
where
internal
sdk
errors
or
misuse
of
the
sdk
or
api
will
cause
acceptance
to
be
raised
right.
Well,
okay,
where.
A
What
happens
is
that
there
are
actually
only
two
ways
of
using
warnings.
A
One
is
that
any
warning
being
raised
will
cause
an
exception
and
the
other
one
is
the
opposite,
where
they
won't
cause
an
exception.
The
fail
fast
only
applies
to,
at
least
in
a
prototype
only
applies
to
the
function
that
sets
the
sdk
and
that
function
is
not
protected.
So,
if
anything
goes
wrong,
there.
C
I
thought
we,
I
thought
you
were
just
saying
that
we
can't
really
implement
that
without
without
breaking
changes,
so
that
we're
going
to
just
put
decorators
on
on
the
functions
individually
right.
No,
no.
A
Somehow
right
we
have
some
mechanism
to
decide
which,
which
sdk
gets
just
used
via
entry
points
or
pretty
much
whatever.
That's.
A
Connection
that
that
one
I
mean
it
doesn't
really
matter.
The
point
is
that
we
have
a
mechanism
to
set
the
escape.
What
I'm,
what
I'm
planning
to
do
is
to
not
protect
that
existing
mechanism
so
that,
if
anything.
A
A
The
warnings
apply
only
to
what
happens
next.
So
if,
while
you're
running
the
application
and
something
goes
wrong,
creating
a
span
or
whatever,
then
if
you
are
running
in
safe
mode,
that
will
be
that
exception
will
be
turned
into
a
warning
and
won't
crash
the
application.
And
if
you
are
not
running
in
safe
mode,
it
will
just
crash
the
application.
C
Right,
yeah,
but
but
I
think,
like
the
so
the
spec
doesn't
say
what
qualifies
as
like
initialization
versus
what
is
just
like,
like
it's
kind
of
fuzzy
on
that
right.
So
if
we
could
offer
the
granularity,
then
people
can
choose
is
what
I'm
saying,
but
I
did
I
did
put
in
the
the
signals
just
now
the
link
to
the
warnings
package.
C
C
Yeah
so
we
could
have,
we
could
have
specific
warnings
for
like
different
levels,
so
to
say
so,
like
maybe
some
users,
the
you
know,
the
metrics
are
super
important,
so
they'll
say
if
the
meter
provider
or
if
the
meter
can't
be
created,
then
we
want
the
application
to
crash
right.
A
A
To
understand
yeah
the
what
I
think
will,
what
I
think
you
want
to
be
implemented
is
something
that
will
filter
out
the
different
warnings
being
raised.
So,
for
example,
if
someone
defines
a
warning
for
a
meter
not
being
able
to
be
created,
let's
say
a
bad
meter
created
warning.
A
What
I
think
you
want
is
for
the
user
to
be
able
to
run
it
and
pass
it.
Some
configuration
option
that
says
if
bad
meter
created
warning
has
been
raised,
then
crash
the
application
and
I'm
not
sure
that
the
warnings
filter
mechanism
works
for
custom-made
warnings.
I'm
not
sure,
because
I
think
I
tried
it
once
and
it
didn't
work,
but
we
can
figure
something
out.
Yeah.
C
Cool
yeah
yeah,
that's
that's
all
I
meant,
and
then
the
only
other
thing
I
think
like
tricky
part
to
this
is
if,
if
we
use
like
a
decorator
on
on
like
classic
on
the
classes
and
stuff
like
that,
will
that
protect
like
the
init
and
all
the
functions
or
you
have
to
decorate
all
the
functions
individually?
I
don't
know
I'm
just.
A
Okay,
good,
so
please,
if
someone
else
is
connector
radius,
this
pr
all
right
what
else?
Okay,
we're
running
filters!
A
Oh
yeah!
This
is
the
what
I
was
just
referring
to,
that
the
warnings
module
has
some
mechanism
to.
A
A
Yeah
yeah:
that's
right!
I'm
not
sure
if
this
works
for
custom-made
warnings,
because
I
think
I
tried
once
to
define
a
warning
and
and
to
define
it
like
this
or
somehow
like
this,
but
I
haven't
played
that
much,
but
all
right,
okay!
Well,
that's
pretty
much
it!
So
I
don't
know
if
anyone
else
has
some
topic.
They
want
to
discuss
about.
A
Nope,
oh
by
the
way,
aaron
is
the
next.
C
C
A
A
Yeah
because
I
was
just
in
the
instrumentations
meeting
and
I
think
they
they
are
going
to
skip
the
meeting
of
next
week,
and
maybe
maybe
we
should
do
the
same.
I
don't
know
how
people
feel
about
it.