►
From YouTube: 2020-09-08 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
B
B
I
bought
a
new
keyboard
and
whenever
I
use
the
numpad,
if
I
type
quickly
it
just
doubles
all
the
like.
All
the
numbers
get
printed
twice
similar
to
what
you're.
B
A
A
A
A
C
A
B
A
Okay,
yeah,
I
guess
we
don't.
Okay,
both
of
those
journeys
in
one
minute,
cool.
B
E
Unfortunately,
I
was
not
in
the
morning
meeting,
so
I
cannot
tell
you
anything
that
happened
there,
but
we
can
talk
about
different
other
things
if,
if
there
is
any
blocker
for
you
guys
under
arc
genes
that
we
can
un
unblock
or
help
with,
let
me
know
that
so
I
can
make
sure
that
things
are
moving
on
the
specification
side
or
or
any
other,
where
I
can
influence
that.
D
E
Oh,
I
know
I
know
so.
The
whole
idea
is
the
whole
idea
is
in
the
specification.
E
There
are
a
lot
of
requests
that
are
coming
right
now
for
from
for
with
the
idea
that
I
think
this
is
good
for
before
to
have
it
in
the
specs
before
g,
even
though
it's
not
necessarily
a
required
thing
just
to
kind
of
to
have
it
before
g,
because
whatever
somebody
believes
it's,
it's
good
to
have
it
before
ga.
E
So
I
think
that
whole
idea
was
more
like
to
to
kind
of
freeze
everything
that
is
not
necessary
for
the
ge
and
just
merge
things
that
are
required
for
ga
for
the
foreseeable
feature.
Until
we
achieve
the
the
goal
of
merging
everything
that
we
we
marked
as
required
for
g,
does
it
make
sense.
C
E
E
So
so
the
whole
idea
is:
there
are
a
bunch
of
issues
still
mark
required
for
ga
in
the
specs,
and
we
should
focus
on
that
and
as
maintainers
and
everything
we
should,
we
are
okay
to
ignore
any
other
thing
that
is
not
as
marked
for
for
ga
required
for
ga,
like
to
to
kind
of
everyone,
has
a
limited
pool
of
time,
amount
of
time
that
we
can
allocate
per
day
so
just
focus
on
this.
Instead
of
anything
that
is
coming.
C
That
makes
sense,
so
I
guess
the
only
issue,
I'm
somewhat
concerned
about
at
least
from
the
x-ray
perspective
is
the
non-random
trace
ideas
issue,
eight,
nine
six,
that's
marked
for
after
ga,
but
if
it's
not
addressed,
for
example,
like.net
may
just
not
be
able
to
support
x-ray,
and
so
I'm
wondering
how
to
make
sure
we're
not
blocked
on
that.
D
C
D
D
D
D
That
it's
fine
put,
it
put
it
as
a
pr
just
to
add
it
in
the
sdk
and
take
it
from
there.
I'm
I'm
confident.
E
A
C
A
E
Yeah,
I
agree.
I
agree
that
it
may
not
work
overall,
certainly,
but
but
right
now
I
don't
believe
they
will
change
soon.
These
one
another
option
is.
E
I
I
do
agree
with
you
so
anurag
I
don't
know
so.
The
point
that
sergey
has,
which
is
a
valid
point,
is
it
will
be
hard
for
you
to
ensure
that
the
entire
all
the
systems
that
are
involved
in
this
trace
will
will
use
this
custom
id
generator.
So,
even
if
you
give
you
this
option
which
you
in
this
in
the
current
solution,
you
may
need
it,
it
will
be
very
hard
to
ensure
that
the
whole
systems
will
will
follow
these
things.
E
So
I
don't
know
how
to
solve
that.
Maybe
an
option
could
be,
but
I
don't
know
I
another
option
could
be
to
add
a
plugin
that
every
time
when
you
generate
a
trace
id,
we
completely
randomly
generate
it,
but
we
use
the
trace
state
and
we
put
into
the
three
state
the
start
time
of
the
trace
in
the
way
that
x-ray
wants
or
or
any
start
time,
because
that's
what
x-ray
needs
and
then
and
then
and
then
from
traystate
plus
the
trace
id
you
can
compose
the
new
x-ray
trace
id.
C
That
has
the
same
problem
right.
The
plugin
has
to
be
used,
and
so
it's
similar
to
configuring,
the
id
generation.
E
Even
the
id
generation
is
not
there
that
maybe
if,
if
every
sdk
allows
you
a
custom
plugin
to
to
run
as
part
of
the
three-sided
generation
or
or
sampling
decision
and
manipulate
the
trades
that
you
can
do
this
but
sergey
I
don't
know,
I
mean
we
are
not
here
to
solve
their
whole
problem,
and
I
think
I
think
I
think,
unless
they
will
be
willing
to
accept
completely
rounded
trees
id,
they
will
always
have
trouble
with
with
like
having
a
very
complex
and
large
system
that
in
some
subsystems
this
may
not
be
configured
well,
but
I'm
happy
to
give
the
trace
id
as
as
an
intermediate
solution
for
them-
and
I
don't
know,
do
you
think
sergey
is
probably
a
hacky
solution
and
it
may
cost
us
in
the
future
that
that
we
offer
this
this
this
right.
A
I
have
two
provinces
that
I
that
I
have
when
I
I
don't
feel
either
of
them
as
a
blocking
it
just
setting
a
timeline.
So
first
problem
is:
I
have
a
few
customers.
Who've
been
encoding,
some
personal
information
to
ids
one
did,
I
p
address
and
another
machine
name,
so
it
was
kind
of
a
not
my
username.
I
mean
so
it's
kind
of
information
exposure
that
made
possible
unintentionally
just
because
users,
just
like
I
mean
I
have
this
piece
of
information
flowing.
A
Why
wouldn't
I
encode
some
useful
things
here
and
that
may
be
bad
from
like
just
pure
like
security
perspective
or
privacy
perspective,
and
second
one
is
we
made
it
in
dotnet
to
be
part
of
the
net
framework
itself
and
it's
like
at
this
stage.
It
will
be
really
hard
to
change.
So
if
you
make
this
requirement
for
ga,
then
we
will
need
to
come
up
with
some
workaround
rather
than
actual.
E
But-
and
it's
I
mean
your
point-
is
net
already
did
a
lot
of
work
and
it's
amazing
work
that
they
did
and
I
don't
want
them
to
not
be
considered
compatible
with
open,
telemetry
g8,
just
because
missing
this
feature,
but
I
also
think
that
we
can
make
it
in
a
way
that
we
added
to
the
change
log.
We
say:
okay,
this
is
not
required
to
be
considered,
ga
open,
telemetry
or
or
we
can
dotnet
can
ship
it
in
the
next
version.
E
C
E
A
Dotnet
and
like
it's
not
like
dotnet
dictates
what
supposed
to
be
in
specs.
It's
just
like
first
timing
and
second,
is,
I
think
it's
so
my
problem
is
like
it's
a
race
of
requirements.
So
it's
a
one
use
case,
which
is
a
big
use
case.
So
it's
a
whole
aws.
It's
like
huge
use
case,
but
it's
one
and
like
we
need-
and
it's
not
a
use
case,
that
by
necessity
it's
mostly
like
this
is
how
we
design
system
and
we
don't
want
to
design
any
anything
else.
A
Like
I
yeah
we
to
make
sure
that
yeah,
it's
needed
for
people.
E
A
Yeah,
it's
a
temporal
database,
I
understand,
but
it's
it
opens
door
for
abuse
and
makes
net
less
foolproof
and
open
telemetry
in
general.
So,
like.
B
A
I
hate
to
see
this
like
how
to
not
sample
your
request,
like
change
your
trace
id
to
abc000
and
like
I
don't
want
this
kind
of
guides
to
be
in
in
a
while.
E
I
I
see,
I
see
what
you
mean
sergey,
but
in
the
end
we
we
have
an
api
correct.
Everyone
can
plug
in
completely
new
sdk
for
our
sdk
and
provide
this.
So
I
don't
think
I
don't
think
we
can
stop
the
the
most
important
things
we
can
stop
in
the
api.
So
a
lot
of
abuses.
E
A
E
C
A
A
B
A
Using
azure
and
they've
been
worried
that
azure
will
imply
some
from
the
usage
pattern.
If
you
use
usage
would
be
attributed
with
some
time
stamps
and
maybe
additional
parameters
and
cloud
can
understand
how
like
what
the
actual
usage
numbers
from
the
customers.
I
cannot
ask
you
more
details,
but
yeah
that
was
yeah
yeah.
C
C
A
E
C
E
At
one
point,
I
had
a
discussion
with
somebody.
It
was
the
same
problem
like
you
know,
for
example,
you
have
a
big
client
and
if
they
send
you
trace
ids,
you
can
look
how
many
in
the
for
example,
you
can
inject
the
trace
id
to
their
system.
Let's
say
your
uber
is
using
google,
I
don't
know
if
there
is
isn't
it
or
not,
but
you
make
a
request.
E
E
E
I
was
talking
to
marcin
from
from
springsloot
and
he
asked
us
if,
if
we
are
willing
to
to
provide
a
shin,
no
sorry
an
implementation
of
our
open,
telemetry
api
that
redirects
into
brave
they
are
willing
to
change
spring
to
to
use
the
open,
telemetry
api
everywhere.
E
As
long
as
we
we
give
that
that
that
implementation
to
them-
and
we
will
discuss
that
in
the
in
the
java
discussions
on
rug.
But
I
think
it
sounds
interesting
for
having
spring
using
open
telemetry.
We.
A
E
C
E
Yes,
so
they
are
asking
us
to
do
that,
and
probably
we
may
have
to
to
do
it
and
maintain
that
we
can
discuss
during
one
of
the
java
sheets,
but
an
fyi
and
fi
for
everyone
that
we
are
in
discussion
with
the
springs
community
and
stuff.
We
need
to
also
discuss
with
micrometer
a
bit
about
this,
but
it's
a
bit
premature.
E
You
may
want
to
self
nominate
if
you
consider
that
you
have
time,
and
you
would
like
to
to
to
be.
C
C
E
I'll
think
about
it
and
anyone
from
google
as
well
guys,
I
mean
say
you
are
at
google,
you
can
tell.
E
Yeah
anyway,
think
think
about
and
yeah,
okay
yeah.