►
From YouTube: Monitor Respond Live Stream Coding 26.10
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
It
says
live
else.
This
is
setting
up
any
meeting.
Maybe
we're
live
now
who
knows
I'm,
sick,
okay,
we're
definitely
like
now.
We
will
also
a
lot
of
people
cool.
So
what
we're
talking
about
is
so
I've
found
a
solution
for
fixing
the
incident
URL
when
we
view
the
incident
as
an
issue.
Let
me
just
show
you
what
I
mean.
A
Okay,
so
this
is
the
problem
we're
going
to
solve
these
failing
tests,
but
what
I
mean
is
you
can
look
at
an
incident
as
an
issue?
A
So
here
is
an
incident
and
you
can
remove
incident
from
the
URL
and
do
it
as
an
issue,
because
all
incidents
are
also
issues
and
then
you
have
issues
and
that
wasn't
working
previously
now
it
is
because
of
this
change.
A
C
A
We
added
the
same
information
on
issue
as
we
had
previously
on
incident.
So
when
we
load
an
issue,
let
this
problem
is.
We
have
a
bunch
of
failing
tests.
A
So
when
issue
is
closed,
it
shows
close
as
an
issue.
It's
been
moved
short
tubes
to
get
it
failed.
A
So
it's
saying
that
there's
no
route
matches
and
Tristan
you
just
said:
maybe
it's
possible
that
the
problem
is
we're
adding
a
slash.
Could
you
tell
me
a
little
bit
more
what
you.
C
D
Yeah,
that
was
my
first
idea.
I
have
another
idea
as
well,
but
it
looks
famous
thing
so
when
we
navigate
to
the
until,
like
an
incident
now
or
an
issue,
what
happens
is
the
when
the
router
loads,
like
the
first
thing
it
does?
D
Is
it
never
gets
you
to
the
base
route
and,
for
some
reason,
I
think
this
might
be
like
a
view,
router
thing
or
maybe
something
we've
done,
but
it
adds
a
slash
on
to
the
end
of
the
issue
so
yeah,
that's
it's
just
slightly
odd
behavior
that
has
come
about
from
our
changes.
D
I
think
it's
because
the
way
we've
defined
the
routes
is
the
the
initial
route
is
like
quote,
slash,
quote
and
so
view.
Router
wants
to
kind
of
match
that
so
it
adds
the
slash
when
we
first
load
the
page.
D
Okay,
I
can't
share
my
screen
right
now,
unfortunately,
but
what
I
was
going
to
look
at
was
issues
that
RB
file.
Perhaps
you
could
bring
that
up.
Champs.
A
So
I
keep
talking
not
being
on
vs
code
or
Pro.
D
Chrome
yeah
just
send
it
if
yeah
yeah,
so
you
see
where
so
go
up
there
in
the
top
right
yeah,
so
you've
defined
four
new
routes
there
and
in
frails,
when
you
define
it
a
path,
slash
route,
slash
URL,
you
give
it
a
name
so
or
it
gets
automatically
assigned
a
name
by
the
Autumn
automatic
magic
that
happens
in
rails.
So
you've
got
you
have
to
find
some
names
there,
so
it's
going
to
use
those
and
the
name
for
it.
Yeah.
D
This
you
show
is
issues
underscore
summary,
so
I
think
what
what
is
now
happening
is
the
rails.
Specs
they're
like
feature
specs
for
that
for
issues
are
referring
to
and
names
path,
and
since
we've
gone
to
find
that
path
now
like
the
path
for
that
particular
URL,
like
maybe
the
name,
doesn't
exist
anymore.
D
So
it's
saying
no
route
matches
action,
show
controller
project
issues
and
I.
Think
that
would
have
like
automatically
made
a
route
called
project
issues
show
or
possibly
just
issues
show
and
I
I
suspect.
If
we
look
at
the
the
actual
test,
like
we
go
and
find
the
file
we'll
find
that
that
is
referring
to
the
name:
drought
there,
because
of
what
we've
done,
we've
done,
it
no
longer
exists
yeah,
so
that
that's
my
thinking,
my
current
thinking
for
why
this
is
failing.
D
And
while
you
look
at
that
I'm
quickly,
going
to
restart
my
zoom
so
that
I
have
permission
to
to
share
screen
in
the
future.
Okay.
A
Okay,
well,
this
makes
sense.
This
is
probably
the
name
project
you
should
show.
C
C
A
Yeah
I
just
thought,
maybe
because
I
don't
know
how
this
works.
A
A
And
then
hash
and
the
line
number
and
we're
gonna
run
that
test
only.
C
C
C
A
I
need
some
more
back-end
guest
speakers
are
now
yeah.
A
Where's
just
Live
code
streaming.
A
A
Yeah
there's
been
a
few
other
teams
that
have
been
involved
in
live
coding
and
so
hopefully,
we'll
get
a
bit
of
put
together
a
lot
of
content
for
Live
code
and
Airship
at
all.
A
Still
running
it's
the
slower
aspect,
one
right
so
I
wonder
if
we
can
test
your
theory
by
just
like
getting
rid
of
the
slash
or
do
you
think
it's
going
to
add
it
always
anyway.
D
A
A
A
Cool
okay!
Well,
so,
if
we
get
rid
of
this
line
entirely,
I'll
show
you
what
happens.
A
A
B
D
Think
I
think
what
what's
happening
there
is
there's
a
weird
base.
Url,
that's
being
sent
remember
how
there's
that
whole
thing
of
like
the
URL
like
rails
sends
a
URL
to
the
front
end
so
that
we
can
load
it
as
config
into
the
router.
D
A
It
feels
like
listen,
it
feels
like
this
is
something's
wrong,
but
seems
to
be
okay.
Maybe.
B
A
Yeah
so
otherwise,
I
started
working
on
splitting
out
the
differences,
so
I
have
the
reformatting
of
the
incident
tabs.
Just
as.
D
C
D
C
A
D
C
A
All
right
cool
we're
getting
a
fail,
but
what
I
wanted
to
know
is
sometimes
it
gives
us
a
screenshot
of
what
it's
doing.
It's
not
giving
us
that,
because
it's
not
actually
using
a
browser.
It's
just
checking
to
see
if
those
routes
exist,
I
think.
D
Oh
now,
I'm
just
thinking
yeah,
so
the
lightness
is
failing
on.
Is
there
as
in
side
issue
with
balls,
helper,
okay,
we're
saying.
B
D
.,
it
would
certainly
be
a
lot
faster,
a
lot
faster
yeah
because
I
bit
I
bit.
Someone
just
knows
the
answer.
Yeah.
A
D
Yeah
sounds
good
one.
B
D
Was
gonna
say
before
before
we
one
thing
I
was
just
going
to
say
before
you
and
is
there
there
are
other
ways
to
write
the
that
issues:
dot
RB
file,
okay,
we've
sort
of
done
it
like
the
the
really
like
Brute
Force
way,
which
is
like
Define.
Each
thing
is
a
separate
line,
but
you
can
also
yeah.
You
can
also
like
do
things
like
you
can
create
this
like
member
object.
D
No,
not
quite
I,
think
we
do
it
in
the
main,
in
the
main
routes
file
a
bit
more
often
but
yeah,
there's
it
rails
has
a
lot
of
flexibility
about
how
you
can
Define,
URLs
and
I.
Think
yeah
I
think
someone
with
back-end
knowledge
of
that,
like
peda
who's
helped
us
out
on
us
in
the
past.
D
We're
just
kind
of
know:
instantly
wants
to
do,
but
yeah
so
for
for
us
to
do
it
I
think
we
need
to
do
a
bit
of
Investigation
a
bit
of
reading
of
the
Rails
docs
and
stuff
yeah
yeah
I
think
it
was
really
good
stuff
to
learn
because,
like
as
a
friend-hand
engineer,
you
kind
of
do.
D
You
should
probably
know
some
stuff
about
like
at
least
the
back
end
parts
that
we
interact
with
the
most,
which
is
like
routes
Hamill
stuff.
So
anything
that
can
go
inside
a
hammer
file
as
to
create
templates
and
also
like
the
helpers
that
we
use
to
send
data
attributes
to
the
front
end
and
also
controllers,
which
is
where
we
like
flip
on
feature
flags
and
stuff.
So.
C
D
There's
a
lot
of
a
lot
of
rails.
That
is
really
useful
to
know
as
a
front-end
engineer,
so
yeah
something
that
I'd
like
to
learn
more
about,
but
definitely
do
that
outside
the
stream
cool.
B
B
A
Of
that
and
see
you
next
week,
I'm
in
the
Stream.