►
From YouTube: 2021-05-18 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
C
Yes,
I
can
hear
you
you
can
share
the
screen.
Okay,.
D
C
C
It's
two
minutes:
past
love,
one
I
will
be
like
leaving
in
around
10
minutes
or
max
15
minutes.
So
I
asked
ruth
to
present
okay
and
yet,
if
you
are
in
the
call,
please
add
your
name
to
that
in
this
list.
Yeah,
like
I
think
you
can
go
over
the
agenda
items
one
by
one.
It's
very
short,
so
hopefully
it
should
be
very
quick.
A
Okay
yeah,
so
mostly
just
updates-
and
the
first
point
we
have
here
is
that
we
have
found
breaking
changes
in
the
1.1.0
beta
3
version
of
the
sdk,
with
respect
to
the
ad
legacy
source
method,
which
was
moved
from
sdk
as
an
extension
method
to
the
api,
and
I
have
created
an
issue
for
this
to
track
it.
And
then
so.
A
We
would
have
to
release
new
newer
packages
now
beta
4
for
api
and
sdk
and
for
the
instrumentation
packages
we'll
have
to
release
rc5,
and
the
issue
is
basically
that,
with
until
beta
2,
add
legacy,
source
method
was
present
in
the
sdk
and
for
some
reason
the
rc4
version
of
the
instrumentation
packages
seem
to
have
been
compiled
against
that.
And
they
always
look
for
the
method
in
the
sdk
and
not
the
api
and
that's
what's
breaking
the
that's.
The
breaking
change
and
yeah.
C
In
general,
like
we
could
generally
make
a
statement
that,
like
asperger.net
guideline,
adding
a
new
abstract
method,
two-way
based
class
or
like
abstract,
based
class,
is
a
breaking
change.
Unfortunately,
the
tool
we
have
does
not
detect
it
as
a
breaking
change
so
going
forward.
We
would
have
to
see
if
the
next
tool,
like
apa
compact,
that's
a
new
tool
which
start
my
team
has
recommended.
So
we
have
to
see
whether
that
tool
would
have
caught
this
issue
or
not.
A
Yeah
yeah
and
the
other
one
other
update
is
for
the
multitargeting
issue,
where
a
dotnet
framework
app
tries
to
consume
a
library
that
is
dotnet
standard.
We
had
this
issue
of
method
of
running
into
missing
method
exceptions.
We
still
haven't
gotten
any
update
from
the
dotnet
team,
so
we're
going
to
be
discussing
this
with
them
about
this
issue
next
week
and
the
metrics
api
pr
got
merged
into
the
dot
net.
A
Pr
for
that
got
much
and
like
this
would
be
getting
released
as
part
of
the
net.net
six,
so
with
cjo
or
victor
would
be
working
on
replacing
the
replacing
the
package
that
we
have
in
our
repo
with
the.net
package.
That
has
the
metric
support.
A
C
E
E
C
The
metrics
group
has
agreed
that,
like
may
end
like
this
month
end,
they
would
mark
api
sdk
as
experimental
and
by
june
it
will
be
marked
in
such
a
state
that
there
wouldn't
be
any
like
major
breaking
changes.
There
could
be
like
some
minor
tweaks
here
and
there,
and
there
is
also
an
effort
to
make
the
api,
not
the
sdk
stable
even
earlier
than
that.
C
So
so
far
what
dotnet
has
done
is
they
have
only
included
those
instruments
which
which
do
not
have
any
like
open
questions.
So
there
are
like
certain
instruments
which
are
like
still
like
being
discussed
in
the
community,
so
what
they
decided
is
they
started
with
the
minimal?
I
think
it
supports,
like
five
out
of
seven
instruments
and
with
the
intention
with
the
plan
that,
like
if
those
two
instruments
are
fine
list,
dotnet
still
have
the
opportunity
to
add
things,
probably
until
like
late
july
or
even
early
august.
C
C
Yeah,
so
I
think
the
original
plan
called
for
like
marking
api
and
sdk
as
like
breaking
changes
only
more
like.
I
think
it's
not
stable,
it's
not
experimental
but
like
something
in
the
middle.
C
It
was
only
like
june
end,
but
there
was
some
conversation
last
two
weeks
about
like
making
api
even
earlier,
so
that
would
also
help
the
dot
net
course
because
like.net
api
is
going
to
be
like
about
to
the
timeline.
So.
E
E
So
that
should
be
where
we
are
going
to
put
the
next
effort,
so
that
is
going
to
focus
on
tracing
because
it's
already
released
and
we
need
some
stability
on
that
side
to
test
that.
So
then
math
could
come
later.
You
know
one
thing
regarding
metrics.
That
may
be
interesting,
but
this
is
not
complete,
but
I
think
it's
worth
to
mention
here
to
through
the
group
is
that
the
hotel
collector
has
a
event
pipe
listener,
that's
capable
of
listening
to
the
the
metrics
that
are
currently
generated
by
dotnet,
thor
and
dotnet5.
E
You
know
so
we
plan
to
do
some
investment
on
that,
so
we
plan
to
do
discovery
of
net
processes
and
be
able
to
collect
the
gc
methods,
runtime
methods
that
are
red
generated
in
in
that,
so
probably
on
the
collector
side.
We
want
to
be
sure
that
we
are
also
capable
to
capture
the
metrics
being
generated
via
the
open,
telemetry
api.
C
Okay,
yeah,
I
think
you
you're
referring
to
the
metrics
which
are
published
using
event
counter
api.
That's
the
one
which
you
are
like
listening
using
event
pipes.
E
If
there
is
interest,
perhaps
we
we
can
schedule
a
demo
of
the
collector
capturing
the
event
counters
as
it
today,
some
two
or
three
weeks
down
the
road.
C
Yeah,
that
would
be
helpful
because
one
of
the
work
item
which
we
plan
to
do
in
the
sdk
is
to
write
a
adapter
kind
of
thing
for
those
metrics
which
are
published
using
even
counter
so
they
are.
They
can
be
piped
through
the
new
api,
because
there
are
like
a
lot
of
useful
metrics
published
by
the
runtime,
using
even
counter
like
gc,
all
the
gc
metrics.
C
So
there
is,
there
was
an
interest
when
we
were
working
on
the
original
metrics
like
a
year
and
a
half
back
to
pipe
that
through
the
new
api.
I
don't
know
whether
like.net
would
provide
some
native
support
to
do
the
conversion
or
like
we
have
to
do
something
in
open
telemetry.
But
that
is
something
which
we
are
definitely
after.
Yeah
yeah.
If
you
can't
like
show
what
how
in
collector
yeah
that
would
be
cool.
E
Yeah,
probably
in
probably
two
or
two
weeks,
I
I
ping
you
back
back
before
the
meeting
like
three
four
days
before
the
meeting,
so
we
can
schedule
an
announce.
So
if
other
people
want
to
watch
that
they
they
have
time
to
to
come
to
the
meeting
to
prepare
to
come
to
the
meeting
yeah.
Okay.
D
F
Oh
okay,
okay,
yeah!
Yes,
I
was
just
trying
to
get.
You
know,
give
a!
I
guess,
update
on
on
stuff
that
me
and
cejo
are
kind
of
been
working
on
as
well
as
maybe
a
call
out
for
you
know,
help
on
reviewers.
F
You
know
if
you
guys
want
to
get
involved
with
also
the
metrics
portion,
so
couple
things
so
me
and
cj
have
been
working
on
the
in
the
metrics
branch
of
of
you
know
in
the
metrics
branch,
with
quote
a
version
of
the
metrics
api,
and
in
that
branch
we
got
a
few
things
merged
in
where
we're
following
the
spec
up
to
the
point
of
quote
the
pipelining
portion,
as
well
as
the
code
for
getting
the
provider
and
so
forth,
so
we
kind
of
have
a
basic
sdk
up
and
kind
of
working.
F
I
am
currently
working
on
a
pr
that
I
put
there
to
add
some
initial
structure
for
aggregators,
and
so
please
help
us
review
as
necessary
and
in
that
current
pr,
it's
kind
of
big.
But
you
know
in
that
pr,
I'm
trying
to
shift
over
to
using
the
api
that
the
net
team
has
is
included.
F
There's
a
couple
of
issues
that
I'm
working
out
with
tariq
on
it
at
the
moment,
but
for
the
most
part,
that's
there
and
kind
of
working
I'm
running
into
some
issues
with
with
the
github
ci
that
I'm
going
to
need
help
with
from
you,
probably
cjo
in
that
some
of
the
unit
tests
using
the
new
package
is
breaking
on
the
tracing
portion,
which
we
didn't
touch.
F
So
I'm
gonna
looking
to
get
some
help
with
that,
but
in
general,
basically
the
the
at
least
my
concept
is
that
we're
gonna
follow
the
spec
and
we're
gonna
be
moving,
probably
one
step
ahead
of
the
spec,
primarily
for
the
purpose
of
understanding
what
the
next
steps
are
and
to
help
inform
the
the
the
api
sig
as
per
their
request,
that
we
do
so
that's
kind
of
where
we
are
today
and
there's
a
pr
out
there.
So
please
anybody!
Please
come
in
and
offer
your
review.
If
you
wish.
C
Okay,
yeah
and
for
the
ci
failures
I'll
take
a
look
once
I
am
back
so
later
today
afternoon.
A
C
C
Okay,
thank
you.
Everyone
see
you.