►
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
A
B
Yeah
we
have
today
a
hackathon
in
my
company
today
and
tomorrow,
okay,
so
yeah.
I
I
I
almost
get
late
to
this
meeting,
because
I
was
too
focused
on
my
my
hackathon
project.
A
Madrid,
okay,
so
you're
seven
hours
ahead.
B
A
Yeah
yeah
now
what
happens
is
there's
so
many.
You
know
conflicting
meetings
and
so
on,
and
then
I
have
a
bunch
of
stuff.
I
need
to
do
for
aws
agreement.
B
B
Nothing
from
my
site-
yes,
sir,
okay
yeah,
my
internet
is
not
working
very
well
and
I
am
at
my
office,
my
company
office
in
madrid,
I'm
not
at
home.
I
have
a
worse
connection
here.
Oh
really,
wow
yeah,
it
looks
so
I
mean
I
don't
know
why.
I
think
the
wi-fi
is
not
working
right
in
this
area.
I
came
to
a
meeting
room
and
it's
not
working
very
fast
here.
It
looks
but
yeah,
okay,
so
it
looks
like
rice
is
not
coming
today.
A
B
We
we
have
instagram
metrics
supported
for
prometheus
and
now
tlp.
Currently,
I
will
say
so.
They
approve
okay.
B
Yeah
there
is
one
issue,
because
I
have
to
bring
that
to
the
data
exporter
on
it
yeah.
I
have
no
time
for.
B
Yeah
for
for
this
week,
I
have
been
working
quite
a
lot
in
the
automatic
context,
handy
branch,
that
I
think
that
bryce
was
going
to
play
with
yeah.
But
let.
A
B
B
They
have
an
implementation
based
on
having
it
on
the
stack
of
the
methods,
so
it's
transmitted
using
the
stack,
so
you
have
to
create
and
you
have
to
create
a.
B
You
store
that
in
the
stack,
so
you
create
a
task
and
whenever
you
call
it,
you
create
the
stack
with
the
custom
properties
and
you
cannot
move.
You
cannot
modify
the
adapter
and
the
thing
is
that
we
we
would
like
to
be
able
to
create
that
when
we
start
a
spam,
so
we
could
set
our
context
there.
So
any
method
that
it's
called
after
that.
We
will
be
able
to
receive
or
read
our
context,
but
I
didn't
find
any
way
for
doing
that.
A
So
that
that
is
so
okay,
I
don't
remember
now
how
you
did
the
network
instrumentation.
I
thought
it
articularly.
Does
that
right?
The
span
context
is
yeah
currently.
B
In
our
current
code,
we
we
are,
we
are
creating
now
context
activity,
context,
manager,
yeah
this
one.
Currently,
we
we
we
are
whenever
we
create
a
span,
we
set
the
context
in
the
current
scope.
B
And
we
read
the
we
use
something
called
activity
manager
or
the
activity,
so
we
we
get
a
numeric
value
that
the
system
moves
between
threads
and
queues
and
tasks.
So
whenever
you,
you
can
get
your
current
number,
let's
say
so,
and
you
can
also
modify
your
current
number.
So
all
your
childs
will
inherit
it.
B
We
had
this.
This
context.
Map
identified
our
activity,
our
current
it
for
the
task,
and
we
set
here
the
span
context
or
the
baggage
context.
So
whenever
we
created
a
spam,
we
created
we
created
this
context,
yeah
we
created
it
and
assigned
to
that
table,
but
once
we
come
to
the
concur,
the
new
concurrency
world.
That
is
something
that
you
see
it
can
it's
more
advanced
than
my
branch.
The
key
point
is
that
we
we
cannot
modify
this
value
whenever
we
modify
it.
We
will
have
here
just
a
method
to
modify
it.
B
B
B
I
don't
currently
don't
have
a
clear
way
to
to
support
it.
I
created
this
context.
Manager
for
start
an
activity.
You
create
a
queue
you
create
another
another
span
and
just
validate
that
the
context
is
good
before
creating
the
span
and
also
after
these
kind
of
things.
But
whenever
we
get
to
the
async
world
things
doesn't
work
doesn't
automatically
create
the
task
task,
local
values-
and
I
couldn't
I
have
this
test
here-.
B
A
You
sorry
this,
so
you
have
this,
you
know
this
context
will
carry.
A
A
The
philosophy
is
to
keep
the
api
not
have
any
implementation
right.
B
B
We
will
have
this
common
context.
We
have
this
context
manager
class
that
just
you
can
get
the
current
context,
value
the
current
context,
value
and
remove
one
context,
value
yeah.
These
are
the
three
methods
we
are
implementing.
The
idea
for
it
is
that
also,
for
example,
someday
linux
could
support
it.
So
we,
whenever
we
create
a
span,
we
set
this
current
context,
value
for
a
span
and
when
a
span
ends,
we
remove
the
context
value
for
the
span
and
whenever
you
want
to
know
who's
that
we
call
this
get
current
context
value
for
this.
B
So
we
have
this
method.
That
is
the
one
that
was
currently
working
without
these
task:
local
things
that
so
that
was
working.
It
was
created
when
you
said
current
context,
which
you
were
creating
this
associated
in
your
span.
B
It
was
yeah
yeah
and
that
that
was
yeah
working,
but
as
we
cannot
modify
the
local
thing
one,
because
it's
on
the
stack-
and
the
key
point
is
that
the
stack
is
only
created
is
another
task
created.
So
whenever
we
create
a
span,
we
are
not
creating
a
task,
so
we
cannot
modify
the
task
value.
B
B
The
only
thing
I
can
think
is
creating
a
span
being
another
async
thing,
so
we
can
set
it
that
could
work.
I
I
just
thought
about
it.
If
we
modify
the
api
and
each
start
span
is
a
task
itself.
A
B
Yeah
this
this
is
using
this
task.
This
is
all
all
new
from
echo13
and
recently
supporting
ios
13
and
up
in
the
latest
beta
is
special.
B
B
A
B
Yeah,
but
this
is
user
code
and
we
cannot,
and
if
the
user
instead
of
this
says
or
a
starter
span,
we
want
to
set
this
value,
so
we
can
get
here
the
current
span,
for
example,
inside
the
code,
but
we
can
because
it's
close
to
this
value,
so
the
task
local
only
lasts
this.
In
that
context,
yeah
so
yeah.
I
don't
really
know
how
to
how
to
do
that,
because
yeah,
even
if
they
start
a
span,
they
should
start
the
span
here
and
set
the
value
here
and
have
this
local,
it's
crazy.
A
To
so
this
doesn't
respond
with
anything.
There
is
no
there's
nothing
that
it
can
respond
with.
It
isn't.
So
when
the
task
is
finished,.
B
B
A
B
And
remove
the
value
here,
because
the
value
only
leaves
this
time.
So
you
cannot
never
end
the
value
here
so
that
that's
yeah
they
made
it
like
this,
so
they
can
just
use
the
stack
and
then
leak
memory.
And
that's
really
nice.
You
don't
have
to
handle
the
memory
because
the
compiler
does
it
for
you.
You
don't
have
to
copy
values
in
in
the
heap,
because
the
compiler
just
save
it
on
the
stack
and
really
move
it
whenever
it,
but
for
the
rest
is.
B
B
B
I
yeah,
I
don't
know
yeah,
I
don't
know
how
to
call
it
like
this
from
two
different
methods,
how
I
and
I'm
being
in
another.
Do
you
know
what
I
mean
I
want
to
win
in
the
start.
I
want
to
run
this
in
a
start
in
spanish
start,
and
I
want
to
run
this
in
a
span
end.
A
B
B
A
A
B
B
B
B
We
we
have
no
way
to
pass
the
context
in
the
methods,
because
the,
for
example,
the
network
library,
doesn't
support
setting
the
cons
the
context
from
outside,
or
things
like
that.
B
B
A
B
So
it's
it's
really
difficult
to
find
a
way
to
modify
and
it's
in
the
stack.
So
you
cannot
play
with
with
the
code
stack
so
easily.
Yeah,
okay,
yeah,
just
just
crying
about
my
problems
with.
A
You
I
was,
I
was
looking
at
the
proto
proto
as
well.
Proto
project
open,
telemetry
proto.
They
have
directions
for
all
the
other
languages,
but
nothing
for
swift.
B
B
Now
clients
were
not
really
used,
except
now
for
ram
instrumentation.
So
now
I
I
think,
having
real
user
monitoring
for
mobile
is.
There
is
a
market
there
and
a
lot
of
interest
so
yeah.
A
That
I
I
asked
a
question
there.
You
know,
because
there
was.
I
had
worked
on
something,
maybe
a
few
years
back
on
an
application
which
was
which
had
lots
of
iot
devices.
That
was,
you
know
sending
telemetry
to
like
a
you,
know:
handheld
device,
okay,
which
is
ios
or
android,
but
you
know
the
iot
device
itself
was
based
on
the
qpc
plus
plus,
so
it
would
collect
like
temperature,
and
you
know,
quality
of
oil
and
so
on,
and
then
and
then
the
idea
was
from
the
handheld.
A
So
it
collects
all
this,
you
know
and
then
it
would
send
this
over
to
the
you
know.
It
collects
the
traces
metrics
and
so
on.
So
my
question
was
you
know,
which
one
do
you
call
as
a
client
spam
here
right?
It
is
because
you
you
know
based
on
so
so
these
days.
You
know
the
client
can
be
written
not
just
in
mobile
or
web,
but
it
could
also
be
written
in
like
rust
or
c,
plus,
plus
or
q,
t
c,
plus,
plus
and
so
on,
yeah.
So
those
are
all
client.
A
A
I
mean
they
are
still
building
some
spec,
so
so,
if
you
have
spans
coming
from
so
the
client
typically,
we
think
of
it
as
a
rum
and
mobile
clients.
A
But
you
know
in
this
some
scenarios
like
this,
where
you
have
lots
of
devices
sending
things
to
you
know
some
kind
of
aggregator
and
then
sending
it
to
you
know
it's
not
running
on
some
cloud
servers
right,
because
these
are
all
things.
So
this
is
actually
the
scenario
was
like
you
know,
a
store
right.
A
It
could
be
a
retail
store,
you
know
having
their
own
kind
of
a
small
network
and
before
before
it
goes
out.
So
a
lot
of
these
stuff
now
are
also
coming
on
ios
android
technology.
Before
people
used
to
write
their
own
pos,
you
know
windows,
clients
and
so
on.
So
these
are
all
so
so
they're.
You
know,
I
think
they
had
something
called
a
device
or
something
for
in
the
spec.
A
A
Because
everyone
has
a
ipads-
and
you
know
some
on
item
and
stores.
You
know
that
is
looking
into
how
the
store
is
performing
and
then
that
in
turn,
talks
to
them.
B
A
To
copy
so
so
why
why
don't
we
have
the
proto
project?
Also,
you
know
include
swift
to
generate
the
because
they
have
it
for
pretty
much.
You
know
they
even
have
it
for
objective
c
yeah.
B
But
yeah
you
mean
the
protobuf:
no,
this
project.
Okay,
you
mean
the
proto,
the
open,
telemetry
protocol
project.
B
B
B
Folder
in
the
scripts
for
the
semantic
convention:
okay,
we
have
these
thumb
templates
and
we
have
these
semantic
attributes
with
j
2
and
the
generator,
and
we
generate
the
protobuf
with
that.
Okay,
okay,.
A
B
Yes,
that's
right:
we
we
download
the
the
specification
from
the
from
the
project.
As
you
see
in
the
script,
you
can
see
that
in
the
generated
script
I
just
we
just
check
for
the
version
that
we
want
in
the
script,
and
we
we
fetched
that
repo
update
our
our
our
version
and
we
create
the
docker
one.
We
do
that
just
to
avoid
doing
with
the
newest
thing
always
so
we
it
could
break
our
behavior
but
yeah,
and
for
this
yeah
it's
this.
B
We
are
using
this
with
the
docker
method
to
run
it.
So
we
we
are
not
using
the
generate.
B
B
B
Yeah,
okay,
yeah:
this
is
the
one
that
uses
for
the
tlp
yeah.
That's
right!
Sorry,
yeah
the
the
year
pc
libraries
are
supported
by
apple,
so
you,
you
must
use
the
apple
provided
tools
for
swift.
A
And
yeah,
if
you
look
at
the
proto,
you
know
they
have
support
for
all
these
languages
right.
We
should
add
that
here,
whatever
yeah.
A
So
yeah,
I
think
this
is
what
it
is
again
also
using
some
docker
to
run
the.
B
A
No,
I
think
you
know
you
should
so
you
know
it
actually
has
support
for
radioactive
c
yeah
yeah.