►
From YouTube: 2021-03-31 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).
C
B
Eh
yeah,
I
talked
with
dan
from
dining
trace
and
he
he's
on
eastern
time,
so
it's
7
p.m.
For
him
right
now,
so
I
think
that
he
said
that
until
he
actually
is
able
to
get
the
permission
to
open
source
it
from
his
manager
that
he
probably
would
skip
out
on
on
this,
and
that
we
could
just
like
discuss
more
generally
how
we
wanted
to
approach
it
and
everything
so
yeah.
D
B
Yeah,
so
I
guess,
let's
see:
okay
well,
I
just
pinged
display
so
that
he
was
at
the
absec
meeting
yeah.
So
at
the
hotel
sig
this
morning
for
javascript,
I
brought
up
your
pr
for
lambda
instrumentation
and
dan
daila,
the
javascript
maintainer.
B
He
mentioned
that
he
had
already
actually
written
a
form
of
lambda
instrumentation
for
the
javascript
sdk
that
they
were
using
internally,
but
that
he
just
hadn't
gotten
around
to
open
sourcing
it
within
for
for,
like
the
js,
contrib,
repo
or
anywhere
just
because,
like
bureaucracy
and
whatnot,
he
didn't
really
have
the
time.
B
But
he
said
he
said
that
it's
definitely
a
different
approach
than
what
we
take
and
the
way
that
he
described
it
was
that
they
instrument
the
underlying
rapid
client
that
the
lambda
runtime
uses,
which
which,
like
frankly,
I
don't
even
know
how
they
found
out
that
much
about,
like
the
undocumented
interventions,.
D
B
Yeah
right
so
yeah,
so
he
said,
like
the
benefit
that
the
rapid
client
approach
offers
is
that
there's
no
is
that
they
have
like
there's
no
frozen,
trace
issue,
there's
no
or
frozen
environment
issue
like
they
have
a
100
like
guarantee
of
sending
segments
before
the
environment,
freezes
or
sending
spans,
and
so
they
don't
need
to
like
worry
about
force,
flushing
which
which
sounded
interesting.
B
But
again
it's
of
course
yeah.
It's
taking
it.
E
D
D
D
D
B
Yeah,
but
I
wasn't
sure
like
so
like
dan
said
that
he
would
basically
like
he
said
there
was
nothing
blocking
him
from
open
sourcing,
their
lambda
interpretation,
apart
from
him,
just
bugging
his
manager
a
little
bit
more
to
go
through
the
paperwork
or
whatever,
and
so
they
he
said
that
he
would
try
to
get
that
done
and
kind
of
potentially
make
a
ptr
for
that
as
well,
so
that
we
could
kind
of,
compare
and
contrast
the
two
approaches,
yeah
and
so
yeah.
B
I
guess
for
consistency's
sake,
between
sdks
I
I
kind
of,
and
also
for
the
very
real
reason
of
not
wanting
to
take
a
dependency
on
the
internals
of
lambda.
I
kind
of
said
that
like
we'd
probably
be
in
favor
of
our
approach,
but
of
course
it's
I
have
not
seen
his
approach
or.
A
E
B
C
A
E
C
A
C
E
C
Morning
we
got
some
information
from
we
also
a
developer.
An
external
developer
is
working
on
node.js
from
the
instrumentation
and
crazy
daniel.
B
B
A
It's
definitely
blocking
until
we
resolve.
You
know
what
the
differences
are
with
the
implementation
that
daniel
has
done.
So
I
think
that
we
do
need
to
I
mean
I
can
reach
out
to
daniel
and
ask
you
know,
set
up
a
group
meeting
for
us
so
that
we
can
walk
through
that
or
we
can
do
it
in
the
next
week's
big
meeting.
Whatever
works.
B
Yep
yeah,
as
long
as
he
can
get
the
his
implementation
open
sourced
as
soon
as
possible.
Then,
since.
E
E
A
A
A
Please
provide
some
of
that
detail
on
the
guidance
on
on
an
issue,
because
it's
just
that
as
other
developers
come
in
and
you
know
larger
community
uses
what
what
we
are
building
it's
it's
long-term
documentation
and,
and
also
the
other
thing,
is
that
I'd
like
to
kind
of
also
see
some
of
our
security
guidelines.
You
know
being
formally
posted.
You
know
so
that
the
larger
community
is
aware
of
it
right
as
they
build
out
more
support
in
different
languages
for
lambda
players.
D
A
You
know
these
are
the
design
tenets
or
the
guidelines
that
we
are
keeping
in
mind
while
building
out
the
gis
implementation-
and
you
know
going
forward
for
others.
B
Yeah,
you
could
probably
just
copy
over
the
one
pager
that
we
wrote
for
the
abstech
review
it
just
for,
like
the
design
of
the
js
specific
one.
A
Yeah
yeah
yeah,
I
mean
again
you
both.
You
can
collaborate
on
that
and
just
have
issue
for
that,
because
otherwise
you
know
it's
like.
As
dan
I
mean
my
concern.
Is
that
also,
if,
as
daniel,
you
know,
submits
his
implementation,
I'd
like
to
kind
of
leverage,
you
know
any
of
the
best
parts
from
there
being
able
to
actually
have
a
more
integrated
solution.
If
that
makes
sense
right
I
mean
again,
we
may
be
totally
right
or
we
may
not
be
completely
right.
A
D
A
Oh,
this
is
our
our
dog,
okay
cool.
You
wrote
it
like.
So
all
right
I'll.
Do
that
that's
an
action
item.
Anything
else
we
wanted
to
cover,
given
we
don't
have
other
four
members
joining
in
today-
should
definitely
poke
them.
Before
this
call.
A
Did
anyone
update
the
work
workdoc,
the
word
doc,
I
don't
know,
let's
make
sure
that
it
is
updated.
Let
me
get
a
link.
A
C
A
A
C
C
A
C
Okay
and
today
I
noticed
that
someone
asked
a
jssdp
question
in
aws
hotel
channel
and
then
I
noticed
that
the
trace
provider
has
no
first
flash
interface.
Yet
there
is
false
flashing
processor,
but
not
in
provider.
So
I
suppose
knowledge
still
has
something
different
with
other
language.
D
C
D
There's
nothing
about
that
in
the
spec.
Generally,
it's
just
class
path
like
if
it's
there.
It's
automatically
used.
D
A
D
C
Thing
right
in
london
python
I
found
that
I
cannot
add
detector
into
provider.
If
I
add
this
sentence
as
this
code,
it
will
require
that
it
does
not
support
modify
provider
because
they
already
use
imagine
variable
configuration
if
using
a
very
configuration.
We
cannot
use
code
to.
C
D
C
D
A
C
So
yesterday
I
said:
how
do
we
maintain?
How
do
we
manage
the
downstream
level
for
lambda?
Well,
that's
the
suggestion
from
analog
that
we
can
use
data
tool
some
module
with
some
audio
yeah.
We
can,
I
think
you
can
solve
this
problem.
So
in
this
case,
if
the
dependency
is
source
code,
not
like
the
java,
it
will
say
the
dependency
is
the
goal
module
or
java
library.
A
Cool
all
right,
I
think,
let's
wrap
it
up.
Then
let's
get
back
30
minutes
and
then,
with
that
later,
all.