►
From YouTube: 2022-04-20 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).
D
B
B
I
just
hope
it
will
not
disturb
a
lot
okay,
so
I
have
created
additional
hyperlink
thanks
to
paulo
with
prs,
which
are
not
created
for
the
panda
bot,
because
I
don't
think
that
right
now,
it's
the
best
moment
to
look
at
the
peers
of
the
panda
bot.
B
Okay,
so
we
have
three
pr's:
let's
go
maybe
quickly
from
the
top
to
the
bottom.
First,
one
is
just.
I
want
to
promote
piotr,
who
is
here
to
nominate
him
as
an
approver.
So
if
anyone
has
any
objections,
then-
or
you
can
tell
right
now
here
or
leave
a
comment
but
basically
the
I
think
that
the
process
is
that
it
should
be
probably
approved
by
all
the
maintainers.
E
D
Yeah
I
posted
on
friday,
I
was
waiting
to
get
feedback,
got
feedback
and
haven't
adjusted
since
so
I
can
try
to
take
care
of
that
today.
Tomorrow.
C
Okay,
yeah,
I
I.
I
only
think
that,
because
you
and
chris
mentioned
a
very
good
point
about
some
stuff-
that's
very
internal.
I
think
just
pick
up
that
stuff
and
move
to.
I
don't
know
doc's
internal
docs,
dev
or
something
like
that.
F
Yeah,
a
quick
question:
is
this
something
that
we
consider
a
blocker
for
releasing
or
do
we
think
we're
we're
good
to
release
now
with
or
without
this.
C
I,
if
possible,
I
don't
know
how
zack
is
busy
with
stuff,
but
if
possible,
I
would
like
to
release
with
the
dogs
a
red
update,
because
I
think
this
also
makes
easier
to
read
a
lot
for
people,
so
I
I
was
thinking
perhaps
if
robert
could
prepare
to
cut
the
release
by
his
tomorrow
right.
So
when
we
copy
here
in
the
pacific
northwest,
we
are
ready
to
have
one.
If
that
gives
enough
time
to
zac,
then
we
have
both
and
we
can
really
claim
the
release.
B
And
the
last
one
is
regarding
mongodb
integration
and
it
was
already
agreed
a
few
times
that
it
will
be
postponed
and
note
that,
a
few
days
ago
I
think
paolo
has
removed
the
auto
bytecode
instrumentation
for
mongodb,
because
out
of
the
box,
it
was
instrumenting.
The
mocodb
client
code.
C
C
So
I
I
would
love
to
me
to
merge
that
after
the
beta,
I
will
give
this
being
besides
the
test.
I
will
give
xp
manually
with
the
examples
and
look
at
the
mongodb
stuff,
but
I
I
from
my
perspective,
as
we
talked
before,
let's
hold
after
the
beta
to
merge
that
perhaps
we
do
a
kind
of
very
quick
release
after
the
beta
with
that
instrumentation,
but
I
at
first
I
would
like
to
hold
off
a
little
bit
just
so
we
can
have
a
little
baking
of
that
instrumentation.
B
This
this
one
is
for
further
reading
for
sure
after
beta
I
come
up
with
it
today,
just
that,
depending
on
what
the
feedback
will
be
on
the
beta
release,
I
have
just
an
idea
that
maybe
it
will
be
if
there
will
be
a
lot
of
trouble.
If
there
will
be
a
lot
of
problems
regarding
the
dependencies
and
the
the
versioning
conflicts,
I
have
an
idea
just
to
remove
all
the
code
or
negative
old,
auto
sdk
just
use
this
repository
to
use
the
bytecode
instrumentation.
B
C
I
I
I
think
it's
it's
a
good
idea
to
kind
of
invite
everyone
here
in
the
sieg
kind
of
especially
now
that
are
releasing
this
beta.
If
people
have
ideas
that
they
want
to
kind
of
really
just
throw
at
wall
to
see
if
it
sticks
and
have
some
good
it's
a
good
moment,
because
then
we
can
redirect
the
project.
If
something
good
comes
from
those
you
know,
so
don't
don't
feel
that
the
idea,
don't
don't
limit
yourself
kind
of
the
idea,
is
not
that
good
bring
it
up
and
we
discuss.
B
Next,
one
is
adding
spell
check
to
docs.
People
had
added
markdown
link,
and
I
will
just
put
it
to
so.
It's
just
about
adding
spell
check.
I
think
it
will
be
a
little
more
complicated
based
on
what
I've
seen
what
have
been
done
in
the
dot
in
the
auto
sdk.
So
I
just
proposed
to,
I
will
just
put
it
into
the
rc
right
now.
B
B
C
Just
a
small
comment:
this
is
important
enough
that
I
think
we
should
also
add
to
the
examples.
You
know
not
only
the
unit
tests
when
we
do
it,
but
we
should
add
one
grpc
client
to
the
examples
you
know.
B
B
But
after
beta
right,
yes
thanks.
B
So
basically,
just
quick,
it
was
my
comment
that
I
think
that
if
we
catch
all
the
exceptions
we
might
catch
too
much,
I
don't
know
maybe
zack.
Maybe
chris
do
you
have
any
experience
here?
If
it
was
have
you
ever
encountered
the
problem
with
this
or
not
really,
maybe
I
should
close
it.
F
Well,
sort
of
right
so,
let's
say
you're
instrumenting
a
method.
Now
that
method
raises
an
exception.
F
D
F
D
Right
so
at
the
instrumentation
level
at
the
method
call
we'll
you
know
just
to
try
like
a
try
finally
kind
of
thing
and
we'll
note
if
an
exception
is
escaping
the
bounds,
the
instrumentation,
but
we
don't
have
a
event
handler
for
like
unhandled
exception
or
first
chance,
exceptions.
C
So
so,
just
to
be
sure
catch
the
exception,
don't
handle
it,
let
it
flow
but
catch
to
other
people.
F
F
And
log
them,
assuming
that
the
exception
was
thrown
from
our
code
as
opposed
to
customer
code,
so.
F
C
I
think
I
think
it
is
a
good
discussion
for
us
to
have
and
establish
policies
you
know
kind
of
for
for
initialization
and
kind
of
also,
I
think,
for
instance,
perhaps
zach
and
matthias
that
worked
on
their
login
code.
They
know
exactly
where
you
can
log
where
not,
but
if
we
could
write
all
of
that
when
we
get
to
do
this
thing
later,
you'll
be
nice.
You
know
instrumentations
here
is
the
police
initialization,
here's
the
police,
here's
the
restrictions
where
logging
is
not
available.
You
know.
H
I'm
also
wondering
like
do
we
have
even
a
scenario
the
few
scenarios
like
out
of
memory
and
everything
we
are
going
to
bootstrap
the
code.
This
happens
at
a
very
initial
time,
even
these
kind
of
exception
like
out
of
memory,
or
these
are
special
kind
of
exceptions
in
it.
H
Coming
back
to
the
other
exception,
which
could
happen
in
our
like
auto
instrumentation
code,
I
would
say,
like
we
should
the
reviewer
code
to
ensure
that
every
code
path
is
covered
with,
like
the
the
try
catch
block,
so
that
and
we
log
it
like
in
an
area
that
is
the
safer
approach
and
our
code
is
not
like
too
tedious.
H
It's
a
very
small
area
where
we
could
cover
all
of
those,
instead
of
just
writing
some
global
handler
for
it.
So
we
will
have
lot
of
control
over
it
as
as
we
identify
a
part
of
the
code
and
had
a
try
catch
to
it,
and
we
are
not
going
to
cause
a
performance
issue.
Also
with
that,
as
we
are,
it's
only.
We
get
kicked
in
during
the
start
time
and
after
that
we
won't
get
involved.
So
it
is
good
for
us
to
do
all
the
things
during
the
initials
time.
B
H
B
A
H
There
are
six
or
seven,
I
would
say,
like
stack
overflows,
another
one
execution
engine
exceptions,
so
there
are
three
more.
I
don't
remember.
On
top
of
my
mind,.
B
B
E
Yeah
I
just
I
only
wanted
to
say
that
I
I,
when
working
on
the
logging
improvements,
I
assume
in
the
near
future,
we
want
to
add
file,
rotation
or
file
rolling,
and
I
mentioned
that
in
a
pr
description,
and
I
just
assume
that
it's
better
to
have
this.
You
know
log
file
growth
bounded,
instead
of
let
it
growing.
E
Yeah
and
about
making
it
configurable
I'm
well,
I
I
wanted
to
start
simple,
I'm
not
sure
if
having
it
configurable
will
be
beneficial
for
us.
I
I
I'm
not
sure
if
this
is
something
that
client
might
might
want
to.
You
know
configure
really,
maybe.
C
Yeah,
I
I
think
we
can
we.
We
should
start
very
simple.
I
agree
with
that.
You
know
one
thing
that
I
was
thinking
yesterday
when
trying
the
the
current
code.
C
Is
that
because
you
use
the
kind
of
native
loader
managed
process,
then
the
pid,
especially
I
think
for
the
native,
because
okay
pids
are
usually
they
are
not
reused
frequently,
but
they
can
be
reused.
C
So
we
are
going
to
be
overwriting
one
pid
and
then
you
are
going
to
have
the
native
trace,
the
native
logger
for
one
process
that
reuse
the
pid
and
then
you
have
to
manage
with
the
same
pit,
but
perhaps
a
different
application
name
and
they
don't
match.
You
know
it
is
a
small
thing.
I
think
it's
very
unlikely
to
happen
in
practice.
C
The
name
of
the
log
file
yeah
the
name
of
the
log
file,
but
it's
like
dotnet,
I
forgot
the
prefix
and
then
we
we
say
native
that
that's
coming
from
the
profiler
and
then
has
the
pid.
It
doesn't
have
the
name
of
the
application
or
module
anything.
That
native
one
seems
at
the
high
risk.
For
me
to
be
reused.
If
the
p
is
reused
and
it's
possible
that
you
have
kind
of
oh,
I
ran
this
program
with
p
one
four
zero.
C
Then
one
for
zero
is
used
again,
but
the
log
for
the
native
for
the
first
one
is
gone.
You
know,
I
don't
think
it's
very
likely
to
happen
in
practice.
I.
B
B
C
Yeah,
so
just
people,
beware:
if
you
ask
for
logs
and
kind
of
see
something
this
as
you
open
the
fire,
you
become
clear,
you
know
we
are
not
gonna,
be
fooled
by
that,
but
I
I
think
right
now
is
a
possibility.
C
I
I
hope
is
unlikely.
I
really
think
it's
unlikely
in
general,
you
need
a
bunch
of
starts
and
things,
but
I
think
we
should
handle
that
when
also
doing
this
log
rotation
and
to
deal
with
that,
perhaps
we
re-examine
how
to
proper
generate
the
names
or
group
these
files.
C
I
I
think
on
this
one:
we
handle
that
too,
just
add
a
check
file,
name
conflict,
something
like
that.
E
But
guaranteeing
the
the
uniqueness
of
file
names
if
we
decide
not
to
use
pids,
but
I
don't
know
some
unique
idea.
Identifiers
instead
might
be
in
this
might
be.
F
C
Yeah,
no,
we
we
could
use
a
correlation,
create
a
random
number
and
becomes
a
correlation.
We
could
add
time
stamps,
because
the
same
period
is
not
going
to
be
used
by
two
process.
At
the
same
time,
we
can
figure
out
the
solution
later.
I
just
wanted
to
point
out
that
it's
a
possible
issue
right
now.
E
Yeah,
I
I
think
this
was
before
the
test
was
reworked
with
you
know,
with
logging
improvements,
so
I'm
not
sure
if
anyone.
E
E
B
D
G
B
All
right,
then,
this
is
our
last
one,
so
I
don't
know
I
can
yes.
C
So
if
zacchaeum
can
work
on
that
today,
then
I
think
chris
and
I
can
review
while
you
guys
go
to
bed
and
then,
when
you
wake
up,
you
can
start
on
that
and
when
we
wake
up,
we
already
have
the
bait
out.
We
need
to
write
a
small,
blurb
kind
of
to
tell
what
we
have
kind
of
what
are
the
source
instrumentations
and
the
single
bite
cold,
instrumentation,
that
we
are
adding
now
point
to
the
docks
and
guide
people
to
his
leg.
B
So
I
started
also
put
I
put
my
ideas
here,
but
because
I
have
assigned
this
initially
to
buy
some
project,
you
were
not
discussing
last
week
and
it
was
my
bad
that
I
was
not
asking
on
slack
to
review
this
one.
So
here
were
some
of
my
ideas
and
now
I
I'm
not
sure
if
you
have
any,
if
you
prefer
us,
for
example,
each
of
our
company
to
create
a
blog
post
on
our
own,
I
think
it
will
be
better.
B
At
least
there
will
be
some
differences
and
it
will
look
at
least
somehow
unique
for
each
company,
but
also,
I
think
that
as
hotel
can
we
also
have
some
blog
post
power.
F
Yes,
open
telemetry
does
have
its
own
blog.
I've
seen
a
few
announcements
on
there,
especially
regarding
tracing
stability
and
things.
I
I
Okay
yeah,
I
was
gonna,
say
I've.
I've
seen
the
post
come
through
medium
yeah,
so
we
transitioned
away
from
medium
late
last
year
earlier
this
year
and
I
just
haven't
used
the
new
one,
yet
austin
parker.
If
you
have
questions
you
can
reach
out
to
austin
parker,
but
I'm
pretty
sure
you
just
figured
out
how
to
do
it.
You
just
you
just
put
a
pr
and
a
new
file
into
that
into
that
folder.
There.
B
What
else
can
we
do?
I
think
we
can
also
is
someone
from
here
joining
the
dot
net
sdk
sig
meetings,
maybe
an
announcement
there.
C
I
can
I
can
talk
to
you
or
raj.
Also,
can
let
folks
know
there
in
microsoft
that
we
are
releasing
that.
C
Yeah
and
we
we-
you
can
do
that
robert
post
on
this
lack
not
only
hours
but
on
the
dot
net
shoe.
You
know
when
we
have
the
link
with
the
small
blurb
but
they're
on
the
the
slack.
C
So
I'm
planning
to
do
yesterday.
I
did
that
and
chris
did
that
too
we
kind
of
run
on
this
stuff
from
the
branch
and
tried
some
local
stuff.
I
basically
worked
with
the
examples.
I'm
gonna
try
to
create
a
small
new
project
today
and
instrument
also,
but
I
don't
expect
to
have
anything
there.
That
is
a
must
fix
so,
but
if
we
have
something
that
perhaps
is
worth
as
a
new
example
after
the
beta,
I
create
the
pr
or
I
create
api
and
later
we
we
merge
and
update.
F
C
No,
I
was
gonna
say
that
the
the
important
thing
is
for
anyone
that
has-
and
I
have
some
of
our
customers
in
mind-
to
ask
them
to
give
a
try.
You
know.
I
think
this
is
key.
Usually
they
take
time
when
you
give
something
like
this
to
test,
but
eventually
we
get
some
feedback.
C
So
if
you
have
somebody
that
perhaps
is
a
candidate
for
take
a
look
and
try
on
their
services,
please
contact
the
people
point
to
the
resources
that
robert
is
tracking
here
and
I
I
think
the
word
of
mouth
is
very
important.
You
know.
Sometimes
the
announcement
on
the
website
doesn't
get
that
visibility,
but
you
pinging
somebody.
It
immediately
gets
some
visibility.
B
By
the
way,
raj
is
there
someone
on
microsoft,
responsive
right
from
the
management
or
I
don't
know,
a
public
relational
relationship
for
hotel
who
can,
for
example,
put
a
blog
post
on
dotnet,
blog
or
I
don't
know
could
be
part
of
microsoft
build?
Could
you
ask
around.
H
B
H
B
Do
you
remember
his
noah.
G
B
C
B
B
D
C
Yeah
well
one
thing
that
I'm
a
bit
kind
of
thinking.
Now
we
want
some
people
to
to.
We
want
to
get
the
feedback,
but
since
this
is
not
a
our
release,
that
we
are,
we
are
still
treating
as
experimental.
C
I
think
we
want
to
kind
of
make
people
aware,
but
we
are
not
making
an
announcement.
That
kind
of
we
are
ready.
You
know
so
I
don't
know
noah
you
you'll
figure
that
out,
but
I'm
not
sure
if,
for
instance,
you
wanna
try
to
have
this
on
the
official.net
blog.
You
know-
perhaps
it's
too
early
for
that.
In
that
sense,.
B
If
there's
one
thing
which
I
have
not
like
the
last
the
last
point
here,
how
do
you
want
to
get
the
feedback
and
how
we
want
to
gather
that
I
was
thinking
of
creating
a
basically
issued
issue
issue
template
like
experience
report
when
we
can,
just
I
don't
know,
ask
for
generic
feedback
and
just
suggest
some
sections
like
use
case,
for
example,.
C
C
I
think
it's
good
to
advertise
the
channel
in
slack
because
we
want
to
be
informal,
so
we
don't
want
to
make
the
bar
because
sometimes
the
when
we
put
the
forms,
we
ask
a
lot
of
information
that
we
think
is
useful,
but
then
we
are
making
the
the
bar
for
people
to
type
and
go
there
and
give
any
feedback
kind
of
higher.
C
But
I
I
I
would
say
first
is
lack
reach
us
on
his
lack
then
put
a
template.
Let's
try
to
keep
the
template
light.
You
know
yeah.
B
Yeah
exactly
so,
but
I
think
we
should
update
it
can
be
after
or
before
release
it
doesn't
matter.
I
think,
just
to
even
put
those
three
sentences.
Like
you
know,
we
need
feedback
and
very
high
on
the
top.
F
Yeah
yeah
yeah
and
with
that
being
said,
there
is
a
user
feedback
working
group
out
there.
Now
that's
working
on
putting
together
feedback
surveys
that
we'll
be
able
to
to
leverage
in
the
future
as
yet
another
way
to
get
to
get
feedback.
F
C
Yeah,
let's
perhaps
try
to
unburden
people
for
us
to
open
the
issues
after
talking
to
them,
you
know,
so
we
do
the
heavy
lifting
of
organizing
and
kind
of
this
stuff.
You
know
I
I'm
more
interested
in
making
easier
this
process,
so
people
kind
of
give
us
feedback
annie.
C
C
I
don't
know
you
spend.
A
A
F
Yeah,
I
think
both
would
be
good
and-
and
I
think,
we're
more
likely
to
hear
the
the
negative
feedback
from
both
communication
methods,
which
is
still
good.
C
F
Yeah,
so
I
don't
know
if
splunk
and
datadog
have
their
own
example
setups
or
anything
like
that.
That
could
showcase
how
to
set
things
up
as
a
vendor.
C
Yeah
I
I
can.
I
can't
merge
that,
because
that's
where
use
it
to
deploy
to
demos
and
stuff,
but
I
can
create
a
branch
and
show
in
a
branch
you
know
our
chains.
C
I
I
think
that
yeah,
that
repo
is
public
yes,
so
I
can.
I
can
show
that
but
but,
as
I
said,
I'm
not
gonna
merge,
because
it's
not
the
official
yet
right.
So
eventually.
I
hope
we
get
to
that
point
and
emerge,
but
for
now
you'll
be
a
branch.
F
B
Maybe
I
have
a
question
who
can
create
me
because
there's
a
quite
a
lot
of
things:
do
you
pref?
I
don't
know,
I
don't
think
it's
worth
to
create
another
github
issue,
because
I
can
do
this
one
this
one
yeah,
this
one
is
on
everyone
here
we're
asking
noah
anyway
adding
a
reading.
You
can
be
as
part
of
this
issue
only
about
this
blog
post.
Is
there
any
should
I?
I
will
just
create
a
github
issue
for
this
one.
Okay,.
C
Raj
one
question
for
you:
I
talked
a
long
time
ago
with
sarab
that
was
the
pm
for
diagnostics
and
he
left
microsoft.
Who
is
the
pm
for
diagnostics?
Now.
H
So
I
don't
know
if
there
is
a
need,
I'm
just
working
directly
with
tariq
or
nova
in
that
area,
but
there
is
a
pm.
It's
a
new
pm.
We
are
giving
a
ramp
up
time.
I've
never
got
to
work
with
them
once
they
ramp
up.
My
plan
was
to
get
them
to
this
meeting
every
week,
so
I
don't
think
that
ramp
up
is
being
complete
yet
so.
H
System
in
the
for
a
very
long
time,
so
he
understand
things,
but
I
think
the
new
pm
needs
to
like
understand,
like
the
fundamentals
and
before
jumping
to
this
is.
F
So
I've
heard
that
there's
writing
resources
available
at
the
cncf
level
to
assist
with
blog
posts,
and
things
like
that.
I
don't
personally
know
how
to
to
get
assistance
with
those
things,
but
it's
new.
F
I
I
don't
know
who
that
would
be
because,
like
I'm
on
the
governor's
committee
for
us
hell,
we've
historically
just
had
to
write,
do
basically
all
that
stuff
ourselves.
Do
you
want
to
chase
that
down.
C
Okay,
yeah-
and
this
reminds
me
that
just
because
fabrizio
has
been
very
helpful
for
us
in
the
docs,
but
he
now
his
on
patent
leave.
So
sometime
that
we
are,
there
will
be
no
fabrizio
to
help
us
with
our
wording.
You
know.
C
C
Icon,
but
is
it
starting
now
you
know
kind
of
thing.
I
I
I
mean
I'm
happy
to
lend
a
hand
in
assists,
though
I
I
I
mostly
here
just
because
paulo
had
requested
a
certain
conversation,
but
I'm
happy
to
help
review
it.
I
I
think,
having
me
help
write.
It
would
be
pretty
disingenuous
because
I
haven't
worked.net.
C
Yeah,
I
I
think
I
think
I
I
don't
wanna
say
that
I
wanna
take,
I
feel,
like
I'm
gonna
take
it,
but
I
I'm
not
sure
if,
when
I
will
be
able
to
do
it,
probably
only
on
friday,
you
know.
So
if
somebody
can
start
before
that,
please.
B
F
Writing
isn't
isn't.
Is
it
my
strength,
but
honestly,
with
the
issue,
we
can
have
a
public
google
doc
out
there
that
we
can
make
edits
and
comment
on
and
group
it
do
it
as
a.
F
You
know
to
be
honest:
yes,
english
is
my
first
language
but
kind
of
in
a
unique
space
where
I
know
the
british
spelling
of
things
as
opposed.
J
To
the
american
spelling
of
things,
and
so
so
what.
J
B
F
C
I
I
I
would
say
again
thanks
everyone
for
working
on
that.
I
think
everyone,
that's
here
kind
of
did
their
contribution
and
it
was
a
long
journey
until
this
I
I'm
gonna,
say
first
release
that
we
do.
I
hope
that
then
we're
gonna
get
some
cadence
and
kind
of
make
more
steady
progress.
B
G
F
Yeah
yeah
there
were
a
lot
of
things
going
on
a
lot
of
debate
on
the
overall
strategy
of
things
and
yeah
yeah.
I
feel
like
we're
with
one
of
the
issues
that
that
was
submitted
that
we
talked
about
today.
It's
kind
of
circling
back
to
some
of
the
things
we've
waffled
on
during
that
two-year
period,
yeah.