►
From YouTube: 2021-02-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
A
I
remember
yesterday
you
talked
about
we
can.
We
can
also
create
a
laminar
layer
for
java
execution,
vector.
A
Yeah,
that
sounds
good.
I
think
that
makes
sense.
Just
I
have
to
think
about
very
clear
that
can
I
enable
the
the
other
library
implementation
no.
B
C
B
B
D
Hello,
hey
hi,
hi,
hey
alex,
so
I
was
just
getting
the
google
docs
set
up
so
that
we
can
review
the
talk.
D
I
think
we
have
it
here.
Let
me
know
if
you
guys
can
access
it.
It's
still
some.
You
know
and
feel
free
to
add
comments.
A
D
Yeah,
I
think
it
would
be
good
to
kind
of
walk
through
that
right
because
unruh,
you
might
have
already
seen
it,
but
I
think
it
would
be
great
to
get
alex's
feedback
and
if
anybody
else
joins
in,
we
can
make
it
available.
You
know
on
the
for
review
on
the
on
the
repo
also
and
alex
again.
We
can
also
figure
out.
You
know
what
the
next
steps
are
today
on
lay
getting
his
hood
into
the
same
folder
as
we
discussed
last
time.
C
D
There
was
going
to
be
more,
I
think
I
think
I
think
there
is
in
the
sense
that
we'd
like
to
you
know,
make
sure
it
so
one
of
the
requirements
that
we
have
is
that
it
has
to
be
cleared
for,
for
you
know,
pushing
to
open
telemetry
from
our
open
source
compliance
team,
and
so
we
will
kick
start
that
process
so
lay
I'll
work
with
you
on
that
and
then
once
you
know
that
that
usually
takes
a
week
or
so
as
soon
as
it's
done,
then
we
can
just
file
push
the
code.
D
Is
there
alex?
Do
you
know
if
there
is
any
requirement
on
the
tc's
side
to
you
know,
push
the
code
or
can
we
just
do
prs
and.
C
C
D
Totally,
that
would
be
good
if
you
can
add,
anarch
lay
and
I
to
to
them,
and
you
know
we'll
make
sure
that
our
compliance
stuff
is
complete
and
then
just
push
all
the
code
there
under
the
python
folder,
as
we
had
discussed.
D
Okay,
so
should
we
just
spend
some
time
reading
through
the
doc
or
just
walking
through
it
alex?
Would
that
be
useful.
C
Yeah,
if
you,
if
you
want
to
walk
through
it,
that's
probably
going
to
be
the
most
useful
thing
here.
I'm
happy
to
also
review
it
afterwards.
After
the
meeting
yeah.
D
By
all
means,
I
mean
again
don't
want
this
to
be
comprehensive,
because
I'm
sure
that
we'll
you
know
it's
good
to
kind
of
ponder
over
certain
sections,
but
we
could
quickly
kind
of
just
walk
through
each
of
the
sections,
and
you
know
if
there
is
anything
which
is
glaringly
missing.
We
can
add
that
in
also
so
lady,
you
want
to
share
your
screen
and
kind
of
just
step
through
it.
D
A
A
And
then
I
introduce
some
technical
challenge
in
this
project.
The
first
thing
I
think
everyone
already
know
that
that's
lambda
freeze,
because
lambda
will
use
a
single
freezer
to
to
freeze
the
lambda
number
sandbox
if
there
are
no
new
requests
coming,
there's
a
reason
why
some
user
complaining
community
said
they.
They
say
the
telemetry
delay
if
they
run
open
elementary
in
london,
environment
and
the
so
I
also
give
the
short-term
solution
to
how
to
how
to
solve
this
issue.
Basically,
we
will
call
forth
flush
at
the
end
of
each
lambda
invoke.
A
A
Version
and
also
mentioned
about
because
the
lava
container
is
linux.
So
for
some
language
like
python,
we
should
build
the
lambda
layer
in
linux
platform,
so
we
can
use
docker
to
build
the
layer.
A
And
also
mention
about
the
this
is
a
definition
of
auto
instrumentation,
because
sometimes
we
might
mess
up
the
library,
instrumentation
and
the
auto
instrumentation.
So
far,
only
java
and
the
python
support
auto
instrumentation,
the
other
language
only
has
library
instrumentation.
A
So
the
library
instrument
means
customer
has
to
change
their
source
code
so
for
some
compiling
language
user.
If
user
change
their
source
code,
they
have
to
recompile
their
project
and
deploy
to
lambda.
So
in
this
case
we
would
not
provide
laundry
layer
for
customers
because
it
does
not
help
for
customers.
A
So
basically
in
logic,
we
will
add
three
layers
of
wrapper
on
customers.
Original
lambda
function
handler
that
this
lambda
function
instrumentation.
We
know
that
this
is
a
generalized
focusing
laminar
function
and
execution
wrapper.
This
is
very
language
specific,
so
in
java
and
python
we
can
use
execution
wrapper
to
the
user.
With
this
help
user
no
need
to
change
their
source
code
and
the
third
layer,
the
server
is
lambda
native
wrapper.
This
is
a
new
feature
provided
by
lambda.
A
A
A
C
A
A
I
mean
we
think
aws
is
for
along
the
layer.
Collector
will
be
enough
for
users
for
lambda
users,
so
ao
awt
straw,
collector
size
would
be
very
small.
So
far,
it's
just
around
20
megabytes.
So
we
want
to
use
adot
recorder,
adot
collector
in
this
popular
baselander
layer.
A
A
Yeah
this
part
just
introduced
what
I
said
before
so,
for
which
kind
of
case
we
will
provide
sdk
layer,
but
also
for
some
cases.
We
would
not
provide
sdk
layer
because
for
some
comparing
language,
sd
sdk
does
not
help
user.
A
C
Oh
yeah,
I
think
this
is
a.
This
is
a
really
good
overview.
Are
you
planning
on
putting
this
inside
inside
the
repo
itself.
D
Alex
because
again,
the
idea
is,
to
you
know,
kind
of
use
this
as
a
baseline
and
then
build
out.
You
know
more
detail
on
each
language
implementation
as
well
as
it
would
be
useful
to
actually
also
look
at
the
implementation
that
you
had
done
with
the
collector
right,
which,
which
might
be
worth
comparing
at
some
point.
D
And
are
there
any
key
areas
that
you'd
like
to
call
out
where
you
would
like
to
see
more
detail.
C
C
C
D
A
timeline
that
they
publicly
share.
A
They
have
no
timeline,
but
yesterday
I
received
emails
from
london
team.
They
talked
about
this
thing
because
our
pm
pushed
them
for
this
feature.
Their
answer
is
now.
They
already
list
seven
solutions,
but
now
they
narrow
down
to
two
one
of
solution
is
I
don't
even
another
solution?
Is
they
cause
an
aggregation
log?
A
I
don't
know
too
much
about
the
second
solution,
but
now
we
are
discussing
about
continue,
use
the
either
solution.
This
says
that
they
will
be
locked
on
the
final
solution
at
the
end
of
february.
After
that
they
will
agree
with
the
timeline
of
this
feature.
Okay,.
C
A
C
Yeah,
no
that's
fair!
I
I
don't
think
I
was
expecting
like
a
hard
time
timeline
here.
It's
more
of
a
general.
You
know
it's
just
a
thing.
That's
actively
being
discussed
or
not
so
yeah
yeah,
cool.
A
D
You
know
maybe
we
can
actually
alex
as
we
build
out
the
I
mean
I
was
thinking
that
you
know
given
we
have
outlined
some
of
the
languages
that
we'd
like
to
support
and
also
you
know,
kind
of
harden
the
collector
implementation.
Also,
maybe
you
know,
spend
some
time
on
really
building
out
the
design
and
also
collating
a
list
of
questions.
In
terms
of
you
know,
as
we
implemented,
we
also
have
questions
on
which
we
can
then
go
and
get
the
more
the
core
team
involved
right.
D
So
we
can
certainly
you
know,
pull
them
in
and
but
let's
kind
of
do
the
leg
work
that
is
needed
on
our
end
to
make
sure
that
we
can,
you
know,
leverage
their
time
then
and
rock
did
you
have
any
other
questions
specifically
because
I
think
we
can
probably
end
early
today
if,
if
books
are
not.
B
D
B
C
D
Where
did
you
add
it?
Sorry,
okay,
to.
D
Helpful
alex
to
maybe
you
know
kind
of
at
some
point-
I
don't
think
we're
there
yet
to
have,
and
more
often
maybe
plan
out
some
of
the
items.
You
know
that
we
need
to
build
out
and
itemize
what
we
need
to
build,
because
then
that
helps
us
also
add
more
engineering
to
working
on
the
projects
and
figuring
out.
You
know
I
mean
ideally
I'd
like
to
see
lambda
completeness.
D
C
Yeah,
so
I
guess
maybe
that's
a
an
item
we
can
take
as
like
doing
do
some
homework
ahead
of
time
for
the
next
meeting,
but.
C
Be
good
to
understand,
you
know
what
what
languages
you're
you're
planning
on
that
you
know.
Amazon
is
interested
in
adding
support,
for
I
know
from
our
side
we're
definitely
interested
in
the
the
core
languages.
So
you
know
like
the
go
python.
Javascript
java
are
kind
of
high
on
our
priority
list
and
then
trying
to
just
chunk
that
work
into
like
issues
we
can
create
here
and
then
we
can.
We
can
kind
of
plan
the
the
work
a
little
bit
better.
D
Yeah,
I
think
that's
a
good
idea,
and-
and
so
I
have
another
question
there,
anna
did
you
want
to
sorry
I'm
just
fixing
this.
Did
you
want
to
write
out
what
you
have
as
a
proposal
for
the
semantic
conventions?
Is
it
you
know
easier
to
propose
a
initial
draft
and
then
kind
of
iterate
with
the
charger.
D
A
Our
tier
rpm
mentions
that
python
node.js
at
the
java,
this
three
language
will
cover
most
of
lambda
user.
So
our
top
priority
is
to
support
this
three
language,
first,
so
python,
because
we
almost
finished
our
soft
work.
So
next
we
will
work
on
node.js
support.
D
Yeah,
that's
good.
What
we
can
do
is
that
we
can,
you
know,
as
alex
said,
we
can
go
back
and
you
know
create
our
list
of
items
that
we
need
to
track
as
issues
and
and
then
we
can
add
it
to
the
back
plug
on
the
repo
itself,
because
then
it
keeps
the
backlog.
D
C
D
C
I
think
this
is
this
is
good.