►
From YouTube: 2020-07-31 Java SIG
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
B
A
A
C
A
B
B
Yeah
you've
been
you've
been
all
all
across
instrumentation
sdk
specs.
C
B
Yeah
I
like
I,
like
your
comment
on
the
spec
about
the
only
way
to
move
things
forwards
is
to
join
the
spec.
C
Yeah,
I
mean
that's,
definitely
our
impression.
I'm
a
bit
surprised
carlos
didn't
have
that
impression,
but
yeah
like
I
don't.
I
guess
that
piero
is
about
to
spec
and
I'm
seeing
it
even
more
of
an
issue
in
the
other
sigs,
actually
that
to
get
language
changes
in,
we
always
just
have
to
bring
it
up
with
the
sig,
otherwise
it
just
doesn't
get
merged.
That's
been
our
experience.
C
B
Oh
okay,
good
good
yeah.
I
think,
there's
also
been
like
you
and
nikita
called
out
everybody
pretty
strongly
on
the
the
maintainers
meeting.
B
B
Yeah
we
had
a
good
meeting
today
we
chatted
so
john
is
back
as
you
know,
so
we
chatted
about
the
reposco
repository
scope,
question
and
one
thing
that
nikita
brought
up
that
seemed
to
so
like
I
was
thinking
of
like
something
like
if
it's
library
specific,
maybe
it
you
know,
could
be
a
divider
of
whether
it
goes
in
the
instrumentation
repo
or
the
sdk
repo
nikita
brought
up
kind
of
the
artifact
name
of
like
you
know.
B
Do
we
like
do
we
feel
like
something
belongs
under
you
know,
instrumentation
artifact
or
not
spring.
Boot
starters,
I
kind
of
was
initially
was
thinking
here,
but
then
afterwards
had
a.
Why
was
it
not
like?
After
though
it's
one
word?
Okay,
I
thought
that
realized
that
some
of
our
spring
boot
starters
some
are
just
doing
the
exporters,
but
some
are
also
doing
the
rest
template
stuff.
C
C
B
Yeah,
so
cool,
so
we're
gonna
bring
that
up
tomorrow.
I'm
gonna
join
the
the
sdk
meeting
tomorrow.
I
told
that
john.
If
the
I
know
it
doesn't
help
you.
I
don't
know.
If
eight
you
said
eight
is
like.
I
mean
well
that's
midnight
for
you.
So
that's
not.
C
B
Oh
yeah,
even
worse,
yeah,
so
yeah,
so
we
were
actually.
I
was
asked
if
you
know
I
mentioned
that
if
if
it
was
not
it
quite
so
early,
I
would
I
could
join
more,
but
I'm
not
gonna
push
on
that.
It's
a
good!
That's!
Actually,
bad
though
it
is
bad
even
for
like
carlos
europe.
It's
the
friday
morning
is
bad
for
europe,
because
it's
friday
evening
I
mean
friday.
D
C
B
A
B
C
Things
I
mean
shims
seem
complex
enough.
They
could
possibly
each
have
their
own
repo,
but
like
right
now
there
is
some
open
tracing
shim
right
yeah.
It
looks
like
I
haven't,
looked
at
it
before.
B
Me
neither
I
need
to,
though,
because
frank
reported,
a
bug
with
the
auto
instrumentation
that
he
was
able
to
reproduce
using
the
open
tracing
shim.
So
there's
something
in
our
bridge.
That's
not
there's
a
bug
somewhere
in
our
bridge.
C
B
Cool
nikita
is
very
concerned
about
ga
about
our
93
required
issues.
B
Yeah
yeah,
I
think
that
is
his
concern,
which
I
encounter
with
you
know,
and
that's
kind
of
why
I
started
tackling
some.
You
know
some
easy
p1
stuff
today.
Just
because,
like
you
know,
they're
we
we
need.
I
really
really
appreciate
the
new
like
new
perspective,
new,
like
thoughts,
new
ideas
on
this
and
those
things
take
time
and
so
and
those
things
are
super
important.
So
you
know
I
can
I
can
do
you
know
the
you
know
few,
some,
a
bunch
of
these
p1
things
and.
B
But
yeah
anyway,
so
yeah.
C
B
So
just
start
tracking.
You
know
weekly
our
p1
issues
because
that's
more
manageable
and
and
honestly
that's
what
we
have
to
have
as
far
as
being
you
know,
worried
about
hitting
ga
and
then
yeah.
So
I
feel
I'm
not
really
that
scared
by
this
list
and
potentially
we
could
bump
priority
down
a
bit
yeah.
So
basically,
all
I
wanted
to
say
was
keep
doing
what
you're
doing.
B
Need
those
new,
we
need
new
ideas
and
new
yeah.
B
For
zero,
seven
should
I'll
find
out
tomorrow,
john
wasn't
sure,
since
he
was
just
back
from
vacation
but
assume
that
zero
seven
sdk
is
going
out
on
monday.
That's
typically,
the
first
monday
of
the
month
is
their
plan,
and
the
only
issue
that
I
flagged
sort
of
that
I
would
like
to
get
in
and
malifi
or
sergey
said
that
he
could
do.
That
is
that
multi-propagator
support
just
because
a
few
people
have
brought
that
up.
Lately.
C
C
C
B
B
Yeah
right
right
yeah,
so
this
one
got
requested
and
anyway
then
closed
and
like
no.
We
need.
We
really
need
this.
So
oh
yeah,
you
probably
other
people
want
that
everybody
wants
so.
C
C
B
The
meeting,
because
I
think
partly
we
had
maybe
delayed
that
thinking-
that
we
would
resolve
that
as
part
of
the
context
stuff
but
john
mentioned
on
the
call
today
that
you
know,
maybe
we
can
just
build
an
api
for
that
outside
of
that's.
I
mean
independent
of
waiting
for
that,
since
that's
blocking
stuff.
C
B
C
C
B
D
B
B
Weird,
if,
if
we
don't
remove
the
grpc
context,
dependency-
and
somebody
else
is
using
this
on
there.
B
B
Nikita
has
concerns
about
the
concurrent
instrumentation.
I
think
this
is
related
to
the
sporadic
some
of
the
sporadic
failures
that
he
was
chasing,
so
we
didn't
have
time.
So
I
suggested
sounded
like
a
special
topic
meeting.
C
B
C
C
B
Yeah
yeah,
it
would
be
interesting
if
they
do
something
beside
like
so
the
the
normal
apm
approach
is
instrument
executor.
C
C
C
A
C
Yeah,
just
for
use
like
I
propagate
context,
anyways,
so
I
would
be
worried
actually
if
this
causes
problems
with
my
own
propagation.
So
as
long
as
it's
like
it's
java
concurrent,
it
seems
like
some
basic
library,
but
if
it's
still
okay
to
disable
it
at
least
that's
something,
then
users
can
always
switch
to
manual
propagation.
B
Yeah
yeah:
that's
actually
a
good
thing
that
we
should
dock
when
we
start
documenting
sort
of
the.
C
B
B
Right,
yes,
yeah,
when,
if
we
want
to
go
down
that
path,
one
thing
to
that
we
would
want
to
think
about
is
in
some
of
the
like
async
web
framework
stuff.
We
rely
on
that
java,
concurrent
instrumentation.
B
We
could
potentially
not
rely
on
it
and
propagate.
You
know,
based
on
the
framework
itself,.
C
C
B
Yeah
run
so
I
know
that.
C
B
Run
all
the
tests
currently
with
we
do
use
the
both
the
class
loader
and
the
java
concurrent
instrumentation
yeah
across.
We
force
that
into
all
the
tests,
mostly
just
to
make
sure
that
we
don't
break
those,
but
yeah
I
mean
we
could
definitely
pull
them
out
and
see
what
breaks
see.
What
see
what
kind
of
work
effort
is
required
after
ga.
A
B
And
then
I
I
started
this
kind
of
this
idea.
The
last
week
when
we
started
having
some
short
meetings
of
on
kind
of
doing
the
weekly
digest
for
people,
and
I
thought
it
was
cool.
It's
actually
well.
A
lot
happened
in
the
last
week
and
also
across
a
lot
of
a
lot
of
contributors,
because
we
had
the
database
the
types
fans
from
this,
that
the
semantic
attributes
from
helen,
more
semantic
attributes
from
frank.
B
So
yeah
I
mean
you
know
everything
that
happens
so
yeah
the
I
did.
B
Steve
flanders,
from
splunk,
who
is
an
approver
on
the
collector
and
he's
also
nikita's
boss,
and
we
recorded
kubecon
eu
talk
about
the
collector.
So
he
talked
about
the
collector.
I
talked
about
the
java,
auto
instrumentation
and
then
he
had
that
has
a
cool,
a
nice
demo
set
up
with
that,
just
showing
how
it
just
all
works,
and
so
that
would
be
cool.
Maybe.
B
He
was
exporting
to
well,
he
was
going
to
the
the
collector
and
then
splunk
to
no
no,
he
used
jaeger.
I.
A
B
Yeah,
so
the
things
that
are
not
going
well
yeah.
I
think
I
may
dig
into
that
kind
of
I
wanted
to
check
with
nikita
first
if
he
was
cool
with
me,
picking
up
where
he
had
sort
of
had
some
good
findings
towards
what
might
be
happening
and.
D
B
C
C
B
B
Wasn't
clear
to
me
what
to
do
there,
so
I
mean
you've
got
we've
got
the
status.
I
could
make
status
the
response.
B
So
there
was
our
http
response,
so
this
is
what
I've
tried.
Yeah
hold
on
the
response.
Let's
see,
can
we
get
the
status
question.
B
Or
even
the
request
log
for
the
the
response.
C
B
All
right,
awesome
answers
my
question.
A
B
Let
me
share
back.
My
steve
was
showing
me
because
he
had
a
slide
about
the
cncf
dev
stats.
Have
you
seen
those.
A
B
D
B
Yeah
so
yeah
I
was,
I
was
looking
at
the
somebody
else
had
sent
around
internally
a
chart,
and
this
is
so.
I
did
the
same
for
the
open,
telemetry
java
instrumentation,
and
so
I
wanted
to
point
this
out
to
you
that
I
think
your
contributions
are
being
counted
towards
infostellar.
B
Okay,
yeah,
it
was
pretty
obvious
that
that
was
you
also.
I
think
this
is
a
great
picture
of
a
growing
healthy
community,
like
oh,
like.
B
This
with
this
is
not
healthy,
yeah
and
yeah.
C
B
The
net,
so
I
just
changed.
B
So
yeah
like,
if
you
look
at
the.net,
unsurprisingly,
not
as
healthy
on
microsoft,.
B
I
thought
that
this
was
for
calculating
contributions
based
on
developers
and
their
companies.
Companies
no
other,
can
check
if
they're
correctly.
D
A
C
A
C
C
Oh,
you
were
looking
at
google.
I
just
found
this
dashboard,
which
is
all
of
open,
telemetry
and
infosteller's
house.
B
D
B
C
C
B
B
C
B
Yeah
yeah
we're
we're
good.
I
mean,
we've
got
the
oh
yeah,
the
actually
the
I
mean
the.
If
you
look
at
across
the
open
telemetry.
So
if
you
go.
B
And
open
telemetry,
so
open
telemetry
was
the
second
largest
at
most
active.
If
you
look
at
in
open
telemetry
the
java
instrumentation
project.
C
B
The
second
most
active
after
the
collector,
so
we've
got
we've
got
activity,
we've
got
people
so
yeah.
I
think
we're
I
I
really
want.
I
really
want
it
to
be
a
nicer
place
to
live.
Oh.