►
From YouTube: 2021-12-16 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
Oh,
you
went,
I
think
you
got
muted.
C
Yeah,
okay,
that
was
in
front
of
my
computer,
but
yes
forgot
to
I
mean
I
just
disconnected
oh.
D
D
C
Yeah
yeah,
I
I
have
appeared
that
it
in
fact
was
just
approved
now
by
cheggy,
so
yeah
it
I'm
still
not
sorry,
that's
working
in
all
cases.
I
found
a
bug
with
some
specific
scenarios,
but
I
think
it
it's
much
better.
Now
yeah,
as
I
am
using
in
my
product,
I
can.
I
also
find
some
so
this.
B
Is
there
this
was
the
one
where
you
know
you
had
that
yeah
the
context.
C
C
B
C
C
C
B
You
share
your.
Can
you
share
your
xcode.
I
think
that
might
be
easier
to
follow
yeah
yeah,
because
what
you
changed,
I
think
we
can.
C
Okay
yeah:
this
is
another
yeah
about
the
thing
is
here:
we
have
the
context
manager.
We
have
this
protocol,
so
it's
a
the
generic
protocol
that
we
will
use
and
we
were
using
the
activity
context
manager
that
it
was
using
whenever
a
new
context
was
set.
It
was
in
the
os
activity,
get
identifier
to
get
the
current
system
activity.
C
B
Yeah,
the
os
activity,
the
one
that
is,
the
library
that
you're
using
right
too.
C
I
have
seen
some
really
strange
behavior
that
sometimes
it's
working
somehow
so
I
am
still
investigating
it's
improving
now,
but
so
what
what
I
have
now
is
that,
apart
from
this
this,
I
also
have
implemented
another
context
manager.
That
is
the
task,
local
context
manager.
So
what
it
does.
It
defines
the
local
value
that
we
have
in
the
in
the
stack
of
the
task.
B
C
C
B
To
that
yeah,
but
I
think
but
baggage
can
be
something
else
right.
It
could
be
from
a
different
distributory
store
right.
It
can
yes.
C
C
So
so
you
can
set
yeah.
You
can
set
current
baggage,
remove
baggage
and
do
whatever
you
want.
So
in
some
how
it
it
works.
Similarly,
to
the
expanse,
because
you're
gonna
have
childhood
baggages
and
with
more
information
and
that
stuff,
so
it's
a
bit
yeah.
I
don't
think
there
is
lots
of
uses
of
such
a
complex
thing,
but
yeah
the
spec
says
about
it.
B
Yeah,
so
I
I
was
told
you
know
you
can
actually
have
like
a
baggage
that
is
associated
with,
let's
say
an
infrastructure
right.
So,
like
you
know
you,
so
you
could
yeah
like
a
swift
on
the
server.
There
could
be
a
trace
on
that,
but
in.
C
All
the
generic
information
you
want,
so
it
goes
with
the
trace
from
to
remote
servers
and
you
can
recover.
You
can
refill
things
you
can.
B
C
So
whenever
it
recovers
your
network
request,
it
has
extra
information
that
can
use
for
other
things
like,
for
example,
imagine
you
are
starting
a
network
request
from
a
test,
so
you
want
to
identify
that
that
trace
is
from
a
test,
and
you
want
that
information
to
move
along
all
your
network
request
or
your
databases
and
that
stuff,
so
the
baggage
will
be
the
place
to
put
that
information
associated
with
the
trace.
C
C
So
it
has
some
yeah
depending
on
where
it's
running
it
could
have
different
values,
because
you
you
can
be,
for
example,
if
you
want
to
detect
from
what
path
network
requests
appear,
for
example,
you
would
also
add
it
to
the
baggage.
So
it's
very
flexible.
B
To
add
whatever
you
want,
I
think
I
think
this
is
definitely,
I
think,
a
way
to
add
additional
stuff
right,
bigger,
more
amount
of
data
and
context,
because,
instead
of
putting
it
like
in
a
header
or
something
because
header
you
know,
you.
A
C
Baggage
yeah
packages
are
transmitted
with
the
headers.
Yes,
they
have
a
format
in
the
header
and
it's
transmitted
with
the
headers
in
the
network
request.
Oh
so
it's
not
in
the
payload,
it's
on
the
no
it's
in
the
it's
in
the
headers,
the
same
way
that
the
span
context,
the
trace
id
and
the
span
id
is
transmitted.
C
It's
in
another
header,
just
with
a
with
a
w3c
format.
Also,
but
baggage
can
be
pretty
big
right.
So.
C
I
mean
it's
not
a
way
to
send
images.
For
example,
I
mean
it's
like
you
want
some
small
information
that
probably
quality
of
or
some
quality
from,
the
trace
of
how
it
began
or
or
what
happened
in
between.
Maybe
you
just
want
to
say
that
these
trades
must
be
saved
all
along
you're.
You
know
you
are
just
monitoring
something.
Do
you
want
this
trace
to
always
be
safe?
So
you
you
could
set
that
in
the
baggage
and
all
the
elements
in
the
chain
could
act
in
in
that.
C
Imagine
the
same,
you
are
running
some
tests
and
they
are
getting
to
your
production
backend.
So
you,
you
are
testing
some
errors.
So
if
you
are
testing
against
production,
for
example,
you
and
you
are
testing
that
the
production
reaches
an
error.
You
don't
want
that
error
to
be
locked
to
your
system,
for
example,
or
to
page
your
developers,
so
you
send
in
the
baggage
that
that
suggests
and
should
not
be
a
considered,
a
real
error.
So
you
could
avoid
you.
Could
you
could
test
in
production
without
noisy?
C
B
That's
right
tag
that
is
passed
across
the
whole.
The
whole
trade
yeah
all
of
the
spans
and
entries
yeah
yeah
make
sense
okay.
So
so
then,
so
you
have
task
local
context,
manager.
C
Yeah
this
is
the
this
is
the
value
that
is
will
be
stored
in
the
task
when
a
task
is
created,
it
will
create
this
both
values.
It
has
also
other
custom
local
values,
but
you
can
define
here
with
which
values
more
you
want
to
have,
and
so
it
will
create
this,
and
the
thing
I
do
is
that
when
I,
for
example,
it
it's
only
created
when
a
task
is
created,
but
we
also
are
creating
a
stance.
C
We
can
create
different
expanse
inside
the
same
task,
so
we
are
not
pairing
the
task
with
the
spans
that
that's
what
we
do
with
the
activity.
We
are
creating
activities
when
we
create
a
span,
so
all
the
logic
is
handled
by
the
system,
but
for
this
we
cannot
create
the
tasks.
We
cannot
create
this
memory.
So
what
what
it
does
is
when
you
create
a
child
task,
it
copies
the
task,
the
values
of
the
parent.
C
It's
a
it's,
not
a
reference,
so
it
will
be
copied,
so
it
will
copy
to
the
child
and
we
we
can
remove
a
span.
So
if
we
have
created
several
spans
inside
the
task,
we
have
added
several
spans,
so
the
things
that
happen
here
that
the
array
grows
with
all
the
expands
and
each
time
you
end
the
span,
it
will
remove
that
from
the
current
span.
D
C
C
C
That's
the
reason,
so
you
can
have
several
expansion
a
task,
but
you
cannot
have
parallel
expanse
running
synchronously
because
you
will
have
another
task
that
will
duplicate
the
current.
The
current
queue.
C
Yeah
it
will
get
duplicated
the
array
yeah
or
the
queue,
but
not
the
expanse
response
will
be
as
they
are
objects.
They
will
only
keep
the
reference
that
that's
the
idea
that
they
tried
to
implement.
C
Yeah
and
then,
and
then,
as
you
can
have
both
activities
and
tasks,
that's
where
things
get
really
confusing,
because
you
can
start
having
activities
and
you
can
create
tasks.
So
what
happens?
Is
that
you
don't
know
when
you
are
evaluating
the
code?
If
you
are
inside
a
task
or
you
are
in
activity,
so
the
best
thing
you
can
do
to
identify
that
you
are
in
a
task
is
try
to
create
an
activity.
C
C
Okay,
so
that's
what
I
try
to
implement
here,
so
it
all
that
is
between
ifs,
is
the
task
code.
Initially,
I
was
supporting
xcode
13.13.03.1.
C
That
would
be
this
code,
so
it
imports
concurrency,
but
with
swift
miner
than
5.5,
and
this
one
is
for
xcode
13.2
or
up,
but
I
think
that
we'll
probably
delete
this
code
and
we'll
move
directly
to
this.
So
if
you
want
to
use
what
is
the
difference
between
the
two
looks
yeah
this
yeah,
this
one
yeah?
It's
because
swift
doesn't
let
you
do
it
clearly,
so
this
one
allows
you
to
run
concurrency
code
in
mac,
os,
10.15
or
ios
13,
but
before
xcode
13.2.
C
C
So
I
was
thinking
of
moving
only
to
this
code,
because
now
it's
public,
this
version
of
xcode-
and
we
don't
have
this
nasty
code
duplicated
here-
that
only
can
create
difficult
things,
and
also
here
we
have
everything
duplicated
twice,
just
because
of
the
version
so
yeah
I
was
thinking.
Probably
I
will
change
it
today
and
I
will
yeah
that
when
I
merge
the
pr
I
will
remove
this,
I
will
try
to
go
only
with
one
version
of
xcode
that
supports
it
and
we
say
it's
yeah.
C
We
say
that
if
you
want
to
use
that
you
have
to
use
xcode,
13.2
and
not
use
concurrency
before,
because
I
also
have
seen
some
strange
behavior,
like
previous
xcode
versions,
didn't
run
the
same
way
than
new
versions
even
in
the
new
system.
So
I
have
seen
some
strange
behavior
there
so
yeah.
I
was
thinking
on
just
force
it
to
be
this
person
and
not
support
previous
persons,
because
it
was.
C
That's
right,
so
we
have
a
yeah.
So
here
we
have
a
context
manager
that
uses
the
other
when
it
thinks
that
it's
not
useful.
So
when
it
yeah,
when
it
certain
sets
the
correct
context,
it
tries
to
know
if
it's
an
activity.
C
C
Yes,
if
you're
in
a
task,
it
should
return
zero,
but
I
have
seen
that
sometimes
it's
not
returning
zero,
depending
on
how
the
task
is
created,
so
that
that's
a
bit
yeah
difficult,
so
probably
create
activity
context.
It
really
returns
zero.
C
Yeah,
if
I
can
create
it
yeah,
probably
this
logic
will
be
better
with
creating
instead
of
getting.
I
will
try
also,
so
if
you
create
a
new.
B
C
C
Also,
so,
if
you
try
to
create-
and
it
returns
thera
that
that
zero-
that
means
you
are
inside
the
task,
so
we
use
the
task,
local
context
manager
and
we
call
this
method.
If
not,
we
create
the
activity
with
activity
map,
as
we
did
as
we
did
before
so
yeah
yeah.
Probably
I
will
try
to
create
this
before
and
instead
of
checking
this,
I
will
try
to
check
this,
because
I
don't
think
I
am
using
this.
C
C
B
C
C
And
the
same
for
removing
we
try
to
remove
if
it
exists
in
the
the
list
that
we
keep
for
activities,
we
will
remove
it
if
it
doesn't
exist.
C
B
So
you
don't
have
to
you,
don't
have
to
when
you
remove
it.
Does
it
just
close
that
whatever
that
span.
C
C
So
let's
remove
it's
automatically
closed.
It's
when
it's
close,
it's
automatically
removed
yeah,
that's
right!
So
so
this
is
the
code
and
also
some
tests,
but
I
am
still
not
sure
about
everything
that
I'm
doing
here
is
working
as
respect,
because
there
are
some
I
I
have
seen
different
results
with
different
compilers
yeah.
So
it's
a
very
I
I
don't
think
it's
finished
in
code.
I
mean,
I
think
they
have
some
issues.
Sometimes
that
is
not.
C
They
don't
have
repeatable
working
methods,
because
I
remember
that
initially
this
get
identified
inside
the
task
was
always
returning
nil,
but
in
one
of
our
tests
we
test
that
it's
not
nil,
and
it's
not
nil.
So
it's
inheriting
it
from
the
parent.
If
it's
a
task,
so
that's
something
that
probably
they
fixed
without
without
telling
anyone.
So
we
have
here
one
of
the
tests.
C
B
Yes,
so
some
other
stuff,
I
think
you
have
to
spend
time.
You
know
with
this
code
to
understand
what
all
this
yeah
it's.
C
It's
it's
quite
convoluted,
yeah,
because,
with
the
activity
context,
what
we
were
doing
was
we
were
creating
activities
with
the
spans.
So
we
had
one
one
relationship
between
spans
and
activities.
C
So
that
could
work
very
easily
because
we
created
the
activity
and
we
just
get
the
activity,
so
we
we
knew
where
we
were,
which
one
the
span
related
to
that,
but
with
these
tasks
as
we
don't
control,
when
tasks
are
created
because
they
are
created
explicitly
in
code
like
this,
we
cannot.
C
Create
them
ourselves,
maybe
that
will
be
a
way
to
work.
I
mean
creating
a
task
ourselves
and
run
everything
inside
that
task,
but
that
will
duplicate
execution
context
for
the
user,
and
that
will
be
really
disgusting
because
it
implies
execution
right
and.
C
C
Yeah,
because
you
are
changing
the
way
code
executes
and
you
are
duplicating,
I
mean
tasks
being
executed,
yeah
that
doesn't
look
like
the
proper
solution,
so
I
was
trying
to
implement
here
with
with
this
queue.
B
Okay,
all
right,
so
I
should
spend
time
on
this
context
manager
code
to
understand
that
a
little
better.
C
Now
it's
not
very
understandable
anymore.
I
think
all
right
once
you
clean
up
the
yeah
yeah.
If
I,
if
I
removed
all
the
touch
local
thing,
there
will
be
less
branching,
it
was
much
more
direct
but
yeah.
It
changed
a
lot
with
this
because
you,
you
have
different,
you
you,
as
you
don't
know.
If
you
are
here,
if
you
are
inside
an
activity
or
inside
that
task,
you
must
handle
both
every
time.
C
Okay,
yeah,
maybe
I
could
try
to
find
other
ways
to
know
it.
Maybe
because
here
logic
doesn't
look
like
really
strong.
B
What
about
logs
are
getting
the
spec?
I
saw
that
you
know
they're
implementing
logs
and
some
of
the.
C
Yeah,
that's
right,
yeah!
I
I
think
we
we
we.
We
should
work
towards
that
yeah
I
I
am
currently
we
we,
I
was
using
span
events
as
locks,
so
I
was
converting
spans
to
lock
or
span
events
to
locks
for
my
users,
because
I
needed
some
some
logging
information
and
I
was
doing
that
through
through
the
span
events.
C
A
B
Yeah,
but
I
think
we
you
know,
I
think,
is
tough,
as
I
think
there
are,
people
will
start
using
it
right
if
they
come
in.
C
Yeah
with
the
new
xcode
version
that
supports
all
the
three
three
different
system
operating
system
versions
that
that
will
be
used
very
soon
so
yeah.
We
must
try
to
have
a
good
solution
for
them
that
works
at
least
for
most
of
the
cases.
I
I
we
cannot
probably
solve
all
the
problems
because,
as
as
you
see,
is
truly
orthogonal
to
expanse
and
if
the
way
that
a
is
implementing
this
for
the
for
the
tracing
is
that
you
have
to
automatically
add
the
values
to
the
task.
C
C
Explicitly
in
the
code-
and
we
I
don't
want-
I
mean
we
cannot.
We
cannot
do
that
because
we
are
outside
the
language
and
we
we
we
have
to
use
another
thing.
C
We
support
one.
We
support
we
support
in
the
importers,
we
have
a
switch
metrics,
so
they
have
this
metric
library
that
we
are
mapping
to
our
this
sweet
metric
is
a
apple
library
that
yeah
include
some.
I
don't
know
where
it
is
yeah,
they
have
this
matrix
factory
stuff
inside
their
library,
and
we
are
mapping
that
there
is
another
for
tracing
that
we
might
also
move
to.
So
these
are
just
the
device
metrics
right.
B
You
know
like
whatever
the
cpu
one.
C
Oh
no,
no!
This
is
a
metrics
library
that
apple
implemented
in
swift,
okay,
generic.
This
is
not
generated
by
the
system.
They
have
some
metric,
they
have
also
a
metric
kit.
That
is
a
library
that
gives
you
information
about
your
device,
but
this
is
a
matrix
library
that
they
wrote
from
from
xero,
and
just
you
can
store
metrics.
B
C
B
But
there
is
yeah
they
they
have
another,
whatever
extension
to
using
this
api
to
generate
like
device,
metrics
and
so
on,
that
is.
C
Yeah
yeah
so
yeah
and
yeah
they
have
another
for
tracing,
but
the
way
they
pass
context
value
with
the
tracing
is
the
same
with
than
they
usually
task
so
explicitly
adding
the
values
when
you
call
so,
we
could
also.
B
D
C
C
C
C
C
C
But
they
don't
have
the
open,
telemetry
api.
I
mean
it's
just
the
you
can.
You
cannot
use
the
api
here
with
this.
It's
on
only
the
format
for
with
the
information
there,
so
they
can
convert
from
their
distributed
tracing
format,
to
open
telemetry
and
sent
to
an
open,
telemetry
collector,
but
they
are
not
implementing
the
api.