►
From YouTube: 2021-12-01 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
Okay,
I'm
not
sure
if
his
I
will
leave
this
one
and
try
to
get
the
meeting
that
he
is.
Give
me
one
minute.
B
A
Yeah,
I
I
I
don't
know
what
happened,
but
at
least
chris
and
I
end
up
in
the
same
meeting
so
that
that
maybe
I
I
don't
know
if
the
calendar
somehow
changed
the
position
of
the
meetings
and
I
clicked
on
the
wrong
one.
I
don't
know.
B
A
All
right,
I
think
we
can
start
reviewing
the
project
board.
I
don't
know
I
I
really
didn't.
It
really
took
a
break.
I
didn't
look
at
much
and
I
start
this
week
again,
but
I
didn't
look
at
much
yet
so
it
seems
that
the
only
new
white
is
support
for
alpine.
A
And
I
think
the
question
is
then:
do
you
want
to
do
this
for
our
attentive
release.
B
D
Same
if
it
doesn't
have
too
much
work,
then
that's
fine,
but
I
don't
think
we
should
block
on
it.
If
it's
gonna
take
too
much
time.
A
Okay,
so
I
I
think,
for
the
time
being,
I'm
gonna
put
on
the
under
the
ga
bar
and
later
we
can
review
that
and
if
somebody
has
a
need
for
that,
but
for
for
now,
let's
keep
under
the
ga
bar
yeah.
B
A
But
then
we
have
to
add
the
building
everything
you
know,
so
I
do
remember
that
for
some
time
ago,
not
recent,
I
did
build
something.
I
thought
that
I
was
building
something
for
alpine
with
environment
variables
configuration
in
the
build.
It
was
not
an
opined
machine
and
kind
of
I
built
the
package,
but
then,
when
I
tried
to
run
it
didn't
run,
you
know,
so
I
think
the
easiest
way
is
simply
to
stand
up
alpine
darker
and
build
there
directly.
It's
much
easier.
A
A
All
right,
so
I
think
that
was
the
only
new
item.
A
Did
you
guys,
because
I
I
didn't
see
much
what
happened
during
this
week
that
and
the
thanksgiving
also
did
you
guys
did
some
of
the
work
that
was
previous
committed
is
now
in
progress
or
complete.
B
So
I
don't
know
that
anything's
been
completed
at
this
point.
I
there's
been
a
general
lack
of
communication
on
on
some
of
the
issues
during
the
last
week
or
so,
and
so
some
of
the
pr's
from
raj
that
I
think
we're
still
waiting
for
some
other
opinions
from
from
maintainers
to
get
that
moving
forward.
A
So
I
I
think
from
from
my
side,
I
probably
can't
get
to
some
of
those
prs
in
detail
today
and
tomorrow
so
more
likely
tomorrow,
but
I
will
put
that
on
all
my
action
items
to
kind
of
give
feedback
on
on
the
pr's
and,
as
I
said,
raj
probably
only
tomorrow
will
get
you
then.
A
C
I
want
to
just
get
one
clarity
on
that
additional
tips.
Maybe
when
everyone
is
there
about
the
folder
location,
the
remaining
feedback,
I
think
we
can
do
it
within
the
pr.
So
this
is
a
bigger
discussion.
Why
should
we
create
a
folder?
C
Should
we
do
it
in
within
the
target
framework
folder
or
at
the
tracer
home
the
root
itself?
So
if,
if
we
have
a
clarity
on
that,
we
can
easily
move
that
vr
lower
faster
towards
the
merging.
A
I
see
I
I
didn't
participate
on
the
discussion,
so
I
I
I'll
delegate
that
I
think
to
chris
and
and
zach
if
they
are
aware.
B
Yeah,
I'm
I'm
interested
in
zach's
opinion
because
my
one
concern
about
merging
the
directories
was
it
potentially
complicating
the
the
lookup
of
the
managed
tracer?
But
if
that's
not
gonna
be
an
added
complexity,
then
I'd
say
it
makes
sense
to
merge.
It.
D
I
don't
know
that
I
I
think
I
need
to
review
the
pr
more
before
having
an
opinion,
so
I
can
take
a
look
stare
tomorrow
and
provide
insight
there
yeah,
I
don't
have
any
more
say
at
the
moment.
A
Yeah,
so
just
for
me
to
be
sure
this
one
that
you
guys
are
talking
about
is
which
one
of
the
two
that.
A
A
Yeah,
so
I
think
for
for
the
board.
Basically,
this
is
what
they
have
in
the
board
and
I
think
the
rest
of
the
time.
Actually,
we
usually
used
to
go
over
the
the
pr's
unless
you
guys
wanna
before
that,
bring
something
up.
A
Okay,
so
let's
go
over
the
prs,
so
I
think
we
talked
about
the
the
proxy
once
some
time
ago.
A
A
C
Last
week,
where
we
planned
last
time
when
we
met
the
plan,
was
to
get
the
additional
tips,
we
are
merged.
First,
that's
the
one
of
the
workaround
and
then
think
about
this.
This
might
not
go
in
our
earlier
beta
release
or
anything
it
can
be
later
after
that,
it's
just
a
skeleton.
We
just
need
to
take.
A
C
Feedback,
whether
we
should
proceed
in
this
direction
or
have
some
other
like
options
explored
for
us,
so
we
also
looped
in
greg
here,
but
I
don't
think
we
got
the
response
from
him
later.
A
Okay,
we
can
ping
here
again
for
yeah.
I
I
think
if
it
was
last
week,
a
lot
of
people
are
on
breaking
last
week,
so.
A
D
Greg
has
been
out
as
well
for
the
last
couple
weeks,
so
just
a
heads
up,
I
don't
know
if
he'll
be
responsive.
I
think
he's.
I
think,
he's
been
sick
for
a
week
or
two.
A
I
see
I
see
yeah,
we
are,
we
are
getting
to
that
part
of
the
year
that
a
lot
of
things
get
transferred
to
january.
So.
A
C
This
also
we
discussed
last
week.
The
action
plan
was
to
wait
for
open
telemetry
to
release
the
new
stable
version,
and
we
take
that
and
that
will
handle
this
part.
C
B
Who
clicks
exclusions
chris
yeah,
so
gotten
a
little
bit
of
feedback
here?
I've
got
some
things
to
work
through
that
robert
pointed
out,
but
I'm
still
looking
for
any
other
thoughts
that
others
may
have
around
some
of
the
decisions
being
made
here.
I
called
out
some
of
the
big
ones,
in
my
mind
like
where
we're
reusing
some
of
the
environment
variables
and
things
of
that
nature.
A
So,
okay
raj
these
ones
somehow
interact
with
your
stuff
or.
C
It's
an
additional
functionality.
I
don't
know
that
it
has
nothing
to
do
with
like
both
are
independent
things.
A
Okay,
did
you
have
a
chance
to
review
it.
C
Yeah,
I
did
it,
it
looked
good
for
me.
The
conversation
here
is
about
the
environment
variable
and
like
not
about
the
functionality.
Am
I
right
chris
on
this.
B
Correct
yeah,
so
it
doesn't
really
change
the
behavior
of
the
startup
hook
and
how
that
interacts
with
other
things,
it's
just
more
of
a
controlling
when
the
startup
hook
should
be
applied
and
when
it
shouldn't
okay,.
A
So
chris,
are
you:
are
you
putting
my
best
to
review
and
so
I'll
try
today,
but
more
likely
tomorrow,
I'll
have
some
feedback
or
approve
or
whatever,
and
then
we
perhaps
move
ahead
and
merge
after
some
extra
discussion
and
of
course
we
always
can
go
back
and
change
the
behavior.
So.
B
B
Thing
that
could
be
shared
things
like
that.
C
I
don't
think
we
should
block
this
fear.
My
opinion
would
be
to
like
we
are
having
some
discussion
related
to
the
how
things
needs
to
be
used.
That
should
be
created
as
a
separate
issue
and
that's
those
environment,
variable
stuffs
and
all
can
be
done
through
a
follow-up
year,
because
this
is
a
functionality
which
says
that
some
like,
if
you
have
some
process
you're,
saying,
don't
get
the
status
hook
injected
into
that.
So
maybe
like
follow
you,
okay,
when
you
take
a
look
into
it,
you
can
like
review
that
part
too.
A
And
the
top
one
robert
is
updating
the
dogs.
A
I
think
this
is
dark
update.
I
don't
think
there
is
any,
perhaps
big
the.
B
One
thing
I
just
wanted
to
call
out
because
I'm
curious
what
others
think
so
the
word
supported
means
different
things
to
different
people,
and
so
when
we're
saying
that
we're
supporting
particular
operating
systems
do
we
need
to
be
more
explicit
about
what
that
means.
Or
are
we
okay
with
just
saying
that
we
support
these.
A
A
Perhaps
we
want
to
say
compatible
for
now
and
as
we
kind
of
define
these
targets
and
get
closer
to
a
beta
nga,
then
we
kind
of
use
the
term
supported,
because
I
I
really
think
even
for
open
source
project
that
when
you
put
support
it
means
that
kind
of.
If
people
find
bugs
people,
you
look
and
try
to
fix.
B
C
A
Yeah,
I
I.
I
think
that
my
tendency
right
now
is
to
say
that
we
are
testing
we
are
having
this
matrix
right
now,
but
then
we,
when
we
get
near
beta
nga,
we
kind
of
then
really
commit
to
support
specific.
A
Yeah
yeah
yeah,
I
I
I
I
think
it's
a
good
feedback.
I
think
I
will,
I
will
add
my
my
blurb
there
and
then
we
we
can
can
move
forward,
but
it's
good
also
to
see
the
the
dogs
being
taken
care
related
to
the
dogs
and
also
the
work
that
raj
is
doing.
I'm
I'm
thinking
that
some
time
ago
I
wrote
kind
of
very
few
lines
about
kind
of
giving
an
overview.
A
I
think
perhaps
we
should
kind
of
extend
that,
and
I
I'm
not
thinking
that
we
should
create
this
right
now
for
as
this
stuff
for
for
us
to
be
committed,
but
perhaps
to
extend
the
documentation
to
cover
how
they
start
uphook
and
their
approach
that
we
are
already
using
work
together
and
kind
of
what
are
the
paths
you
know.
A
So
I
think
raja
red
put
a
lot
of
description
on
the
issues
npr's,
so
that
could
be
basically
leverage
to
update
that
document
to
to
reflect
our
of
those.
You
know
so
people
have
a
landing
place
that
they
can
arrive,
read
and
understand
how
this
parts,
I'm
gonna,
create
a
issue,
but
I-
and
I
will
put
kind
of
for
we
can
discuss
on
on
the
next
meeting.
It
should
be
for
alpha
or
beta,
but
I'll
create
the
issue.
A
So
we
don't
forget,
but
I
don't
think
it's
something
that
we
need
to
tackle
right
now.
I
think
perhaps
in
the
beginning
of
the
next
year
or
after
kind
of
we
are
closer
to
our
alpha
release,
then
we
we
should
look
at
that.
B
So,
along
the
lines
of
the
startup
hook
locally,
I've
proved
out
that
using
the
profiler
to
set
the
environment
variable
for
the
startup
hook
works
and
is
a
workaround
for
the
errors
that
I
was
seeing
when
running
certain
applications.
B
When
the
asp.net
instrumentation
is
requested
and.
A
B
B
I
said
I
I
mean
there's,
obviously
some
sort
of
timing
issue
going
on
there.
So
I
don't
know
if
it's
just
as
simple
as
we're
trying
to
bootstrap
things
in
a
module
that
we
shouldn't.
C
Or
or
not,
and
of
course
like
on
the
same,
so
the
additional
depths
should
fix
that
issue.
Also,
the
the
reason
is
like
when
the
tpa
list
gets
created
in
a.net,
it's
going
to
create
it
with
additional
depths
also.
So
if
we
have
that
library
in
one
of
our
subfolder
placed
so
it's
going
to
resolve
that
automatically
someone
uses,
we
don't
need
to
modify
our
code
in
those
cases,
I
feel
now
it's
not
auto
upgrading
it
to
the
higher
version
of
library.
That's
why
we
crash
there.
C
I
I
did
not
get
time
to
do
a
in-depth
analysis
on
that,
but
looking
at
the
error
message
and
everything,
that's
and
the
stack
saves
us.
That's
the
issue.
Maybe
once
the
like
additional
depth
gets
merged,
we
can
try
it
with
that
and
see
if
that
works.
That
would
be
a
good
workaround
for
that
kind
of,
like
scenario.
A
Yeah,
I
I
I
feel
right
now
that
you
should
document
the
work
around,
but
I
think
we
need
kind
of
deeper
understanding
and
actually
I
think
the
other
thing
that
we
want
to
have
is
kind
of
okay.
It
happened
here.
Can
we
be
sure
that
all
the
instrumentations
that
we
are
injecting
from
contrib
don't
have
similar
cases?
You
know
kind
of
how
you
can
validate
this
kind
of
thing.
A
A
A
Yeah,
I
think
I
I
think
for
now.
Let's
skip
documented
the
the
the
work
around
that
you
found
chris
and
kind
of
trying
to
dig
a
deep
to
having
a
kind
of
really
good
understanding
of
this.
Yes,.
B
So
there
so
there
isn't
really
a
workaround
without
doing
a
build
of
the
profiler
at
this
point,
because
I'm
basically
using
the
profiler
to.
A
So
so
let
me
go
to
the
basics
here,
because
I
I
I'm
perhaps
forgetting
how
they
they
work
around.
So
when
you
set
the
environment
variables,
you
start
to
use
the
startup
hook
to
so.
B
So
it's
a
timing
thing.
So
let's
say
you
set
the
startup
hook
environment
variable,
but
then
you
also
set
the
profiler
environment
variables
as
well.
So
what's
going
to
happen,
first
is
the
profiler
is
going
to
load
and
run
and
it's
gonna
trigger
its
loading
before
the
startup
hook
is
actually
loaded
and
run.
B
A
A
Yeah,
I
have
to
think
about
it.
I'm
I'm
right
now
I
I'm
unsure.
If
we
perhaps
should
get
this,
because
if
we
get
this
right
now
we
are
going
to
make
it
easier
to
test
and
try
because
right
now,
it's
kind
of
broken.
A
I'm
just
wondering
if
we
do
that
kind
of
we
hide
some
stuff.
You
know
and
to
be
fair
to
I
I
kind
of
have
a
very
high
level
grasp
of
the
thing.
I
think
I
need
to
see
the
great
details
you
know
kind
of
to
really
get
a
grasp
of
that.
A
Okay,
I
think
friday
friday.
I
I
have
a
good
chunk
with
without
meeting.
So
all
right
sounds
good.
I
hoping
with
you
outside,
so
you
can
schedule
that
okay
sounds
good.
A
A
He
has
kind
of
deliverables
that
he
plans
to
do
with
this
project
and
I
think
you'll
be
time
for
that,
and
also
erasmus
that
have
been
doing
a
lot
of
effort
on
the
testing
side.
I
think,
is
the
time
for
for
us
to
have
them
as
approvers.
A
Yeah,
I
think
I
I
if
for
some
reason
somebody
thinks
that
that's
not
the
case,
don't
need
to
tell
in
front
of
them.
You
can
pick
me
outside,
but
I
think
I
saw
just
people
agreeing
and
approving
that,
so
I
will
get
the
things
started,
so
they
soon
should
be
approvers
on
the
team.
Congratulations
to
both.