►
From YouTube: 2022-04-13 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
C
Let's
give
one
more
minute,
perhaps
zach
you
join
today.
I
know
robert
is
on
pto,
so
he's
not
joining.
C
C
All
right,
so,
let's
get
started
keeping
the
drive
to
release
this
beta.
We,
we
have
a
morgan
here
today
with
us,
and
one
thing
that
I
want
also
is
kind
of
as
soon
as
we
wrap
up
kind
of
get
some,
it's
a
beta
with
a
limited
number
of
instrumentations
but
kind
of
get
some
broadcasts
about
that.
So
we
get
some
feedback
and
usage
and
in
case
so
for
that
we
we
should
wrap
up
the
things
that
we
really
want
to
fix
for
next
week.
C
Basically,
next
week
is
waiting
for
the
sdk
to
have
a
stable
release,
but
on
top
of
that
release
we
just
publish
it.
So
let's
wrap
it
up
that
kind
of
last
steps.
Let's
see
prs.
C
I
think
there
is
no
controversy
here
about
renaming
the
stuff
from
the
test
from
samples
to
test
applications
in
the
original
issue.
I
mentioned
that
I'm
I'm
not
a
hundred
percent
convinced
about
rename
example
to
sample
and
actually
the
sdk
use
example.
So
let's
have
that
conversation
totally
separate
and
just
be
sure
that
I
think
we
shouldn't
do
anything
about
this
rename
before
the
beta.
C
You
know
we.
A
There
is
a
reason
I
know
of
why
sdk
adopted,
like
example.
Instead
of
samples,
we
have
a
sampler
and
sap
sampling
in
yeah,
so
that
confuses
a
lot
with
these
samples
whenever
people
read
about
it
or
when
they
search
for
it.
That's
the
reason
why,
like
sdk
adopted
examples
instead
of
samples-
and
I
recommend
we
keeping
in
that
way,
so
it
will
avoid
the
confusion
because
we
just
bring
the
sdk.
We
are
not
doing
like
a
different
work
here.
C
Yeah,
I
agree
with
that.
I
think
I
tend
to
find
confusing
the
use
of
sample
and
sampling
when
we
actually
want
to
show
kind
of
the
prototypical
case
of
the
thing.
That
is
actually
example
right
and
we
are
not
doing
sampling
in
any
sense
here,
so
I
I
think
it
gets
confused.
I
agree
with
that
right,
so
I
think
it's
better
just
to
keep
that
discussion
separate.
I
think
we
can
later
try
to
convince
fabrizio
about
our
perspective,
but
I
think
for
the
test
applications
itself.
C
It
should
not
be
controversial
if
someone
has
something
against
that.
Let
us
know
in
the
pr
you
know,
but
in
principle
I
I
don't
think
I
don't
see
anything
that
should
block
that.
C
So
fabrizio
did
a
lot
of
improvements
in
our
docs.
I
think
mostly
most
of
the
issues
that
were
here
or
addressed.
I
think
there
is
a
last
one
last
thing
from
chris.
C
C
Yeah
yeah,
I
think
it's
so
it
already
clarifies,
but
I
I
think
you
are
right
that
it
may
give
the
impression
that
we
have
kind
of
some
api
for
people
to
quickly
write
that
we
do
have
the
api.
But
the
api
needs
to
be
built
with
us
and
all
that
stuff.
We
don't
ship
api
for
people
to
do
that
so
yeah.
So
I
I
think
there
is
no
rush.
Fabrizio
is
in
other
time
zone.
C
C
And
then
we
have
a
bunch
of
bumps
of
virgil
beauty.
You
had
mentioned
about
this
stuff
about
examples
and
some
of
this
stuff
that
we
could.
I
just
wanna
be
sure
that
perhaps
I
I'll
try
to
go
over
this
today,
but
we
we
have.
C
Okay
and-
and
the
main
point
that
I
wanted
to
make-
is
that
I
closed
it
through
of
dance
because
they
were
trying
to
update
the
things
that
we
want
to
be
old
to
show
in
the
examples,
the
conflicts
and
this
kind
of
thing
you
know.
So
that's
the
only
thing
but
yeah,
let's
hold
off
all
those
for
for
after
the
beta,
and
I
think
the
model
db
for
rasmu.
Erasmus
is
also
on
pto
all
that
stuff,
that
it
seems
that
now
it's
clear
he
he
removed
the
dependence.
C
So
I
think
the
pi
is
good
itself,
but
I'm
gonna
hold
off
that
after
the
beta.
Let's
not
merge
that
before
the
beta.
C
E
So
what
did
we
remove
the
mongodb
instrumentation,
the
the
bytecode
instrumentation,
or
is
it
still
present.
B
E
C
Yes,
it
it
it
does
that
rasmus
pr
solves
that
true,
but
the
current
implementation
really
captures
the
background,
pings
and
stuff.
You
know,
but.
C
C
All
right
we
have
some
new
bugs,
I
think
we
understand
most
of
this
came
from
the
code
reveals
that
we
are
doing
now.
We
don't
have
a
file
rotation
for
the
log
and
right
now
we
are
limiting
the
log
size,
which
could
be
potentially
a
problem,
but
I
think
it's
kind
of
the
safest
for
the
beta,
so
my
preference
is
kind
of
to
go
with
that
for
now
and
afterwards
we
we
kind
of
look
and
to
improve
either
file
or
rotation
file
limits,
the
other
one.
C
C
If
it's
out
of
memory,
very
next
thing
is
gonna,
throw
that
in
somewhere
that
we
don't
catch,
you
know.
So
we
download
we
don't
do
anything,
it's
just
a
catch
for
the
startup.
I
think
we
should
revisit
to
try
when
it's
possible
to
log
that
information.
So
we
don't
kind
of
just
go
silent
and
there
is
no
log,
but
other
than
that.
I
think
it
also
it's
something
that
we
can
live
without,
for
the
time
being,.
C
Yeah
yeah,
so
so
that's
that's
what
I'm
saying
I
I
would
just
like
to
revisit
the
ones
that
we
have
to
be
sure
that
in
the
places
that
we
can,
we
are
logging,
the
other
places
and
there's
nothing.
You
can
do
right
so
linked
the
docs.
Also
from
the
prs
there
was
a
typo
in
the
docs.
If
we
had
any
kind
of
linked
for
the
markdown
files
that
should
have
been
caught
so.
C
Solution,
yeah,
if
they
did
that
it
was
working.
It's
great.
I
think
fabrizio
also
introduced
that
to
some
ripples
I
we
should
ask
him
to
be
sure
that
we
are
kind
of
using
perhaps
a
good
option.
You
know,
but
if
probably
whatever
that's
the
key
is
doing
is
something
that
we
should
be
following.
D
You
know
really.
B
C
Third,
one
for
the
logs:
yes,
I
think
that
one
should
be
for
the
beta,
because
that
is
kind
of
from
when
we
go
it's
a
legacy
from
when
you
got
from
upstream
and
we
it
is
our
first
release.
We
don't
need
to
support
both
right.
We
can
choose
one.
I
asked
matilds
to
take
care
of
that
next
week,
so
before
the
beta,
we
should
take
care
of
that
one.
C
So
I
I
was
going
kind
of
from
top
to
bottom,
but
from
top
to
bottom
from
the
log
to
the
top.
But
yes,
so
I
think
we
should
label
these
things
that
we
wanted
for
beta.
C
I
forgot:
what
is
the
alias
of
materials
I'll,
send
it
to
you?
Okay,.
C
I
think
matthias
is
a
member
already
right.
He
has
the
prs,
so
he
has
the
easy.
C
So
this
is
clearly
for
something
after
beta
we've
didn't
do
this
instrumentation
before
so
not
this.
We
talking
about
on
the
other
thing,
so
not
before
data
bump
versions,
so
this
one
should
be
a
red
market.
No,
it's
not
this!
I'm
assuming,
as
I
said,
that
we
wanted
a
stable
release
for
the
sdk,
so.
C
Unless,
for
some
reason,
this
kind
of
starts
to
drag,
yeah
flick
test.
C
I
didn't
see
this
one.
I
actually
gonna
do
a
quick
pr,
because,
while
you're
doing
a
review
from
the
api
that
I
added
the
asp.net
tests,
I
noticed
that
the
timeout
for
some
of
the
tests
that
are
flake
are
pretty
small
for
things
running
in
github
actions.
So
I'm
gonna
just
increase
the
timeout
of
those
and
see
how
it
goes.
You
know.
C
And
this
one
we
are
not
gonna
do
at
this
very
moment
we
can
prioritize
later
right,
dependable
for
native.
C
C
So
a
quick
review
here
of
the
stuff
that
was
recently
fixed,
I
just
double,
checked
and
the
the
thing
that
was
not
working
for
me
about
the
additional
depth
was
because
that
the
end
line
being
different
on
linux
and
windows.
C
Not
because
of
that,
because
we
need
to
manipulate
the
file
and
the
expression
doing
the
manipulation
was
using
the
platform
specific
one.
So
the
build
didn't
build
the
proper
thing
in
one
of
the
platforms.
I
don't
remember
it
was
windows
or
linux,
but
the
usage
that
we
are
doing
for
the
additional
depths
is
fine.
The
way
that
we're
documenting
is
fine,
so
that
was
close.
C
Raj
fixed
the
plugin
and
we
are
robert-
did
a
lot
of
work
for
documenting
mateo's
clean
up
the
the
standard
output
logs.
We
had
a
bad
exception,
zach
implemented
the
list
for
the
sdp
log.
So
it's
very
nice
now
you
can
look
in
the
files
and
you
see
what's
happening
with
the
sdk,
which
is
very
nice.
C
So
the
test
is
not
fake
yeah
and
then
we
are
going
back
to
furthering
the
passport
stuff
that
we
did
in
previous
weeks.
C
This,
that
is
in
progress
chris.
E
Yeah
so
questions
that
I
have
around
there.
We've
we've
talked
about
a
few
different
things
related
to
this,
so
noah
brought
up
a
concern
related
to
it,
and
then
I
believe
we
talked
about
introducing
some
sort
of
configuration
to
enable
it,
and
I
wanted
to
discuss
whether
or
not
we
want
that
configuration
to
be
part
of
this
beta
and
if
so,
do
we
want
it
to
be
defaulted
on
or
off.
C
So
I
didn't
have
time
to
investigate,
but
when
I
are
trying
the
examples
I
had
a
few
combinations
that
were
hanging
to
to
close,
so
I
thought
that
we
should
be
looking
in
adding
the
option
and
actually
the
default
for
me
should
be
disabled.
C
Okay,
you
know,
because
I
I
didn't
have
time
to
investigate
that
to
to
be
sure
what's
happening.
If
it's
a
specific
case
about
the
debugging
or
running.
Actually
it
was
not
debugging,
it
was
contrast
5
I
was
launching,
but
it
was
the
debug
build.
So
I'm
not
sure
if
there
was
something
special
about
the
debug
deal.
You
know,
I
don't
think
you
are
going
to
be
encountering
many
people
trying
this
with
the
bug
built,
but
it's
a
possibility.
C
So
I
think
either
I
would
rather
remove
it
it
from
the
beta,
which
will
be
a
simple
pr.
We
just
remove
keep
the
code
but
don't
add
the
handle
or
add
the
option
with
if
disabled,
by
default.
E
C
C
So
yeah,
whenever
you're
ready
for
a
pr
for
us,
then
we
we
take
that.
E
Yeah
and
then
I
think
I'll
just
submit
some
separate
issues
for
some
of
the
other
related
things,
but
I
think
that's
the
the
only
one
related
to
the
beta.
C
Yeah,
so
this
is
related
here
to
to
this
issue.
That's
here,
I
don't
know
if
raj
had
any
time
to
work
on
this.
A
A
I
see
I
don't
think
it
has
any
relation.
I
could
not
recreate,
but
based
on
your
error
code,
whatever
you
provided,
it
does
not
look
like
it's
from
that
handler,
but,
whatever
we
said
being
said
like
keeping
that
with
an
option
enabled
would
be
good
and
keeping
it
in
disabled
to
get
a
confidence.
We
will
enable
it
again
after
the
beta
and
leave
it
and
see
how
it
goes
that
that's
an
ex
creep.
It
is
an
experimental
thing
for
us.
C
Okay,
okay,
so
you
did
the
investigation.
Chris
is
gonna.
Do
the
pr,
so
I'm
gonna
consider
this
dome,
because
it's
gonna
be
an
address
by
the
other
item.
Then
right.
We
we,
we
didn't,
have
a
wrapper
and
we
are
gonna.
Add
the
option
via
the
number
three
two
one,
so
I'm
gonna
move
this
to
dawn
sounds
good.
B
B
C
B
C
I
think
we
we
can
go
ahead
with
the
beta
without
it
as
where
we
are
talking.
Do
you
wanna
wait
a
little
bit
because
you
can
ping
me
and
then
we
remove
after
the
meeting
you
have
the
meeting
on
thursday.
C
C
E
B
E
E
Okay,
that's
just
what
I
wanted
to
conduct.
E
And
then
for
the
the
code
scanning?
Is
that
also
a
should.
E
B
C
Yeah,
I
I
vaguely
remember,
I
don't
have
to
double
check
that,
but
I
my
impression
is
that
for
for
the
beta
is
not
required.
You
know,
I'm
not
a
hundred
percent
sure
when
you
get
to
official
releases.
You
know.
E
C
Yeah,
I
I
think
we
already
have
the
issue.
Sorry,
I
I
searched
there.
Okay
depend
about
or
licensed
headers.
C
Yeah,
so
I
I
could
do
this
follow
up
and
looking
for
that,
but
I'm
almost
sure
that's
not
required
for
for
the
beta
but
I'll
I'll
double
check
that.
C
C
And
these
two,
they
are
more,
let's
say,
blocked,
then
especially
the
bump
reference
and-
and
we
are
committed
to
this,
but
we
just
want
to
do
after
we
do
the
the
bump
to
a
stable,
sdk
release.
C
So,
as
far
as
I
understand,
the
sdk
plans
is
to
cut
one
by
next
week.
So
then,
immediately
after
that,
we
should
cut
our
release,
which
will
be
a
milestone
for
this
project.
We
should
do
a
small
celebration
in
the
next
sig
meeting.
Don't
know
how,
but
we
should
so
I'd
like
to
thank
everyone.
That's
finding.
I
know
that
is
a
challenge
for
us
to
find
the
time
between
the
other
commitments
to
working
on
this,
especially
that
we
are
not
kind
of
in
production
anywhere.
C
We
are
just
releasing
the
beta
so
find
the
time
and
the
energy
to
keep
coming
and
g
gaming
stuff
and
doing
this
stuff.
It's
really
important.
So
thanks
everyone
for
their
work
and
effort,
as
small
as
it
may
be,
is
always
helpful.
You
know
so
thanks.
Everyone.