►
From YouTube: 2020-12-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).
B
C
Happy
december
22nd
23rd
y'all,
we
almost
we
almost
made
it.
B
B
C
Well,
we
are
giving
people
in
a
minute
I'm
going
to
phone
a
friend.
C
So
the
undertow,
the
1643,
the
pr
that
just
won't
quite
get
over
the
finish
line.
The
latest
problem
is
that
nikita
snuck
in
the
undertow
pr
yesterday
and
it
does
some
new.
C
So
I
don't
know
if
you
saw
this
what
he
wanted,
because
of
that.
Oh
maybe
I'll
just
put
that
key
holder
in
our
api
package
for
now.
Oh.
C
I
don't
think
it's
something
that
the
tests,
the
new
tests
caught,
that
was
broken
already,
I'm
not
totally
positive,
but
what
I
so
at
first
I
was
like.
Oh
okay,
I
know
what
to
do
in
the
agent
for
testing.
I
need
to
do
the
same
thing
over
here,
but
this
is
only
capturing
the
things
in
the
agent
exporter.
C
B
B
C
C
B
C
That
was
going
to
take
me
a
while
to
figure
out.
B
C
Have
a
feeling
I'm
going
to
just
move
it
out
and
create
an
issue
to
deal
with
that
later,
because
I
just
want
this
pr
to
get
merged.
C
Yeah,
hoping
that
akito
is
going
to
join
tonight
so
that
I
can
pester
him
to
approve
it
or
find
out
exactly.
D
C
He
wants
to
unblock
that
yep,
but
in
the
meantime
I'm
sure
I've
seen
y'all
are
fast
and
furious.
Still
in
the
non-stop
in
the
sdk
repo.
B
B
B
B
C
Doesn't
wonder
I
had
a
question,
do
you
do
we
lose
anything
by
having
the
auto
configure
spi
stuff
outside
of
the
main
artifact.
B
A
B
A
E
C
B
And
so
if
the
mutators
add
spin
prices
and
update
face
configure
gone
already,
the
agent
loses
its
way
of
custom
distros
configuring,
the
sdk.
Actually
so
we're
going
to
have
to
either
define
a
configuration
spi
in
the
agent,
which
is
probably
a
good
idea,
because
if
we
can
avoid
the
whole
shading
weirdness,
it
does
make
it
a
bit
easier,
but
that
or
we
might
use
the
auto
configuration
agent
if
we
want
to
that's,
also
an
option,
but
we
are
going
to
run
into
that
soon.
B
C
B
A
Exactly
I
think
the
thing
so
the
thing
I
don't
know
that
blogdan
will
be
okay
with
is
the
the
strategy
of
just
doing
a
very
loud
log
and
setting
off
a
alarm
and
opening
up
a
youtube
video
when,
when
someone
tries
to
get
access
to
the
global
before
it's
configured,.
A
It's
actually
just
funny
anecdote
when
I
was
first
learning
how
to
do
java
agent
at
new
relic.
The
first
tutorial
that
we
did
was
to
actually
make
it
so
anytime.
You
started
up
your
program.
It
made
it
played
an
audio
file
as
a
part
of
the
java
agent
in
your
pre-me.
A
Exactly
I
think
it
was
a
meowing
cat,
though
I
think
that
was
the
what
the
tutorial
had
like
provided
an
audio
file
with
the
meowing
cat,
so
yeah.
I
I
think
it's
fine
and
I
think,
unless
there's
some
super
weird
extraordinary
case,
it
should
always
be
possible
for
you
to
put
a
static
initializer
in
your
main
yeah
in
your
main
and
initialize
things
before
anything
can
get
access
to
it.
E
A
Because
imports
obviously
are
not
a
real
thing:
they're
they're,
just
a
compiler
hack,
so
that
I
mean
I
think,
that's
the
I
think
there
you
should,
unless
you're
doing
some
weird
agency
stuff,
which
you
all
can
you
know
solve,
you
should
always
be
able
to
do
some.
You
do
your
initialization
in
the
static
main.
The
only
thing,
the
only
cases
where
I
don't
know
about
the
possibility
is,
let's
say,
you're
in
an
app
server
and
you're,
just
deploying
a
war
like.
Are
you
going
to
be
able
to
or
is
it
are
there?
C
How
would
so
if
open
telemetry
api
was
up
at
that
level
at
the.
A
A
B
A
B
A
That's
probably
okay.
I
just
want
to
think
through
these
weird
yep
yeah.
B
A
Cases
I'm
also
thinking
about
like,
like
the
spring
like,
if
I'm
using
spring
boot,
there's
a
whole
bunch
of
stuff.
That's
going
to
happen.
Well,
I
guess
you,
if
you
can
do
it
in
your
static
initializer
that
still
happens
before
the
boot.
The
spring
boots
yeah.
C
Run
time
lambda.
B
I
think
at
an
entry
point
you
might
have
four
classes
that
you,
you
call
the
static
in
each
class,
but
I
think
and
again
I
think,
the
auto
configure
that
could
be
a
viable
alternative
if
you
do
really
want
an
spi
driven
approach
like
the
main
difference
in
the
sp,
I'm
thinking
of
auto
configure,
rather
than
returning
fact,
providers
they're,
just
configurers
that
can
configure
a
builder
that
solves
the
problem
of
not
being
able
to
mutate
it
because
you
can
have
multiple
configures
and
that
would
work
too.
I
think
so.
A
B
So,
of
course,
the
easy
one
is
to
expect
the
user
to
call
the
initialize,
but
again
it's
our
artifact,
so
we
can
easily
call
it
with
reflection
from
get
from
the
global
getting
if
you
want
to.
I
think
it's
fine,
and
so
that's
probably
what
we
would
do,
and
so
we
don't
lose
anything
compared
to
what
we
have
now,
while
still
having
the
core
experience,
not
magicky
seems
like
we
get
the
best
of
both
worlds.
A
I'm
just
thinking
through,
I
think
I
mean
to
my
mind.
A
lot
of
these
problems
are
probably
I
mean
they're
they're,
not
not
not
real
problems,
but
they're
definitely
ones
that
if
we're
willing
to
provide
some
very
clear
documentation
and
best
practices
and
here's
how
you
should
deal
with
this
issue,
here's
how
you
should
configure
your
sdk
here
are
the
options
and
make
sure
it's
super
clear.
A
I
don't
know
if
you
saw
I
put
in
an
issue
today.
We
actually
had
some
feedback
from
the
field
about
trying
to
find,
because
we've
been
changing
our
artifact
names.
Like
every
other
version,
they're
like
I
can't
figure
out
what
the
artifact
names
are
called
and
I
was
like.
Oh
if
you
use
the
bomb
well,
what
if
he
used
the
bomb
and
he's
like
I
didn't
know,
you
could
use
a
bomb
in
gradle.
A
I've
only
done
that
in
maven
and
like
oh
well,
so
there's
probably,
I
think,
there's
some
best
practice
documentation
that
we
really
need
to
provide
to
people,
because
I
think
those
people
aren't
necessarily
going
to
understand
how
to
use
the
bomb
and
how
to
understand
how
to
use
what
we've
published
in
an
effective
way
so
put
in
that
issue.
Just
to.
I
think
we
need
to
get
our
docs
much
cleaner
and
more
explicit
and
simpler
and
upfront
before
before
release.
A
So
I
think
I
think
a
lot
of
that
would
probably
obviate
a
lot
of
these
issues,
especially
for
people
who
maybe
have
kind
of
maybe
have
gotten
used
to
the
auto.
The
magical
way
it
works
today
is
making
sure
there's
a
good
path
to
get
from
here
to
there.
So,
as
I
said,
I'm
not
the
one
arguing
about
it.
I
think
this
we
just
need
to
make
sure
we
can
get
buggy
on
board
and
nikita
is
there
lurking
with
no
camera
and
his
mute
he's
just
like.
B
B
B
Even
yeah,
I
think,
espionage
like,
as
you
say
whether
bogdan
also
thinks
it
sounds.
Okay,
a
lot
of
configurable.
What
not
maybe
more
interesting
is
the
care
I
just
sent
about
the
exporter
and
I
don't
know,
like
that's,
also
up
your
alley
nikita
if
you
happen
to
have
a
chance
to
discommit
right
now,
just
one
idea
of
trying
to
make
things
easier.
A
A
C
B
B
E
E
A
B
D
B
B
D
Definitely
wait
and
and
and
what
what
class
we'll
deal
with
converting
from
spam
to
spam
data.
B
D
D
D
D
A
B
A
How
does
this
work
with
all
of
the
environment
variables
around
the
batch?
Like
the
span
processor
configuration.
B
A
They're,
independent
yeah,
the
environment
variable
stuff
is
weird
right
in
a
weird
place
right
now,
because
it
actually
none
of
it
lives
in
the
sdk
at
all.
It
all
lives
over
in
the
exporter
package.
I
think
well,
except
maybe
this
batch
spam
processor,
like
it's,
spread
across
a
bunch
of
places
right
now,
like
from
a
from
a
module
perspective
right,
yep,.
A
That
it
feels
like
we
have
a
way
forward
to
finishing
that
piece
of
our
configuration
story.
If
not,
I
feel
like
we're
back
stuck.
I
don't
know
yep
well,
thanks
for
walking
through
that.
Hopefully
bogdan,
we'll,
take
a
look
at
that
tomorrow.
The
comments
tomorrow.
B
D
Well,
you
certainly
are
walking
into
in
the
right
direction.
That's
for
sure.
I
I
wanted
to
get
like
my
hands
on
the
final
version
like
when
you
said
you
are
done,
but
you
know,
but
you're,
not
one
one
at
all.
Yet
in
that
time
I
want
wanted
to
squeeze
in
and
to
check
once
again
if
configuration
makes
sense
both
for
agent
and
for
vendor
gui.
A
Next
step,
actually,
if
we
could
create
the
auto
configuration
module,
because
we
can
do
that
independently
of
the
other
changes
right,
we
can
get
that
in
place,
get
it
prove
that
it
works
and
show
that
it
works
and
then
rip
it
out
of
the
sdk
or
api
and
sdk.
It
seems
like
that's
a
good
path
forward.
B
Okay,
yeah.
That
makes
sense.
I
think
the
biggest
thing
I
wanted
to
confirm,
with
the
remove
sp
discussion
was
less
about
the
sdk
configuration
and
more
about
the
custom
sdks,
and
I
think
I
got
the
confirmation
that
no
one
really
cares
about
those.
So
we'll
just
focus
on
the
auto
configuration
story
for
the
sdk
itself.
A
Yeah,
I
don't
know
it's
interesting.
I
don't
know
whether,
like
it'd
be
interesting
to
hear
what
christian
says
about
how
dynatrace
is
doing.
It
they're
also
working
off
a
fork
that
still
supports
java
7..
So
I
have
no
idea
what
their
code
base
must.
Look
like
at
this
point.
A
D
B
B
C
B
D
D
B
B
B
Yeah,
I
think
so,
but
I'm
gonna
try
prototyping
it
and
we
can
see
what
it
looks
like,
but
I'm
guessing
it
would
be
yeah.
I
hope
we
don't
have
to
shade
it
like.
I
think
one
problem
right
now
is
all
our
sps
are
in
the
api,
so
we
have
to
shade
it.
If
they
move
out,
we
wouldn't
have
to
shade.
I
think
that
that
might
be
a
nice
benefit
from
that.
Also.
B
B
A
C
Yeah,
I'm
glad
that
that
several
that
a
bunch
of
us
are
are
out
because
it
would
be
harder
if
there
was
a
flurry
of
activity
going
it'll
be
nice.
If
it's
I
don't
know,
what
are
you
doing
honorary
you
can
create
a
flurry
of
activity
on
your
own.
I
know.
B
B
B
C
Hey,
I
just
discovered
something
interesting
with
our
build.
The
github
action
builds
that
they
build
against,
they
merge
into
mast
or
they
merge
master
into
your
pr
first
before
they
build
it.
Have
you
seen,
I
don't
know
yeah
well,
so
I
was
so
confused
today
because
the
the
14,
the
1643,
the
the
the
big
one,
started
failing
on
undertow
tests
and
I'm
like
wait
a
minute
as
I
went
to
run
it
locally
and
I'm
like
there's
no
undertow
in
here,
because
it
just
merged
yesterday.
C
So
I
was
like
how
can
the
build
be
failing
on
that
that
code
and
I
finally
dug
in
and
it's
that
checkout
action
that
we
use
it
like
applies
the
pr
to
the
to
master
as
if
the
merge
happened.
B
C
C
All
right
nikita:
are
you
ready
to
talk
about
1643.
C
B
D
C
I
want
to
talk
about
what
do
you?
What
do
you
want?
Oh,
I
did
the
undertow
you're
not
going
to
like
this
too
much,
but
I
had
to
back
out
your
cool
thing
to
do.
Have
things
going,
instrumentation
have
their.
C
I
will
open
a
issue.
We
have
to
figure
out
how
to
make
it
work
in
the
new.
C
D
C
I
added
doc
so
look
at
the
doc
trying
to
think
of
what
else
you
asked
for.
Oh,
there
were
a
couple
things.
Let's
see.
C
I
didn't
resolve
a
couple
things
I
was
going
to
check
this,
I'm
not
sure
I'd
have
to
test
that
and
honorag.
Maybe
if
you
can
answer
this
one.
B
B
B
B
C
A
Hey
we
had
a.
We
had
a
question
from
one
of
our
field,
folks
today
about
where
they,
what
the
maven
coordinates
would
be
for
the
new,
the
runtime
metrics
after
they
got
moved
over
from
the
sdk
extension,
and
I
couldn't
figure
out
how
they
could
actually
grab
those.
A
C
Yes,
so
nothing
there
so
should
be
able
to
search
runtime,
metrics,
runtime
library.
A
C
Okay
yeah,
so
we
we
split
we're
using
two
different.
Well,
I
guess
three
different.
Well,
we
have
io
open,
telemetry
instrumentation,
and
then
I
open
telemetry
java
agent.
Isn't
it.
C
A
A
I
don't
I,
I
have
a
feeling-
that's
not
like
how
to
find
this
isn't
documented
anywhere.
At
the
moment
at
least,
I
couldn't
find
it.
No,
no
okay!
C
Yeah
yeah,
I
think
that's
yet
another
reason
why
our
library
instrumentation
will
not
be
ga
for
a
while
a.
C
All
right
any
other,
so
it
sounds
like
next
week
we'll
just
we'll
cancel
all
meetings.
B
So
for
the
next
release,
so,
first
of
all
nikita,
I
know
you
were
talking
about
a
point
13.1,
but
does
punk
not
need
that
anymore
for
the
spring
batch
stuff,
just
wondering
ask
again
see
we're
talking
about
a
point,
13.1
patch
release
for
the
spring,
that
you
still
need.
D
D
A
Sure,
if
we,
if
we
feel
like
we're
ready
whenever
we
think
we're
ready,
I
don't
know
I
don't
want
to.
I
think
I'd.
B
A
B
A
But
I
think
I
think
we've
got
our
configuration
story
done
then
it's
a
time.
I
think
it's
time
to
cut
the
kind
of
here's
our
release
candidate
for
one
or
1.0.
D
C
And
you're
out,
starting
on
friday,.
D
E
C
Hope
too,
yes,
that's
awesome!
I
I
was
just
lamenting
talking
with
our
family
in
los
angeles
and
wishing
that
we
could
hop
on
a
plane
and
go
down
to
los
angeles
right
now,
because
it
is
cold
and
dark
here.
Yeah.