►
From YouTube: 2021-06-23 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
Yeah
and
yeah,
I
didn't
drink
coffee
until
I
moved
back
here
like
oh,
I
guess
a
long
time
ago
now,
15
years
ago
now,
but
but
the
the
dreary,
the
long
dreary
winters
are
very,
very
I
don't
know
make
you
want
to
drink.
Coffee
have
something.
A
Yeah
that
would
explain
why
seattle's
like
america's
home
of
coffee,
it
rains
all
the
time.
C
B
All
right,
we
don't
have.
Oh,
how
did
the
did
the
release
work
for
you.
C
E
B
C
C
D
B
I
threw
this:
oh
yes,
yes
and
oh
yes,
both
of
you
are
here
so
the
problem
with
this
is,
I
think
that
if
you're
running
the
java
agent,
the
java
agent,
the
bridge,
will
the
library
instrumentation
will
go
over
the
bridge
and
this
will
be
stamped
onto
the
library
instrumentation
spans.
Also.
A
B
C
C
C
C
B
Yeah,
that's
fine!
Let's,
let's
kick
that
down
the
road,
then
I
mean
I
think,
that's
something
we
can
change,
I'm
okay
with
changing
later.
Also,
I
don't
think
our
instrumentation
names
are
like
public
contract
sort.
C
A
C
C
C
A
Implemented
the
method
for
ignoring
the
task
classes,
so
we
used
to
have
this
kind
of
huge
list
of
test
classes
with
comments.
Why
are
there
ignored?
Why
shouldn't
we
add
state
to
them?
And
I
first
think
I
moved
that
to
a
try
and
the
second
thing.
I
tried
to
split
that.
So
we
now
have
several
different
ignored:
something
spies
in
different
instrumentation
packages
and
the
global
one
got
a
bit
a
bit
smaller.
A
B
A
That
was
kind
of
the
point,
because
even
if
you
do
not
apply
instrumentation,
you
might
have
tasks
that
carry
over
states
somewhere
and
yeah.
A
C
A
Yeah
get
much
more
complex.
C
E
B
Yeah
the
task
ones,
we
definitely
need
like
it's
functional,
not
just
optimization
the
the
global
ignores
the
global
ignores
and
the
or,
I
guess,
the
additional
class
load,
the
the
additional
library
ignores.
Also
I'm
curiou.
I
I
struggle
with
how
much
performance
like
the
what
how
much
we're
getting
improving
the
startup
time
by
adding
all
those,
because
it
seems
sort
of
ad
hoc
of
what
we
put
in
there
and
what
we
don't.
B
So
this
list
here
of
things
we
say
to
the
only
the
prem.
The
main
point
of
this
is
to
improve
startup
time,
and
so
I'm
just
kind
of
curious.
Like
I
mean
it's
kind
of
very
ad
hoc
of
what
we
throw
in
here
and
what
we
don't.
A
B
C
C
C
D
B
And
sometimes
it
requires,
you
know
the
the
extends
ones,
although
we
pretty
much,
we
have
the
class
loader
optimization
things,
but
even
then
like,
if
you
have
that
on
there
like.
If
you
have
spring
on
your
class
and
we
have
an
extended
spring.
C
B
I
mean
it
might
especially
now
with
the
the
tree
that
try
the
the
tree
eye.
The
actually
honorable
agrees
that
it's
a
try
agreeing
with
aikido,
so
I'm
gonna
go
along
with
with
them
and
call
it
a
try
again.
B
It
might
be
interesting
to
if
there
was
a
like
way
to
auto
generate
these
sort
of
from
our
our
instrumentation
yeah.
Basically,
just
a
big
old
list
of
everything
that
we
don't
instrument
like.
E
C
B
But
it
would
know
like
say
within
the
spring
libraries
that
we're
testing
we
know
all
of
their
subclasses.
C
And
we're
gonna,
so
I'm
also
sort
of
working
on
expressing
a
gradle
plug-in
for
the
whitebody
computer
class
thing
we
have
right
now,
just
because
usually
you
use
that
gradle
plug-ins
for
that
sort
of
thing,
and
I
don't
want
to
call
that
muzzle
anymore,
like
I
think,
muzzles
are
checking
right,
not
the
code
gen.
So
I'm
thinking
of
just
calling
it.
D
D
C
C
Yeah
working
on
migrating,
all
of
that
stuff,
like
once
everything
is
caught
in
I'll,
consider
that
sort
of
migration
complete
and
the
next
step
is
probably
going
to
be
to
extract
some
of
those
files
into
a
project
we
publish.
So
we
can
finally
publish
these
plugins
we've
been
wanting
to
do
that
for
a
while.
C
B
That
that's
what
the
conventions
things
are.
Those.
C
B
Oh
okay,
so
the
the
convention
thing
was
okay.
They
yeah.
C
C
C
B
C
B
C
It's
just
I
mean
it
used
to
be
a
bin
tree,
and
now
I
don't
know
what
it
is,
but
yeah
we'll
have
to
register,
and
I
it's
a
long
time
we're
going
to
register
and
stuff,
but
it
was
pretty
easy.
I
think
you
can
like
by
default.
It
will
publish
into
this.
Its
own
sort
of
maven
coordinates
gradle.plugin.org,
but
as
long
as
we
can
include
the
ownership
of
our
coordinate,
we
can
publish.
C
C
C
B
C
C
So
the
fix
tests
on
windows,
the
best
solution
to
that
is
to
migrate.
All
our
tests
to
java
then
test
containers
correctly
doesn't
like
it
skips
the
test.
If
it
doesn't
detect
docker.
Let's
do
that,
but
they
don't
have
the
functionality
very
easily
available
for
non-junit
users.
C
B
A
C
B
B
B
A
A
This
is
the
one
that
improves
the
test
assertions
that
used
to
fail
your
test,
if
you
instrumented,
ignore
type
and
do
in
the
one
of
those
additional
recognized
ignore
types,
I
improved
that
so
that
you
can
choose
whether
it's
okay
to
keep
it
ignored
or
whether
it
should
be
actually
allowed
so
for
spring
integration,
for
example,
ignoring
the
whole
messaging
package
is
perfectly
okay,.
A
This
actually
duplicates
it
so
that
there's
ignore
spring
messaging
in
the
additional
library
configuration
and
when
the
spring
integration
tests
run,
they
instrument
something
there.
I
don't
even
know
what,
because
it's
not
really
necessary
for
anything
and
what
this,
what
this
class
does
is
basically
confirms
that
yeah,
it's
okay,
to
ignore
that
those
classes.
A
A
A
It
would
check
the
additional
library
class
if
we
instrumented
messaging
a
messaging
class,
and
it
turned
out
we
do
so,
it
would
fail,
but
with
this
with
this
new
library,
specific
configurer,
we
won't
instrument
this
or
again.
We
if
we
do,
even
if
we
allow
this
once
the
session
detects
that
we've
estimated
the
type
that
was
ignored
in
additional
library
computer,
then
we'll
check
the
instrumentation
specific
one
and
see
what
the
instrumentation
outer
wrote
with
the
instrumentation
author
said
that
it's
okay
to
instrument
it
or
we
should
ignore
that
and
then
it
won't
fail.
A
B
Ignored
right
so
is
there
so
I'm
still
not
quite
following
what
what
the
why
we
have
it
here
also.
A
But
if
you,
if
you
add
the
ignorer
to
the
to
the
library,
it's
this
one
yeah
this
one,
then
it
won't
instrument
them
at
all.
So
it
kind
of
stuff
like
the
confirmation
that
the
additional
library
says
that
we
should
in
the
instrument
messaging-
and
this
one
says
yeah
no
disturbance
messaging-
is
exactly
what
we
wanted.
B
Okay
yeah-
I
was
just
thinking
originally
that
this
part
of
your
goal
here
was
to
split
out
the
additional
libraries
into
their
instrumentations.
B
A
Because
if,
if
I
just
simply
removed
the
messaging
package
from
the
additional
library
configurer
class,
it
it
won't
ever
be
detected
in
tests
right.
So
if
you
actually
kind
of
accidentally
instrument
a
class
from
the
package,
tests
won't
notice
that
the
sessions
will
notice
that
and
they
won't
fail.
B
B
And
that's
because
if
you're
running
the
tests
not
in
spring
integration
but
in
a
different
module
yeah,
for
example,
okay
and.
A
B
B
All
the
classes
in
the
kafka
library
that
we
want
to
instrument
and
we
could
create
that
tree,
try
of
all
those
classes,
but
first
and
we
could
stick
that
all
in
the
kafka
instrumentation
itself.
B
But
I
think
the
problem
the
trick
is
with
spring,
where
some
of
the
like.
Where
do
we
put
that
those
ignores
for
like
spring
messaging,
because
we
have
a
couple
different
inspirations
that
could
touch
that
yeah.
A
E
B
Like,
like
the
stuff
you've
been
doing,
is
like
slowly
untangling
the
stuff
so
that
visualize,
where
it's,
where,
where
to
go,.
D
A
E
C
C
Most
libraries,
of
course,
the
instrumentary
this
meant
like
http
framework.
It
has
all
these
general
features,
but
if
this
async
stuff
is
does
not
fall
into
that
goal,
then
it
doesn't
have
to
use
it
right.
Is
that
like?
Do
you
think?
That's
the
problem
here?
That's
too
much
phase
is
not
a
good
fit.
E
A
And
it
is
confusing
so
yeah
this
is,
it's
probably
only
useful
for
our
all
those
generic
annotation
or
method
instrumentations
that
don't
know
what
it
is
that
they
can
instrument
any
code
anyway
I'll
try
to
get
it
back
in
shape
or
try
to
make
it
presentable
this
weekend,
we
will
have
to
think
about
splitting
it
to
a
separate
kind
of.
Like
I
don't
know,
library,
internal
modules.
A
A
Oh,
that
was
just
your
that
was
standard,
cast
loader
confusion
and
it
didn't
work
as
expected.
So
I
are
you,
as
I
never
commented,
I'd
probably
just
remove
this
whole
reflection,
hug
and
just
move
those.
C
A
C
C
B
It
sure
would
be
nice
to.
I
would
love
to
be
able
to
run.
Like
I
mean
our
smoke
tests,
don't
really
do
very
much
coverage.
The
way
that.
C
B
Containers,
somehow
I
don't
know
it's
this
stuff
is
all
this
stuff
is
a
lot.
E
C
Maybe
allow
lori
to
give
it
a
bit
like
I
feel,
as
if
any
time
I
asked
laurie
to
think
about
something,
he
comes
up
with
an
awesome
solution.
So
hoping
that
happens
this
time,
because
yeah
being
able
to
build
a
repo
from
any
commit
is
a
good
feature
of
repositories.
I
think
so
us
we
aren't
really
in
that
state
of
some
of
our
repo
dependencies
are
flicky
like
this.
B
C
B
B
Great
all
right
I
mean
the
yeah
maven
repo
is.
B
B
B
C
Yeah,
I
think
we
talked
a
bit
where
I
thought
it
might
be
a
relatively
common
thing,
because
it's
so
easy
to
create
a
new
stuff
in
grpc.
If
I
realized,
we
don't
instrument
stubs,
we
introduce
instrument
the
channel
and
it's
extremely
rare
for
apps
to
install,
I
mean
it's
bad
for
now,
essentially
multiple
channels,
so
that
doesn't
mean
our
instrumentation
should
break.
Of
course,
but
technically
I
have
a
feeling.
This
app
is
just
not
handling
grpc
correctly.
B
C
A
A
C
E
B
All
right
anything
else.
A
I've
got
one
minor
question:
we
have
those
we
use
before
the
a
after
ga
tags
or
labels
on
our
issues.
B
B
B
E1
we
should
probably
ask
nikita
on,
let's
see
after
ga,
let's
get
rid
of
after
ga,
and
then
let's
ask
we'll
ask
akita
on.
E
B
A
B
Yeah
we
we
used
to
set
aside
some
time
and
evening
to
do
like
a
little.
E
E
B
C
That's
the
main
problem.
I
think
we
could
also
time
box
in
the
sign
and
then
just
never
work
on
them
and
never
be
checked
in
on
and
then
it's
effectively
the
same
right
now.
So
that's
where
having
a
engineering
manager
can
help
sort
of,
I
don't
think
we're
in
dire
streets
or
anything
though
yeah
we.
B
All
right
well
have
a
good
day
first
shot
next
week.
Finally,
oh
no
way,
that's
a
lot
faster
than
you
thought
it
was
going
to
be.
C
C
E
B
Got
the
we'll
do
an
open,
telemetry
lunch
or
something
yeah?
If
not,
let
me
know
and
I'll
try
to
get
up
to
seattle.
A
I
mean
I'm
already
vaccinated.
I
got
the
second
shot
two
weeks
ago
exactly
two
weeks
ago,
but
oh.