►
From YouTube: 2022-02-14 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).
C
C
Okay,
let's
do
we
need
to
add
something
in
the
agenda.
I
mean
to
start
with.
C
Okay,
so
returning
I
mean
just
just
go
ahead
with
the
last
status
meeting.
C
And
still
not
getting
time
to
really
create
a
create
a
local
brand,
create
a
branch
for
that
to
push
my
changes
in
a
remote
branch
and
give
it
to
them.
So
let
me
see
if
I
have
time
today.
I
don't
think
this
week.
Also
I'll
have
enough
time
for
this,
but
well,
let's
see
matrix
implementation.
C
I
did
go
ahead
with
some
more
changes.
Basically,
that
changes
involve
the
in
memory
storage,
the
writable
storage.
I
plan
to
raise
a
pr
for
that.
It's
it's
a
big
change,
so
I'm
just
split
it
splitting
it
into
two
parts,
so
the
first
part
will
be
just
doing
the
actual
measurements
and
the
second
part
will
be
the
collection
so
I'll
raise
the
first
part
of
the
change
to
today.
C
So
probably,
I
think
once
we
have
any
one
type
of
aggregation,
we
can
always
do
the
other
aggregation
implementation,
the
same
line
so
I'll
be
using
the
pr
the
first
pair
today
and
then
second,
we
are
somewhere,
probably
if
it
is
not.
If
I
have
to
just
read
it,
I
really
did
it
I'll
do
it
this
week,
but
if
I
need
to
split
it
into
bigger
parts,
probably
probably
do
it
start
of
next
week,
sometime
yeah,
so
that's
the
status
for
matrix,
so
yeah.
This
is
something
I
think.
Probably.
C
C
C
Yeah
it's
more
complicated,
I
mean
it's,
it's
very
difficult
to
really
the
kind
of
scenarios.
It
has
been
very
difficult
to
figure
out
how
best
to
do
it.
I
mean
three
four
times
I
have
changed
the
implementation
to
make
it
work
and
that
that's
more
for
the
collection
I
think
consuming
the
measurements
are
bit
straightforward,
but
consuming
the
actual
metric
from
that
consumption.
C
How
do
we
maintain
the
delta?
How
do
we
maintain
the
cumulative
matrix?
You
know
that
that
that's
kind
of
complicated
that
is
to
me
it
is
getting
complicated.
So,
probably
once
we
once
I
reach
the
pr
once
I
get
more
comments,
I
think
will
be
in
better
state.
C
D
C
C
C
C
B
C
But
I
think
it's
I
just
saw
that
the
the
github
one
of
the
link
you
posted,
where
it's
basically
in
the
documentation
right
where
benchmark
results
will
not
be
stable
because
of
the
virtual
virtual
machine
configurations.
Every
time
we'll
get
so
yeah,
that's
something
we
have
to
discuss.
We
have
to
think
and
whether
it
does
it
makes
sense
to
have
benchmarks
if
they
are
not
going
to
be
stable
enough
because
of
the
virtual
machine
configuration.
C
C
Yeah,
I
saw
one
comment,
I
think
even
you
also
mentioned
that
probably
it
is
more
stable
in
mac,
but
the
reason
can
be
that
there
are
less
less.
I
mean
number
of
mac
machines
in
within
github.
So
probably.
C
Yeah
that's
another
option,
but
I
think
if
mac
os
works,
I
think
better
to
have
everything
internally,
if
not,
then
maybe
having
another
virtual
machine
spawning
a
virtual
machine
on,
say,
azure
or
aws
and
try
to
get
the
benchmark
results.
That's
another
option.
C
C
Preparing
the
monday
meeting
for
me
putting
it
benchmark
not
stable.
We
already
discussed
that.
C
Let's
try
to
see
what
can
we
do
for
this
anything
else.
You
want
to
add.
C
B
C
C
Don't
know,
I
probably
good
to
see
the
specification,
because
I
remember
specification
thus
says
that
we
should
not
be
using
the
runtime
storage
context
should
not
be
but
yeah.
I
don't
know
if
nothing
there
in
the
specification
not
which
says
that
we
should
not
be
exposing
it.
We
should
be
good
to
do
it.
C
B
C
C
B
C
C
C
C
Supported
platforms,
I'm
just
thinking
what
probably
independencies
you
could
at
least
put
it
here,
something
at
least
actually
somewhere.
We
can
document
it
either
here
or
or
I
mean
even
it's
fine
if
we
can
have
a
bigger
matrix
here
that
for
for
say,
if
we
add
visual
studio
2022
and
for
bazel,
you
can
mention
it
only
works
with
beta
5.2
and
grpc
1.39.
A
Sims
1.43
is
the
latest
stable
release
of
grpc
yeah.
If
we
require
that,
I
mean
I
just
my
concern
is
it
is
too
new
and
if
we
require
that,
maybe
our
consumer
will
have
to
upgrade
that
as
well.
We
can't
share
it
with
some
previous
stable
version.
C
So
come
so
you're
saying
that
if
we
upgrade
it,
we
won't
be
able
to
share.
This
builds
with
the.
A
Yeah,
if
the
customer
is
using
like
an
earlier
version
like
the
1.38
in
their
dependency,
if
not
for
open
telemetry,
then
it
means
we
can't
share
it.
C
Now
we
can
share,
because
we
don't
we
don't
release
the
build
slide.
We
release
the
source
code
and
customers.
C
Should
I
mean
we
don't
really
say
that
customers
should
use
our
build
pipeline
to
build,
build
open
telemetry,
so
they
should
be
using
their
own
grpc
version,
even
though,
if
we
may
be
compiling
with
1.43,
that
does
not
mean
that
they
are
they
supposed
to
use
the
same
value.
They
should
be
using
okay.
A
C
C
But
that
that's
the
problem
still
right,
I
mean
that
does
not.
This
does
not
mean
that
customers
are
supposed
to
use
this
one.
There
may
be
a
customer
who
want
to
use
grpc,
1.40
or
something
we
are
still
enforcing
them
to
use
the
39.1
I
mean
okay,
it
does
not
mean
this
is
our
build
pipeline
and
I'll
say
that
this,
these
all
versions
are
basically
part
of
our
build
pipelines.
C
B
Right,
no,
it's!
It
means
that
maybe
some,
for
example,
otnp
grpc,
will
use
it,
but
if
we
don't
build,
we
will
not
fetch
anything
from
this
one.
Okay,
so.
C
B
B
C
So
then
tom,
it
won't
be
issue
right
that
wasn't
your
concern
right.
C
C
C
A
C
Can
do
that
yeah?
We
can
say
in
fact
libraries
we
can
say
here,
but
the
problem
is
that
this
only
says
for
our
build
pipeline.
So
we
don't
have
any
bill
pipeline
for
2022,
so
adding
it
here
will
not.
We
won't
be
able
to
add
another
another
row
here
to
say:
visual
studio,
enterprise,
2022
and
then
based
on
5.0,
then
another
column
for
grpc.
C
C
C
C
Okay,
this
is
this
is
for
me,
I
think
I'll
race,
the
this
issue,
this
issue
I
raised
it.
This
would
be
part
of
the
metric
one
of
the
first
period
which
I'm
going
to
raise
today.
C
This
I
didn't,
I
did
try
it
saying
doing
a
jd
yeah
I
got
built
with
stl.
I
did
try
it,
but
somehow
I
could
not
reproduce
the
issue
so
we'll
try
one
more
otherwise
I'll
ask
him
how
to
do
it.
C
Okay,
how
to
build
this
one
yeah,
I
just
no
so
okay!
I
I
think
I
modified
one
of
our
test
code
and
I
just
put
there
and
then
then
just
build
it
with
that
so
yeah.
I
I
didn't
include
these.
I
didn't
use
this
this
step,
but
I
just
modified
our
existing
test
code,
replace
this
file
there
and
just
build
it
with
that.
But
there
was
no
error
so
just
doing
it
for
doing
this,
and
then
using
this
in
our
test
code
and
trying
to
build.
C
A
C
Hey
tom,
can
you
look
into
this
whenever
you
get
time,
I
mean
this
is
something
I
think
the
visual
studio,
2022.