►
From YouTube: 2022-01-04 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
You
for
having
me
here
not
much
just
trying
to
remember
how
to
write
software
had
that
off
for
the
past
like
week
or
two.
So,
let's
get
back
into
it.
A
A
People
are
work
back
to
work
now,
hopefully
we'll
see.
I
know
a
couple
folks
are
actually
out
all
the
maintainers
are
still
out
for
this
sig
and
yeah
so,
but
I
think
a
few
more
folks
will
probably
join.
How
are
you
all
doing.
A
Sorry
about
that
yeah
I
should
have
mentioned
so
shopify
gave
like
me,
robert
and
francis.
We
all
worked
together.
We
they
gave
the
whole
company
like
the
week
off,
and
I
forgot
to
probably
mention
it
to
other
folks
and
yeah
most
people
in
america.
Most
people
take
off
a
lot
of
time
between,
like
christmas
and
new
year's,
it's
kind
of
like
everyone
sort
of
like
closes
the
computer,
but
yeah
hope
you
guys
are
doing
well
and
2022
is
good.
Shana
tova.
Does
that
work
for
the
regular
new
year?
B
A
C
A
Yeah,
I
know
you
guys
have
there's
still
some
the
work
that
you've
done
so
as
to
get
merged,
so
I'm
trying
to.
Unfortunately
you
need
two
people
to
merge
it.
So
I'm
just
trying
to
wait
for
someone
else
from
this
good
for
my
company
or
someone.
D
No
problem,
it's
not
blocking
us
or
something
like
that.
A
Okay,
yeah
it'd
still
be
good
to
get
in
just
so
that
you
guys
aren't
sending
folks.
You
know
like
a
custom,
instrumentation
thing
and
then
trying
to
migrate
them
to
a
upstream
one
later
or
whatever.
I'm
sure
is
a
hassle.
So
but
anyway,.
A
D
A
A
A
A
So
yeah
I
don't
have,
I
know
matt
usually
does
this
quick
run
through
of
the
specification
meeting,
so
I'm
happy
to
do
that
and
then
we
can
get
it.
I
know
a
couple
folks
here
have
some
pr's
open
or
whatever,
so
we
can
just
open
the
floor
to
anything
but
yeah
does
anyone,
I
guess,
have
anything
urgent
to
start
with
or
not
urgent,
but
just
anything
they
wanted
to
discuss
before
you
get
into
the
the
part
where
I
talk
a
lot
for
no
reason.
A
Oh
okay,
we're
all
just
kind
of
we're
all
just
hanging
out
cool
all
right.
Well
I'll
share
my
screen.
Let's
see
if
I
can
do
this
in
a
way
that
doesn't
just
share
my
desktop.
A
You
can
all
see
that,
yes,
cool
all
right
feel
free
to
fill
in
your
names,
just
you
so
choose
anyway,
so
for
the
spec
sig.
It
was
this
morning
pretty
light
attendance
and
nothing
happened,
cool.
So
that's
cool.
I
guess,
looks
like
they're
reviewing
some
metric
stuff
last
week,
pretty
light
as
well.
So
I
yeah-
I
don't
well
anyway,
and
that
concludes
the
specialization.
A
Sig
recap:
I
guess,
let's
pop
open
the
repo.
As
far
as
like,
where
we
stand.
Oh
looks
like
someone
made
well
so
like
sort
of
the
open
pr's
here
that
are
actively
being
worked
on.
I
know,
yaniv
your
sqs
context,
propagation
thing
looked,
I
had
approved
it.
I
think
we're
still
waiting
on
one
more
approver
or
I
don't
even
know
for
I
think
matt
actually
proved.
I
think
we're
just
waiting
on
it
to
merge
and
release.
A
If
I
remember
correctly
so,
unfortunately,
people
who
have
those
merger
rights
are
frances,
robert
and
matt,
none
of
whom
are
here.
So
I
can
try
to
ping
matt
or
robert
or
something
to
get
a
merge,
but
it
might
take
a
couple
days
or
a
week
or
so.
I'm
also
out
friday.
We
can
wait
for
next
week.
No
problem
cool.
A
I
will
wait
for
next
week,
I'll
make
sure
to
nudge
robert
when
he
gets
back,
though,
and
try
to
have
him
prioritize
merging
just
because
it's
been
sitting
for
a
while
sense
that
there's
some
other
pr's
here
that
are
a
little
stale
and
not
super
worth
getting
into,
but
mostly
don't
have
a
ton
to
talk
about.
I
think
the
other
one
to
talk
about
is
the
rails.
Is
tim,
you
have
a
rail
7,
the
rail
seven
active
record
pr.
D
A
Okay,
so
I'll
re-review
I
mean
I
looked
last
time.
I
think
it
was
fine
I'll
just
give
it
another
approval.
I
can
try
to
unblock
ci
generally
the
issue
here.
I
think
we've
talked
about
this
a
number
of
weeks.
It's
just
we're
pulling
in
our
ci
runs,
are
mostly
pulling
in
late,
almost
like
acting
unofficially
in
a
canary
capacity.
A
So
it's
nice
in
the
fact
that
we
learn
pretty
quickly,
whether
minor,
even
patch
or
minor,
releases
break
stuff,
but
bad
in
the
sense
that
we
should
probably
not
have
ci
be
broken
really
ever,
but
you
know
we
should
be
getting
alerted
to
this
and
something
that's
you
know
we
should
be
restricting
our
version
to
something
reasonable
and
then
being
able
to
with
more
confidence
say
that
we
support
some
minor
release,
but
I
don't
know
that's
also
maybe
a
little
restrictive,
but
okay
anyway,
I
will
try
to
see
if
I
can
clean
up
and
see
I
quickly.
A
Usually
this
stuff
is
like
minor
issues
and
when
we
merge
this
pr
that
will
make
all
of
our
instrumentation
compatible
with
rail
7.
As
far
as
I'm
aware,
which
is
a
good
sign,
we
yeah
we're
not
maybe
we're
running
so
for
the
other
rail
7
updates
for
context
and
even
amir,
if
you
guys
are
speaking
with
users
or
anything,
we've
sort
of
we
added
appraisals
for
in
the
test,
suite
for
all
the
rail
7
components.
So
that's
rails,
that's
active
support
action,
view,
active
view,
action
view,
you
think.
A
Oh
no
action
pack,
I
just
had
our
test
suites
run
against
with
rail
seven
installed
and
everything
passed
and
then
reviewing.
I
did
a
quick
just
like
you
know,
time
box
review
of
if
there
were
any
significant
changes
in
the
method,
signatures
for
those
like
rails
integrations
and
they
all
look
good
and
pretty
much
mine.
A
You
know
nothing
too
significant
active
records,
the
exception,
which
added
a
bunch
of
funkiness
to
its
method,
signatures
which
tim's
pr
will
unblock,
basically
by
allowing
us
to
just
naively
pass
through
all
the
arguments
without
having
to
rewrite
that.
You
know
without
having
to
like
explicitly
name
them,
which
is
much
more
flexible,
but
because
of
the
because
ruby
is
weird
and
braille's
is
weird
about
the
way
you
do
that,
there's
some
extra
work
required,
which
is
what
this
pr
does
anyway.
Sorry!
So,
okay!
So
that's
good!
A
Besides
that,
I
guess
we
have
to
release
the
gem
for
github
open
source,
their
mysql2
client,
and
it's
called
something
cool
I
forget
trilogy,
which
is
essentially
just
a
new
ruby
library
for
managed,
for
you
know
making
my
sql
queries,
so
they
added
instrumentation.
For
that
we
need
to
release
it,
and
then
I
guess
this
is
a
new
pr,
which
is
that
debugging,
I
guess
someone
there's
a
user
trying
to
use
whoa
special
forces
engineer.
A
That's
so
cool!
Sorry!
I
wonder
if
that's
sarcastic,
my
wife's
looking
at
me
like
I'm
a
video
is
anyway
he
added
some
debug
info
I'll
review
this.
I
guess
I
think
in
general
it's
a
little
weird
actually
there's
been,
I
think,
from
this
user
rob
from
honeycomb
a
week
or
two
ago
and
have
sort
of
mentioned
that
our
when
our
exporters
fail
they
kind
of
fail
silently
they're,
not
you
know
they
throw
like
an
error
message,
but
it's
not
super
useful
and
people.
A
The
only
way
to
sort
of
know
what's
going
on
is
you
have
to
also
add
like
in
the
otlp
exporter.
There's
like
a
metrics
package.
You
can
add.
You
know
like
a
little
hooks
where,
if
you
add
a
metrics
reporter,
you
could
see
you
know
statsd
gauge
metrics
for
like
oh,
it's
a
you
know
a
time
out
issue
or
it's
a
you
know,
service
unavailable
issue,
but
yeah.
A
I
think
there's
a
little
bit
of
a
need
to
maybe
standardize
and
improve
that
and
make
it
a
little
more
accessible
so
that
you're
not
having
to
add
an
entire
metrics
suite
just
to
read
your
debug
logs
more
clearly
so
anyway.
I
think
that's
on
the
top
of
mind
for
folks,
but
in
the
meantime,
stuff
like
this
is
probably
pretty
unobtrusive
and
frankly,
like
not
many
people
are
using
the
zipkin.
A
I
guess
some
people
are
using
it
because
that's
how
you
export
to
some
services,
but
so
that,
anyway,
that's
a
small
pr
outside
of
that,
I
don't
think
there's
really
anything
going
on
in
this
will
be
addressed
by
tim's
work.
Some
of
these
are
just
like
add
some
better.
You
know
debug
logs
and
yeah
anyway.
This
is
what
we
were
discussing
earlier,
which
is
like
builds,
are
failing
too
frequently.
A
Let's
maybe
like
be
a
little
more
restrictive
with
their
versioning
and
then
add
a
something
to
our
github
ci
build
so
that
it
just
runs
like
a
canary
overnight
cool
anyway,
I
don't
have
any.
I
think
that
kind
of
summarizes
where
things
are
at
anyone
anything
they
want
to
discuss
or
talk
about
or.
A
B
I've
seen
many
gems
that
you
are
those
they
live
and
there's
the
hierarchy
of
the
folders
underneath
it
and
in
many
places,
there's
like
empty
files
that
just
declare
module
module
and
do
nothing.
What's
the
motivation
for
this,
if
you
open,
for
example,
instrumentation
and
then
pick
a
random
instrumentation,
I
don't
know
and
then
leave
and
then
open
telemetry.
A
I
think
that's
generally,
like
I
mean
I
think
the
short
answer
is
like
because
that's
the
way
ruby
repositories
are
kind
of
structured
where
you
declare
the
module
and
then
you
pull
in
like
the
yeah
the
instrument,
then
you
pull
in
all
like
the
details
of
the
instrumentation
in
practice
like
it's
not
super,
let's
see
like.
B
A
A
C
Then
here
you
see
that
there's
no
like
we
don't
redeclare
that
module
or
whatever.
A
I
am
not.
You
would
think
I
would
be
better
at
ruby,
because
I
write
in
ruby
and
I
work
at
a
company
that
does
ruby
but
yeah.
I
actually
have
no
idea,
except
that
I've
just
seen
that
pattern.
A
lot,
I
think,
maybe
okay,
maybe
what's
next,
what's
required
here-
is
that
technically
these?
A
D
I
don't
know
which
may
be
right
that
it
has
to
do
with
auto
loading,
maybe
I'm
not
too
sure
like
the
zeitgeist
stuff,
but
but
I
might
be
completely
off
on
that.
A
No,
that
sounds
right.
I
mean
I
think.
A
Like
this
looks
reasonable
to
me,
I,
like,
I,
don't
think,
there's
I
don't
think
it's
a
mistake.
If
anything,
I
would
say
like
the
ones
that
don't
do
that
maybe
are
a
little
goofy
to
me.
This
was
bass.
This
is
quite.
A
Well,
I'm
not
sure,
let's
see
like.
A
Yeah,
I'm
not.
I
don't
know
why
that,
like,
I
I've
seen
that
pattern
a
lot
in
ruby.
That's
just
like
the
way
things
are
structured.
I'm
not
sure
why.
A
Some
library,
some
gems,
are
doing
it
and
others
aren't.
To
be
honest,
I
don't
know
if
there'd
really
be
any
issue,
if
you
chose
not
to
have
that.
B
A
It
might
be
because,
like
maybe
these
gems
are
technically,
you
can
use
them
outside
of
a
like.
You
could
install
them
wherever.
So
we
need
to
ensure
that
this
is
declared
like
this
module
exists,
if
you're
just
installing
this
instrumentation-
and
I
don't
know
some
some
random
library-
that's
not
like
the
sdk
or
api.
A
A
You
know
like
people
copy
and
pasted
over
some
instrumentation
at
one
point
from
like
datadog,
and
then
people
added
some
others,
and
then
they
changed
the
structure
of
the
repository.
So
it's
possible
some
of
the
stuff
just
kind
of
got
left
in
like
accidentally
or,
like
you
know,
there's
not
like
a
cohesive
vision
around
like
the
right
way
to
do
some
of
this
autoloading
stuff,
but
yeah,
I'm
kind
of
just
making
stuff
up.
So
I
don't
know
I'll.
A
Ask
francis,
you
would
know
cool,
okay,
cool,
that's
a
good
question,
any
anything
else
on
people's
minds.
A
I
will
try
to
update
in
the
chat
or
I'll
pick
you
guys
if
I
can
get
a
review
on
the
aws
stuff
and
yeah
tim
I'll
ping,
you
on
the
rails
thing
or
the
koala
if
we're
stuck,
but
it
should
be
minor
all
right.
Well,
everyone
have
a
a
happy
new
year
or
whatever
or
don't
I
don't
care
and
yeah
I'll
see
y'all
next
week,
it's
good,
seeing
you
all
hope
everybody's
doing
well
all
that
good
stuff.