►
From YouTube: 2021-09-29 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
A
A
B
B
B
No,
I
we
were
very
quiet,
it
didn't
mean
much.
I
just
said
that
I
I
know
that
raj
is
not
gonna
join
us
today.
He
had
a
conflict,
but
I
think
I
think
we
have
quorum
to
get
started.
B
B
D
D
D
B
But
I
I
didn't
look
that
sorry.
If
I'm
asking
basic
questions
here,
so
you
need
to
start
on
windows
docker,
but
that
requires
you
to
configure
the
docker
on
the
box.
Right
should
be
running
the
the
windows,
the
hyper-v
actually.
D
B
But
so
this
status
is
that,
basically,
you
can
run
in
your
machine
but
doesn't
run
in
ci
yep
okay.
So
if
somebody
has
any
experience
of
windows,
docker
hosting
windows
in
docker,
maybe
you'll
be
helped
for
that,
especially
in
the
case
of
this
is
github
actions
right.
So.
E
E
D
E
E
C
B
Enough
rights
to
do
that,
then.
Okay,
so
perhaps
that's
the
next
step,
because
we
can
we
can
try
to
have
you
access
the
box
directly,
so
you
can
see
what's
missing.
Regarding
your
box,
that's
not
working
good
question.
Who
has
the
access?
You
know?
I
think
I
do,
but
I
didn't
try
yet
so
I
probably
have,
but
I'm
not
sure.
B
B
All
right
the
proof
of
app
stream
kind
of
it's-
it's
basically
strap
yeah.
I
I'm
suspecting
that
something
is
broken
on
the
linux
side,
I'm
not
sure
exactly
what
it
is,
probably
something
related
to
the
renames
and
change
of
the
projects.
B
So
I'll
try
to
debug
that
to
see
what's
causing
the
linux
tests
to
fail,
it
seems
something
basic
about
starting
the
profiler.
I
don't
have
any
evidence
that
the
profiler
is
starting,
but
unlike
windows,
there
is
no
event
viewer
or
anything
easy.
I
think
I
should
use
s
trace
or
lldb
to
start
to
debug
that,
but
other
than
that,
I,
if
anybody
has
a
suggestion
to
investigating
profiler,
not
starting
on
on
linux.
C
All
right,
so
what
what
version?
Of
course
you
are,
are
you
running
against?
We
are
running
both
3.1
and
5
0.,
I'm
trying
to
so.
I
added
some
code
at
some
point
recently
to
emit
events
whenever
the
profiler
has
a
diagnostic
message
and
I'm
trying
to
remember
if
that
was
in
5-0
or
6-0,
I'm
afraid
it
might
be
in
6-0,
but
there's
you
know
you
can
open
a
net
trace
session
and
and
give
it
a
special
provider
and
it
will
spit
out
any
profiler.
You
know
failed
to
load
messages.
I.
B
I
noted
that
dot
net
five,
the
trace-
you
can
start
the
process.
You
can
give
the
comment.
So
perhaps
it's
five.
Do
you
know
what
is
the
provider
from
the
top
of
our
mind?
B
C
D
C
But
me,
but
as
I
as
I
get
symbols
for
corsail
r
and
then
I
set
a
breakpoint
on
cr
like
profile
profiling,
helper
load,
profiler
or
something
like
that
and
there's.
I
there's
just
a
method
in
the
runtime
that
you
can
debug
through
why
it's
failing
to
load,
and
I
realize
that
that
is
not
a
very
user-friendly
experience.
But
if
you
can
open
it
in
lodb,
then
and
get
core
clr
symbols
which
they're
open
source,
so
you
should
be
able
to.
E
Quick
question
david,
because
maybe
you
know
I
tried
using.net
race
today
on
wsl
like
use
it
to
start
a
new
process,
on.5
and
it
crashed.
Is
it
possible
that
it's
not
working
wsl.
C
It's
a
good
question.
I
know
we
did
some
stuff
to
support
container
but
again.
E
C
The
best
place
sure
I
I
can't
think
of
any
reason
it
wouldn't
work
on
wcsl
specifically,
but
I
mean
yeah
filing
an
issue
on
basically.
E
C
Interesting,
okay,
yeah,
finding
an
issue
on
the
the
microsoft
net,
diagnostic
or
sorry,
github.net
diagnostics.
Repo
is
the
best
way,
and
I
can
I
can
get
you
in
touch
with
john
who
owns
the
the
tracing
stuff.
C
B
B
Time
but
but
I
I
would
say
the
folly,
the
crash
is
not
expected
anyway
right,
the
two
should
have
say
hey.
I
can't
do
that.
I
can
do
this
not
crash.
You
know
true
yeah.
So
if
the
combination
is
not
supported,
not
crashed,
it
should.
B
B
So
I
yeah
that's
the
next
steps
for
for
that
one
and
I
think
the
the
most
interesting
thing
following
the
discussions
that
we've
been
having
with
raj
about
using
the
startup
hook.
Last
week,
we
had
a
a
longer
conversation
about
these
two,
so
we
still
see
the
need.
I
think
this
is
the
the
the
conclusion
that
we
are
in
the
last
meeting,
but
we
also
see
the
potential
for
a
lot
of
collaboration
about
the
bootstrap
and
how
to
use
this
code.
B
There
is
in
principle
there
is
no
need
to
have
a
different
bootstrap.
B
I
think
one
thing
that
I
I
I
think
we
need
to
discuss
here
is
because
okay,
we
do
the
sdk
injection,
but
also
there
is
all
the
source
instrumentation,
let's
start
with
the
basic
one,
the
asp.net
core
framework
that
is
added
on
the
bootstrapping
of
the
sdk
that
also
potentially
can
have
version
conflicts
that
need
to
be
solved.
You
know.
B
So
I
think,
I
think
the
the
idea
to
start
with
having
something
using
the
startup
hook
is
great,
so
we
can
explore
the
problems
that
we
are
going
to
have
with
the
versions
there,
but
I
I
do
expect
if
we
really
try
this
kind
of
corner
case
to
find
the
issues
there
to.
Regarding
the
versions
of
these,
let's
say
the
versions
required
by
some
of
these
source
instrumentations.
B
You
know
just
to
make
concrete
if
somebody
has
some
older
build
of
asp.net
core
and
tries
to
start
the
observer,
that
relies
on
some
updated
version
and
I'm
talking
about
not
of
diagnostic
source
itself
but
of
asp.net
core
itself.
B
But
you
are
targeting
a
application
that
has
a
old
version.
I
think
we
are
going
to
have
the
same
problem
as
diagnostic
source,
perhaps
with
the
difference
that
this
may
not
be
part
of
the
runtime
itself.
But
from
what
I
read,
I
think
we
should
just
try
to
have
this.
B
E
You
got
a
chance,
see
my
comment
if
I
tried
to
suggest
it
but
feel
free
to
edit
my
comment
if,
if
it's
not
like
in
line
with
your
suggestion,
basically,
I
propose
like,
like
the
first,
the
first,
the
third
and
the
second
at
first
paragraph.
Try
to
basically
express
what
you
probably
are
telling
right
now
just
to
have
this
as
a
common
code
and
then
tackle
this
versioning
problems
separately.
B
Yes,
yes,
I
I,
I
think,
that's
good.
I
think
we
just
should
be
very
explicit
kind
of
let's
see
the
code,
the
initialize,
that
we
call
we.
We
should
be
very
specific
and
hey.
Let's
try
to
call
this
code
here.
You
know
not
let
a
kind
of
open
what
I
mean
is
kind
of.
Let's
try.
First
call
in
the
same
code
that
the
profiler
calls
instead
of
having
another
reference
to
the
sdk,
you
know
and
then
we
go
from
there.
B
Then
we
are
going
to
discover
perhaps
things
that
need
to
be
changed
things
that
need
to
be
updated.
But
that's
what
I
think
is
the
the
starting
point
should
be.
Are
you
add
a
comment
about
that
and
link
to
the
code?
Then.
B
I
I
I
think
makes
sense
to
be
on
the
sdk,
but
I'm
gonna
say,
on
the
other
hand,
that
for
the
time
being
we
want
to
be
here
so
we
can
move.
We
are
kind
of
on
a
poc,
so
we
can
move
quickly.
You
can
change
things
quickly,
but
I
think
in
in
general
makes
a
lot
of
sense
to
be
something
a
package
offered
by
the
sdk.
B
You
know,
but
I
I
think
in
the
short
run,
we
should
be
keeping
with
us
and
then
later
we
come
back
and
kind
of.
Oh,
we
found
the
the
code
that
does
what
is
needed
in
these
scenarios.
We
are
stable
enough.
Let's
move
to
the
sdk.
B
Any
other
comments,
because
I
think
we
should
really
get
raj
to
start
to
kind
of
prototype
and
put
this
proposal
into
code.
So
we
can
see
and
try
by
ourselves
to
see
the
stuff
that
I
was
mentioned
before
about
conflicts
and
this
kind
of
issue.
B
Yeah
so
from
my
part,
that
was
the
stuff
that
I
wanted
to
touch
base.
Do
you
guys
want
to
bring
something
up.
A
Do
we
have
a
list
of
things
that
we
want
to
get
done
before?
We
can
take
the
proof
of
concept
and
make
that
the
main
branch.
B
I
think
we
didn't
organize
that
we
discuss
it
like
basically
have
a
few
bytes
called
instrumentations
a
few
source
code
instrumentations
that
are
really
implemented
on
the
contrib
and
be
able
to
inject
that
on
framework
and
net
core.
You
know,
that's
the
very
high
level,
but
we
need
to
put
a
list
like
that.
You
know
I
mentioned
this
in
the
past,
like
we
also
should
clean
up
the
issues,
but
I
think
the
next
thing
that
we
should
do
is
really
switch
the
branches.
B
So
when
we
switch
the
branches,
I
think
also
you
become
clear
for
people
coming
to
the
ripple.
Now
what
we
are
doing,
one
thing
it
doesn't
block
the
order,
but
then
I
think
you'll
be
the
moment
for
us
to
put
that
and
really
try
to
target
something.
I
would
love
to
target
something
kind
of
to
the
end
of
this
year.
You
know.
B
And-
and
I
think
if
we
have
kind
of
asp.net
cover
to
some
extent,
not
our
versions
but
to
some
extent
it
becomes
very
triable.
You
know
people
really
can
experiment
with
it,
because
it's
most
of
the
applications
have
that
in
a
way
or
another.
A
B
Yeah
robert,
can
you
open
an
issue
with
this
checklist?
Even
if
it's
incomplete
we
are
going
to
discuss
on
top
of
it
and
then
we
we
we
build
on
top
of
the
issue.
E
A
I
don't
care
if
we
use
the
same
issue
to
discuss
both
like.
If
what
do
you
all
thinks
easier
to
manage
two
separate
issues
or
one
with
two
less.