►
From YouTube: 2022-04-27 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
B
Yes,
it's
easy
evening
for
you:
we
had
a
very
difficult
time
scheduling
this
meeting
because
we
have
people
in
germany,
east
coast,
america,
time,
india,
australia,
so
it's
just
like
this
is
the
best
of
the
worst
times.
I
guess.
B
All
right,
I
guess
I
can
get
rolling.
I
was
expecting
brad
and
timo
to
be
here,
but
maybe
they
forgot
about
the
new
meeting
time,
so
we
can
I'll
follow
up
with
them
later.
I'm
gonna.
Excuse
me,
I'm
also
planning
on
attending
the
1
30
p.m.
Time
to
just
in
case.
Anybody
still
goes
to
the
old
meeting,
so
it
looks
like
sean.
You
have
a
pull
request
open.
That's
great!
I'm
really
excited
to
see
that
one.
B
That's
good,
I
think
you
mentioned
that
I
guess
brett
and
teemo
had
been
reviewing
this
before
so
I'll.
Let
them
review
it.
The
only
thing
I
noticed
is
that
the
the
ci
checks
are
failing.
There's
a
php
unit
test,
that's
failing.
B
A
Yes,
but
I
think
demo
could
have
answered
better,
I'm
not
sure
how
much
you
are
aware,
but
basically
demo
is
dealing
with
this
auto
instrumentation
along
with
symphony,
starting
with
symphony
framework.
I
guess
so.
I
just.
B
A
B
Okay,
yeah:
let's
we'll
follow
up
with
timo
and
channel
after
this
meeting,
and
maybe
we
can
get
some
clarity
from
him.
I
don't
have
a
whole
lot
of
context
on
that
auto
instrumentation,
I
know
he's
been
he
has
in
the
back
of
his
brain,
but
he
also
just
started
a
new
job.
So
that's
also
important
too.
B
A
B
I'm
bob
are
you
coming
to
us
as
a
contributor.
A
B
Welcome
welcome,
is
there,
have
you
had
any
issues
or
blockers
getting
started,
or
is
there
anything
that
we
can
do
to
help
facilitate
your
onboarding.
B
A
A
But
I
am
not
able
to
send
that
so
when
the
application
is
working
fine,
but
I
tried
with
zipkin
and
jaeger,
so
those
are
successful,
but
somehow
I'm
not
able
to
send
otl
pg
at
this
exporter.
B
I'm
I
think
that
that
may
be
related
to
the
changes
that
brett
just
pushed
out.
Coincidentally
enough
yeah
there's
a
pr.
What
pr
is
that
yeah
665.,
and
I
think
that
he
mentioned
in
in
a
message
to
us
that
maybe
I
don't
I
don't
know
if
it
was
in
a
public
channel
or
not
that
that,
like
the
collector,
just
started
silently
dropping
traces
and
then
with
that
fix
it
shouldn't.
So
I'm
hoping
that
fixes
your
issue.
If
not,
then
then
we
can
have
a
chat
about
it
in
the
channel.
B
I'm
just
going
to
merge
this
now
and
then
I
will
cut
a
really
I'm
going
to
cut
a
release
now
ish
too,
and
then
you'll
be
able
to
use
the
new
release
for
that.
B
A
Demo,
yeah,
currently
our
examples.
The
laravel
and
symphony
examples
are
not
up
to
date.
So
would
we
be
changing
that
as
well.
B
I
I
think
so.
I
think
that
the
the
correct
answer
to
that
question
is
it
depends.
I
know
we're
we're
actively
going
to
be
involved
in
the
sig
meeting.
I
think
I
assume
we're
going
to
actively
involved
in
the
sig
meetings
for
that,
and
I
think
that
will
be
separate
from
our
laravel
and
symphony
demos,
because
I
know
that
they
have
like
specific
instrumentation
scope
and
like
problem
statements
that
they
want
to
show
in
the
open,
telemetry
community
demo.
B
B
Yeah,
I'm
planning
I'm
planning
on
attending
that,
so
I
will
I'll
keep
I'll
keep
my
eyes
and
ears
open.
Maybe
we
can
talk
about
that
during
the
next
meeting,
because
that
will
be
after
this.
B
Fun
sounds
good
all
right.
Well,
I
I
will.
I
just
cut
another
release.
Thank
you.
So
you
should
have
that
going
and
then
I
I'll
follow
to
shout
out
follow
up
with
teemo
in
channel,
so
we
can
start
a
thread
about
auto
instrumentation
sure.
Thank
you.
All
right,
y'all
have
a
great
night.