►
From YouTube: 2022-05-12 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
I
guess
I
need
to
do
a
better
job
of
maybe
announcing
it
in
the
elixir
channel
earlier,
because
I
mean
people
have
a
number
of
questions,
but
they
tend
to
just
ask
them
in
there
and
not
join
this.
Maybe
they
would,
they
might
not
know
or
not
know
in
time,
use
this
more
as
a
office
hours
recently
yeah.
C
C
C
C
C
Basically,
everything
ended
up
with,
like
whatever
the
original
operation
was
and
then
like
with
context
with
link
spam
and
with
spam,
so
it'd
be
like
async
with
spam
whatever
and
then
the
first
two
arguments
are
just
like.
C
B
Docs
that'll,
be
some
it'd,
be
good
to
link
to
that
application
and
it's
docks
from
the
main
docks
the
main
open,
telemetry
apis
like
guides.
I
guess
we
should
add
what
is
what
I
guess.
Hex
has
a
hex
box.
That's
a
special
thing
for
guides.
I
don't
want
the.
B
Yeah
yeah
yeah,
the
gustavo
mentioned
that
we
should
have
guides
I've
forgotten
all
about
that
and
but
yeah
we
have
guides
for
stuff
and
then
link
out
to
that,
because
we
wouldn't
want
to
dock
it
in
the
name
api
since
it's
a
separate
extension
but
the
yeah.
That's
where
people
are
gonna,
look
and
yeah.
A
lot
of
this
stuff
keeps
coming
up
yeah
and
I
should
have
a
pull
request
for
the
logging
metadata
today
be
cool
yeah.
The
main
thing
is
helpful,
just
not
sure
the.
B
B
C
B
No,
I
don't
think
so,
but
they're
saving
it
to
the
languages
yeah
it's
up
to
whatever's
the
languages
preferred
or
whatever
the
okay
it
just
said.
If
it's
implicit,
then
it
should
be
available
or
something
which
I
guess
yeah
that
actually
answers
the
question
of
whether
it
should
be
configurable,
because
it's
in
the
spec,
I
guess
just
following
this
bag,
easy
enough.
C
C
C
The
no
the
ecto
one
it
has
one
argument
and
it's
just
the
repo
prefix
right,
okay
yeah,
but
you
can't
say
like
add
this
as
a
filter
or
whatever
yeah.
I
thought
you
said
plug,
not
yeah.
Sorry,
I
think
phoenix
is
making
an
assumption
and
you
can
optionally
pass
that
I'll.
Just
need
to
check
that
by
the
way
filters
are
next.
B
A
C
B
You'll
just
say:
use
the
nun
sample
or
whatever.
It's
called
the
no
sample
and
drop
everything
for
instead
of
having
to
manually,
check
and
drop
or.
B
Yeah
and
but
if
we
have
a
like
tracer
per
endpoint
or
whatever,
then
it
can
be
configured
to
like
it,
it
can
just
be
used
by
the
open,
telemetry
plug
up
telemetry
phoenix
to
implement
this
feature
versus
users
would
be
able
to,
but
they
wouldn't
have
to
like
mess
with
it
themselves.
It's
just
a
oh.
We
would
just
like
set
the
sampler
for
the.
C
A
B
Okay,
because
now
because
yeah
we
have
tracers
per
scope
and
scope
can
be
anything
not
just
the
instrumentation
library,
so
we're
not
so
we
could
have
a
scope
per
plug
endpoint
or
whatever
they're
called.
Oh.
C
C
Calling
spandex
they
were,
he
was
just
like
expand
explaining
like
all
of
it.
It
wasn't
like,
as
I
don't
know
if
you
saw
greg's
talk
that
went
up,
but
he
did
a
great
job
of
like
explaining
everything
so.
C
C
C
C
C
Just
using
that
socket,
I
think
that's
the
spot
that
they're
really
doing
it.
C
I
don't
know
if
you
even
see
that,
because
I
think
it
upgrades
in
cowboy
right
yeah,
I
think
you'd
see
the
requests
for
the
upgrade,
it
would
return
100
and
then
it
would
then
just
hit
that
socket
handler.
B
Fun
interesting
to
figure
out
how
to
get
at
it
is
I
mean
the
javascript
should
be
making
spans
too.
So
you'd
want
to
be
sending
the
you
wouldn't,
except
it
doesn't.
C
B
C
I
think
the
javascript
has
to
be
essentially
hacked
to
always
generate
a
trace
on
each
message
being
sent
to
the
server
and
I'm
not
sure
exactly
I'm
sure,
there's
a
way
to
monkey
patch
it
and
make
it
work,
because
the
phoenix
client
has
a
fair
amount
of
hooks
available.
I
think
where
you
can
just
write
custom
javascript
code,
oh
okay,
but
then
you
would
need
to
also
include
the.
C
C
C
Every
one
of
them
be
named
the
same,
and
then
in
your
handler
and
the
live
view
you
would
need
to
put
yours
put
another
span
in
there
and
name
it.
How
you
really
want
it
all
right,
yeah,
but
you
wouldn't
be
able
to
set
attributes.
It's
really
the
you
wouldn't
have
attributes
on
the
spam,
that's
in
the
client
yeah.
This
is
why
I
never
touched
it
because
this
giant
bag
of.
C
C
A
A
B
There
was
the
setting
status
doing
that
one
yeah
okay,
I
got
resolved.
C
C
It's
only
elixir
but
a
different
back
end
for
phoenix.
C
So
I
know
some
people
were
trying
to
like
plug
ellie
for
a
while.
I
don't
think
it
ever
got
finished,
but
you
know
somebody
built
like
an
entire
new
plug
like
it's
a
purely
elixir
plug
implementation,
whatever
yeah
they
did
it
in
an
elixir
yeah,
but
it
might
be
able
to
like
have
a
lot
better
tracing
facilities
since
yeah
cowboy.
C
B
I
saw
this
yeah
so
we'll
see
yeah,
it's
not
really
5x,
but
even
if
it's
one
x
and
it
works
better
than
right.
Well
I
mean
people
might
well
might
yeah.
I
mean
if
it
just
gets
rid
of
like
how
there's
a
recording
but.
B
B
If
it's
going
to
go
anywhere,
it's
going
to
it's
got
a
long
ways
to
go,
but
because
it
just
uses
http
decode
from
erlang,
like
ellie,
does,
while
cowboy
has
it
all
written
in
erlang
to
decode
http,
and
that
can
scale
better.
It's
slower
a
little,
but
it
scales
better.
I
don't
know
if
it's
still
how
slow
it
is
compared
now
that
we
have
a
jit
but
yeah.
Okay,
well,
we'll
see
yeah.
If
it
was
in
early,
I
could
push
for
people
to
help
out
and
I'd
kill,
ellie
and
I
killed
chatterbox
and
I'd.