►
From YouTube: Monitor Respond LIve Coding 12.12.22
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
It's
all
good
yeah,
so
I
guess
to
start
with
introductions.
I'm
Tristan
I'm
working
on
the
monitor,
responding
as
a
front-end
engineer
and
yeah
currently
located
in
New
Zealand.
A
Yep
cool
James
also
on
the
monitor
response,
team
and
front
end
I'm,
normally
based
in
Berlin
but
I'm,
visiting
home
in
Australia,
so
I'm.
Finally,
in
a
similar
time
zone,
yeah.
B
We
overlay,
which
is
great
yeah
and
today
we're
working
on
a
particular
issue.
I'll
just
share
my
screen
for
this.
B
Yeah,
so
this
issue,
Network
images,
tab
missing
from
alert,
detail
View.
This
is
a
bug
that
was
raised
about
a
week
ago
and
there's
already
there's
some
details
on
here.
There's
a
possible
fix,
so
yeah
we'll
just
dive
into
that,
and
probably.
B
I
did
yeah
yeah
yeah,
so
I'm
describing
the
instructions
that
I
left
for
myself
or
for
anyone
else.
Who
would
want
to
pick
this
up
yeah
and
it
includes
like
a
development
sort
of
fix
and
also
a
a
little
note
about
testing
how
it
might
be
tested
yeah.
That's
it
and
there's
a
little
bit
of
discussion.
B
Some
talk
about
severity,
although
it
oh,
it
has
actually
been
set
yeah.
So
that's
good,
so
it's
been
triaged
and
has
been
pulled
into
the
current
Milestone
as
well.
B
Pretty
much
yeah,
but
the
general
term
is
I,
think
just
deciding
how
important
something
is
yeah,
so
part
of
the
Triad
process
might
involve
closing
something
if
it's
minor
enough
or
if
it
yeah.
If
it's
worth
keeping,
then
it'll
be
given
a
priority
in
a
severity.
B
Also,
we
get
a
lot
of
issues
raised
that
we're
you
don't
really
know
which
team
should
own
it.
So
triage
also
includes
a
bit
of
like
just
determining
oh
this.
This
is
best
taken
care
of
by
this
other
team.
So
you
just
reassigned
you.
You
would
just
update
the
devops
group,
section
labels
and
then
yeah
and
into
I
think
it
would
show
up
in
the
triage
queue
for
that
team
at
some
at
whenever
they
do
triage
next
and.
C
B
We
do
it
I
think
the
general
thing
across
git
lab
is
we
do
it
weekly,
yeah
yeah,
so,
let's
open
it
up
a
deep
environment,
so
I'm
currently
on
master
I,
should
do
that
thing
where
we
create
a
branch
using
the
issue
number
that
we
talked
about
in
one
of
the
previous
live
streams.
A
So
you
can
do
that
in
the
in
the
in
the
issue
as
well.
B
A
C
A
A
The
only
issue
with
that
is
like
now
you
have
to
pull
it
and
then
move
to
that
I
did
this
a
couple
of
times.
B
B
A
I
didn't
realize
it
creates
a
draft
Emma.
That's
a
lot
better
yeah
yeah.
B
That's
correct
yeah,
so
I
should
fit.
B
And
I
reconfigured
a
couple
of
hours
ago
yeah.
So
actually
this
is
the
only
new
approach.
The
last
couple
of
hours,
normally
there's
like
pages
of
stuff,
but
it's
actually
still
the
weekend
for
the
US
going
to
Europe.
So
yeah.
B
So
I'll
switch
to
that
yeah
looks,
looks
like
it
works
cool,
so
now
I'll
just
open
up
my
give
environment
oops
did
not
mean
to
open
it.
B
C
B
At
while
we're
doing
this,
I
think
I'll,
just
actually
I
shouldn't
need
to
restart
that,
but
I'll
just
refresh
I'll
go
to
the
page
and
refresh
it.
So
we
have
something
to
compare
with
as
we
change.
Yes,
it's
still
booting,
oh
interesting.
C
A
Removed
that
I
removed
the
tab
from
the
metric
tab
component,
I
didn't
realize
it
was
being
rendered
elsewhere.
Yeah,
obviously
I
should
have
checked
for
that,
but
yeah.
What
might
be
a
little
bit
more
interesting
is
adding
the
like
updating
the
tests,
because
the
tests
sort
of
should
have
picked
up
this
bug,
yeah.
B
Yeah
totally
yeah
sorry
so
I'll
just
paste
this
in
and
then
we
can
run
the
tests.
B
So
if
we
were
going
to
do
like
an
integration
type
test,
I
don't
know
if
that
that's
what
we
need,
but
just
because
this
is
where
we
put
it.
What
do
you
mean
the
integration
test?
Sorry,
oh,
like
between
multiple
components,
because
it
has
I
think
the
reason
why
this
this
sort
of
goes
into
like
why
I
think
the
test
failed,
but
which
I
can
expect
to
briefly
explain.
B
B
This
is
this
is
actually
there
and
there's
a
test
and
I'll
just
quickly
find
that,
because
it
would
be
good
to
look
at.
B
But
it
passes
even
when
it's
not
rendered
on
the
page
yeah
here
we
go,
and
that
is
because
so
the
the
tabs
wrapper
got
removed
from
this
tab,
but
it's
stubbed.
So
it's
it's
just
shallow
mounted.
Basically,
and
because
it's
shell
amounted,
it
doesn't
care
if
there's
a
GL
tab
inside
it
or
not.
C
B
If
we
were
to
like
print
out
the
HTML
of
the
of
the
like
top
level
component,
it
would
just
show
metric
image.
Tab
stump,
there's
one
line
and
nothing
inside
it.
Yeah.
A
B
B
A
B
It's
kind
of
a
weird
one
that
you
could
all
you
could
make
the
argument
that
that
a
JavaScript
spec
isn't
the
right
place
to
test
this
that
actually,
this
would
be
better
soon
as
a
features
a
bit
like
a
ruby
capybara
one
that
renders
the
page
and
checks
that
the
tabs.
A
C
B
Good
question:
do
we
we
probably
should
have
so
I
would
say
it's
been
missed
or
maybe
it's
there
and
it's
passing
when
it
shouldn't,
but
yeah
I
can
quickly
have
a
look
at
that
as
well.
So
it'll
be
like
feet,
alert.
C
B
Think
shows
you
like
details
and
that's
a
so
there's
nothing
where
it
says:
checks
for
the
metrics
tab,
so
yeah.
This
is
where
we
would
do
it.
A
C
B
Right,
yes,
yeah.
It
makes
sense
to
to
try
and
close
this
issue
off,
because
it's
a
bug
and
and
add
a
test,
and
if
it's,
if
it's
fast
to
add
a
test
like
if
we
could
do
it
right
now,
then
we'll
submit
both
yep.
If
it
proves
to
be
a
little
bit
harder,
then
it's
better
to
fix
the
bug
and
then
merge
the
test
later
yeah.
B
This
one
in
particular
has
this
because
it
was
actually
created.
The
bug
was
caused
in
1507
the
milestone
for
things.
Even
it's
interesting
that
that
happened,
because
it
means
currently,
the
bug
only
affects
gitlab.com
and
it
doesn't
affect
self-hosted
instances.
A
B
Yeah,
that's
something
to
know
that
worth
knowing
for
the
listeners
of
this.
If,
if
you're
not
aware
that
there
are
like
different
ways
to
deploy.
B
And
the
main
one
with
the
most
users
is
like
the
cloud
version
where
that's
on
getlab.com,
but
there
are
tons
of
customers
that
are
using
that
are
self-hosting
their
own
one
and
there's
also
an
option
for
gitlab
to
post
and
dedicated
instance
for
a
customer
if
they
want
that
as
well,
that
one's
called
get
laid
dedicated
and
it's
pretty
new
you
see
but
yeah,
so
the
just,
because
we
deploy
to
getlab.com
like
every
day
this
bug
will.
It
does
exist
in
githmet.com.
B
There's
like
an
example
of
it
there,
but
it
doesn't
exist
in
self-hosted,
because
the
15.7
self-hosted
release
hasn't
been
created.
Yet
yeah
will
be
created
really
soon,
though
so,
like
probably
in
the
next
week.
So
that's
why
it's
like
yeah!
That's
why
I
would
consider
fixing
the
bug
and
doing
the
test
as
a
follow-up
yeah
good
question,
though
yeah
so
I'll
start
off
by
oops
opening
that
file
again.
B
Sorry
I
just
want
to
have
a
next
to
the
other
file,
so
I've
got
the
code
here,
the
JavaScript
test
and
the
feature
speech
yep
yeah.
So
let's
find
out
where
that
this
is
being
used.
So
metric
image
says
there
we
can
confirm
going
into
it
that
there's
no
tab
wrapper,
but
the
other
tabs
in
this
alert
details
have
it
so
yeah
we'll
want
to
just.
B
B
A
B
C
B
Yeah
yeah
and
it's
got
the
starter
test
ID
and
we'll
see
what
we
did
here:
yeah,
so
that
that's
looking
pretty
much
the
same
as
this
a
test
ID
still
on
Tab
that
that
is
presumably
used
for
this
spec.
C
B
The
component,
so
we
may
actually
not
even
need
that
data
test
ID,
let's
have
a
look
at
the
tabs
config
and
then
go
search
for
it.
B
Respect
yeah,
so
those
tabs
have
been
connected
to
rear
to
view
router,
I
think
yeah.
So
there's
a
test.
That's
confirming
that.
B
For
each
tab,
when
you
sit
the
current
tab
index
as
zero
one
or
two
then
ID
for
that
tab
gets
pushed
to
the
router
to
the
browser
history.
The
interesting
thing
with
this
is
actually,
when
you
look
at
the
indexes
we
because
Matrix
has
been
removed
from
the
tab
component.
The
indexes
are
also
now
wrong,
like
this.
In,
according
to
the
GL
tabs
component,
activity
has
index
of
one,
so
this
actually
causes
another
bug
that
is
described.
B
Relatedly
I'll
just
show
that
really
quick.
So
it's
the
thing
where,
if
you
click
the
activity
feed
tab,
you
end
up
with
metrics
in
the
URL,
because
the
metrics
tab
is
missing
from
metabolist,
so
yeah.
That's
also
an
interesting
like
thought
about
the
way
this
implemented
it.
It
wouldn't
really
work
if
the
tabs
were
being
added
dynamically,
for
instance
like
if
they
could
be
shown
in
some
cases
and
hidden
in
other
cases,
the
sort
of
the
the
way
the
rat
has
been
done
would
need
to
be
slightly
tweaked,
but.
B
B
Yeah-
and
you
can
see,
there's
a
helpful
comment,
actually
discouraging
that
exact
thing
yeah,
so
that
that's
something
that
would
have
come
up
in
review
and
possibly
there
should
be
a
follow-up
to
refactor
this
yeah
and
in
theory,
you
should
be
able
to
mount
the
tabs
and
tips
that
you
should
be
able
to
mount
the
GL
tabs
component
and
the
GL
tab
component
and
do
a
full
Mount,
not
a
shell
amount,
and
then
click
I,
think
click
the
tab.
B
And
then
it
have
the
same
expect
and
it
should
work.
So
you
could
replace
this
with
clicks
yeah,
which
would
be
the
more
resilient
approach.
B
The
only
issue
is
just
if
I
don't
know
if
GLT
needs
something
special
when
you
mount
it
like
I
might
be
expecting
certain
picture
like
something
to
be
provided
on
the
context
or
something
like
that.
But.
B
C
B
Yeah
true
good
point
yeah
yeah,
so
we
should
be
able
to
save
this
and
then,
if
my
environment
were
working,
we
could
view
this
locally.
But
unfortunately,
it's
not
and
I'm
not
sure
why.
B
So
GDK
has
has
about
10
different
services
that
run
you
can
see
them
got
a
list
of
them
when
you
restart
and
then
GDK
tail
prints
off
the
last
something
like
hundreds
lines
of
logs
from
each
service.
B
So
it's
a
good,
a
good
like
quick
check
to
see
if
anything's
broken
and
then
you
can
also
go.
You
can
specify
servers,
so
you
can
go
GDK
to
our
webpack
and
then,
if
I,
like
GDK,
restart
webpack
I
mean
oh,
that's
fun,
oh
I'm,
not
on
the
right
directory.
B
If
I
restart,
we
pick
this
tail
should
update
yeah
so
tail
the
other
thing
the
tail
is
once
it's
running
at
all:
live
print
anything
new
that
gets
there.
It
gets
added
to
the
logs.
C
B
Yeah
and
even
though
there's
like
a
ton
of
warnings,
this
is
actually
a
healthy,
looking
webpack
because
it
says
that
your
project
is
running
at
us.
This
IP
import.
B
Yeah
so
WebEx,
fine,
that's
what
that
tells
us
rails
web
there's
another
one
check.
B
This
one
is
worrying
me
because
it
says
it's
shutting
down
it's
the
last
thing,
I
see,
but
maybe
workers,
maybe.
B
Workers
and
it's
actually
still
running
I'm,
not
sure
get
lab
work
course.
This
just
looks
like
some
regular
status
messages
connect
no
such
file
or
directory
yeah.
That
also
doesn't
look
good.
B
I
reconfigured,
but
I
didn't
check
that
it
was
working
so
yeah,
so
I
think
for
now
we're
just
gonna
have
to
keep
going
with
the,
but
the
stream
and
I'll
figure
out
the
environment
later.
What
we
can
do,
though,
is
we,
can
look
at
click
and
run
the
tests,
so
I
can
run
these
ones
first
start,
and
then
we
can
also
run
the
feature.
Spec
maybe
add
something
there
before
we
do
that
I'll
just
commit
what
we've
added
yeah.
B
And
it
checks
it,
there's
no
secrets
being
committed,
which
is
great
and
then
we'll
push.
This
it'll
run
some
more
hooks
and
I'm
going
to
assume
that
they
pass
and
have
a
look
at
the
tests.
So.
B
And
these
tests
were
passing
before
it
broke
and
we're
still
passing
after
it
broke
so
I,
don't
expect
anything
to
fail.
Yeah
that
all
looks
fine
yeah.
So
one
thing
we
talked
about
was
we
could
do
a
full
Mount
of
the
tab
of
the
GL
tags
component
and
check
if
that
exists,
or
something
like
that.
A
So
yeah
I,
just
I
recently
did
the
tests
for
incident
tabs
and
what
I'm
pretty
sure
we
did
is
because
metrics
isn't
always
showed
because.
C
A
Is
part
of
EE
and
it's
not
part
of
so
you
only
get
it
if
you
pay
for
it
right.
B
It
might
be
different.
Oh
okay,.
A
A
B
Okay
Uncle
response
as
premium,
and
that
said,
everything
else
is
available.
C
A
B
A
Yeah,
okay,
sweet!
So
if
you're
running
that,
then
we
need
a
test
to
say
metric
should
not
be
shown,
but
here
we
should
always
assume
that
metrics
is
shown.
C
C
A
C
A
Index
can
change,
but
in
this
case
index
doesn't
change.
So
that's
fine,
so
yeah
I
think
it
would
be
easiest
to
do
yeah
a
a
non-shallow
mount
so
a
full
Mount
and
then
just
check
to
see
that
we
have
the
titles
and
we
can
navigate
to
the
tabs.
B
Cool
yeah,
so
let's
do
that
yeah.
So
we
already
have
Mountain
method
Mount
in
this
case.
A
B
A
B
A
B
B
Yeah,
it
should
definitely
I
mean
this
is
called
tab
navigation,
so
it
makes
sense.
Currently
all
it
does.
Is
it
checks
that
the
right
thing
is
pushed
to
the
router
right
or
I?
Guess
to
be
more
complete?
It
should
check
what
you
just
said,
which
is
which
tab
is
actually
displayed,
yeah
yeah,
so
we
could
make
like
one
little
test.
B
We
could
start
with
just
Matrix,
so
not
worry
about
the
parameterization
of
it.
Yet
just
do
one
for
metrics,
where
it
clicks
the
tab
and
then
checks
to
see.
What's
displayed,
maybe
yeah
yeah,
it's
a
bit
more
of
an
integration
test
that
because
you're
kind
of
like
testing
the
internals
of
GL
tab
a
little
bit
by.
B
It
true,
so
that's
the
only
downside
with
the
Tesla
that
makes
sense,
but
because
it's
like
such
a
core,
reliable
piece
of
functionality,
I
I,
don't
think
like
if
we
ever
change
geotabs
so
that
clicking
on
the
tab
didn't
change
tabs,
we
would
break
so
many
things
yeah.
So
absolutely.
A
C
C
B
B
A
B
There
would
be
a
bit
of
like
probably
digging
through
the
rather
docks
and
looking
at
other
tests
and
things,
whereas
the
the
clip
one
at
least,
should
be
pretty
simple
to
figure
out
if
it's
going
to
work
or
not
yeah
but
I
agree
like
both.
Both
tests
have
validity.
A
I,
don't
know
if
we've
actually
implemented
it
yet
in
incidents,
but
what
I?
What
I
feel
like
we
did,
or
what
we
talked
about
or
imagined
is
like
passing
the
like
setting
the
router
query
when
we
Mount
when
we
load
the
component,
because
maybe
for
more
context
here,
what
I
found
quite
confusing.
C
A
A
So
we
have
a
component
sorry
A,
View
application
that
is
rendered
by
the
Ruby
on
Rails.
That
now
takes
over
the
routing
from
a
particular
part
in
the
URL,
so
we
have
a
base
URL
and
then
after
this
is
controlled
by
a
view.
So
what
I
imagine
we
would
do
is
when
we
create
the
component
or
even
create
the
application
The
View
application.
We
would
give
it
the
router
details,
which
would
include
like
hey
you're,
on
the
metrics
page
Maybe
I'm,.
B
Not
sure
we
do
have
on
here
that
the
Almond
incident
tab
spec.
A
B
We
have
one
that
checks
have
a
certain
tab.
Is
there
and
it
even
clicks
the
button.
So
we
could
support
it
gets
the
button.
We
can
see
what
it
does
yeah,
so
it
clicks
it.
It
finds
the
active
tabs.
That's.
A
C
A
A
Actually,
testing
the
tabs
gitlab
tabs
component,
because
this
component
also
tracks
which
tab
is
active
because
it
does
some
funny
there's
some
funny
little
workarounds
in
this
component.
C
B
B
Yeah
I
mean
this.
This
may
be
the
simplest
way,
the
most
pragmatic
way
of
hooking
into
that,
because
it
if
you
have
a
third-party
component
and
it
doesn't
expose
something
like
the
active
tab
as
an
API,
then
you
have
there's
nothing.
You
can
rely
on,
potentially
so
without
having
to
resort
to
internal
implementation,
details
so
yeah
yeah.
For
now
we
could
just
follow
a
similar
pattern
to
this.
Maybe.
B
C
A
A
Implementation,
because,
usually
on
gitlab
tabs,
you
just
have
the
current
active
tab
as
a
search
parameter
in
the
like
URL
parameters,
but
instead
of
using
a
URL
parameter,
we're
actually
changing
the
I.
Don't
know
what
you
call
it
like
the
core
URL.
So,
instead
of
using
question
mark
active
tab
equals
metrics
we're
instead
using
like
issue
incident
or
in
this
case,
alert
slash,
Alert,
ID,
slash,
metrics
or
timeline.
A
B
But
for
alert
details
it's
using
the
the.
A
B
Using
view
rather
yeah,
so
that's
why
this
is
not
available
for
us,
perfect,
yeah,
yeah
and
then
what
what
we
were
talking
about
with
the
different
testing
levels.
B
So
we
we
mentioned
like
we,
we
just
looked
at
any
unit
test,
which
was
checking
which
tab
was
available,
which
tab
was
currently
viewed
and
we're
also
talking
about
adding
a
feature
test,
which
is
the
Ruby
one
as
a
way
of
doing
like
a
more
complete,
robust
test.
But
the
the
only
problem
with
this
is
we
have
this
testing
pyramid
where,
as
you
go
up,
the
tests
become
more
expensive.
B
Our
policy,
as
we
as
we
describe
it
somewhere
on
this
page,
is
yeah.
These
tests
should
only
be
used
when
the
internal
state
of
objects
needs
to
be
tested,
cannot
be
tested
at
a
lower
level,
only
test
the
heavy
path,
but
make
sure
to
add
a
test
case
for
any
regression
that
couldn't
have
been
caught
at
a
lower
level,
with
a
better
test.
So
interesting
that
this
is
actually
the
exact
case.
B
That
means
that
so
A
regression
is
what
has
just
happened.
There
was
a
piece
of
functionality
that
was
working
that
got
broken
so
that
type
of
bug
that
subtype,
it's
like
a
subset
of
bugs
I,
guess
that
we
call
regressions
and
yeah.
So
it's
not
something
we
couldn't.
B
You
know
some
cases
that
we
wouldn't
have
like
considered
like
a
security
bug,
wouldn't
be
a
regression,
because
it's
not
like
something.
If
there
was
a
security
bug,
it
was
never
probably
never
working
correctly,
but
in
this
case
the
functionality
was
working
correctly
previously
and
it
has
been
broken
and
yeah
so
that
that
is
called
a
regression
right.
B
B
A
B
And
add
them
at
the
lowest
level
possible,
so
yeah
and
yeah,
as
we've
seen
already
by
looking
at
the
fact
that
there
is
a
unit
test
for
this
and
it
didn't
catch
it,
then
we
know
that
it's
they're,
it's
slightly
tricky
like
it's,
not
just
obvious
that
a
unit
test
is
always
going
to
catch.
This.
B
C
B
C
B
It'll
we
can
look
at
the
existing
one;
it
will
render
the
it
sets
up
some
data,
so
it
sets
up
like
a
user,
a
project,
an
alert
at
signs
in
so
so.
The
back
end
is
running
through
all
this.
While
this
test
is
executing,
there
is
like
a
mock
backing
or
like
a
you
know.
Decent
amount
of
the
back
end
is
actually
running,
and
then
it
will
visit
the
page
that
is
under
test
and
then
start
making
decisions.
B
You
guys
don't
want
to
say
it
yeah.
So
in
this
case,
I
think
it's
worth
having
one
to
check
the
tabs,
because
so.
B
There's
enough
complexity
going
on
there
by
only
doing
a
JavaScript
test,
there
will
always
be
potential
that
you've
missed
something
yeah.
A
B
Makes
sense
yeah,
because
the
fact
that
this,
as
you
mentioned
about
the
router,
it
actually
does
have
a
route
in
rails
and
it
has
a
front-end
router
and
those
things
have
to
also
work
together
so
by
only
testing
it
in
JavaScript
you're,
not
getting
there
for
interaction.
So
yeah
in
the
case
of
like
tabs
that
are
hooked
into
the
router
I
think
it's
definitely
worth
having
a
feature
test.
B
C
B
B
C
A
Well,
that
might
just
about
be
enough.
It's.
B
A
B
Yeah
exactly
yeah,
so
in
our
case,
let's,
let's
add
this.
So
let's
find
the
right
level
when
actor
has
permission
to
see
an
alert.
B
It's
a
good
question.
Do
the
tabs
appear
when
you
do
when
you
don't
have
permission?
That's
my
GDK
was
working.
I
could
test
it.
B
Yeah
thanks,
let's
just
assume
for
now
that
you
do
have
to
be
logged
in
because
at
least
if
you're
logged
in
we
know
it
works,
maybe
we
can
move
it
outside
of
this.
A
B
B
Yeah
exactly
so,
you've
got
yeah
logged
in
or
logged
out
and
then
you've
also
got
guest
reporter
developer
maintainer
owner
as
all
the
different
roles.
B
There's
nothing
in
there
about
the
level.
Oh,
you
need
to
be
developer
role
to
access
alerts.
Okay,
so
that
tells
us
that
you,
don't
you
probably
don't
see
much
at
all,
if
you're
not
a
developer
and
then
once
you're
logged
in
you
can
probably
see
everything
below
this
like
the
alert
details,
Tab
and
the
metrics,
Tab
and
stuff
yeah.
A
C
B
That's
what
that's
saying
that's
what
it
seems
to
be
saying:
yeah
would
have
to
double
check
that
to
see
if
that's
actually
the
case
of
the
product,
but
most
likely
it
is
so
then
sorry.
A
You
push
your
commit
before
right.
I
just
realized
that
my
GDK
is
running.
I
can
just
pull
your
branch
and
we
can
test
it
online
yeah.
B
Yep
I'll
put
a
link
to
the
Mr
in
the
chat
foreign.
B
Where
are
we
at?
We
were
okay,
yeah,
so
I've
just
copied
this,
and
this
is
obviously
not
going
to
work
because
it's
doing
all
sorts
of
incident
specific
stuff.
So
we
want
to
have
a.
We
look
at
the
page
structure
just
to
see
what
which
class
to
select
within
and
how
to
find
the
incident.
Other
alert
tabs
and
things
like
that,
yeah
so
over
to
alert
metrics.view.
B
Pilot
details,
don't
be
sorry,
is
there
a
top
level
class
in
the
template?
Doesn't
look
like
it
for
now.
We
can
leave
that
out
and
we
can
clean
that
up
later
we
can
have
a
look
at
what
how
we
can
narrow
down
the
search.
The
reason
for
doing
that
by
the
way
is
as
just
execution
time.
So,
if
you,
if
you
start
doing
just
find
query
on
the
entire
page,
there's
going
to
be
a
lot
of
irrelevant
elements
that
are
being
rendered
that
you
then
I
like
searching
through.
B
B
Let's
just
not
worry
about
that
yet
then
we
have
finding
the
tabs
and
the
insulin
test.
So
let's
have
a
look
at
the
Details
page
to
see
if
there's
something
on
the
tabs
yeah.
So
there
is
a
test
ID
there
already.
So
we
can
use
that.
B
Yeah
hard
but
strange,
that's
what
it
is.
Maybe
we
could
tidy
that
up
later
as
well
and
then
aggregate
failures.
That's
we
I,
don't
even
know
if
we're
gonna
have
multiple
expects.
So
let's
just
remove
that
for
now
yeah
and
I.
Think
or
maybe
we
can
leave
it
because
I
think
we
want
to
do
this.
We
want
to
check
that.
B
Oh
interesting,
so
this
is
checking
for
on
the
incident
page.
This
checking
that
the
instant
title
is
on
the
page
somewhere
we're
not
really
worried
about
that
right
now.
We
we
actually
maybe
replace
rename
this.
So
we
can
say
what
we're
actually
doing.
It
shows
the
metric
images
tab.
So
okay
will
keep
us
as
small
as
possible
for
now.
So
that's
all
we're
doing
in
this
test
is
that
we
want
to
just
show
that
that
tab
exists.
We're.
B
C
A
B
A
So
I'll
stop
your
screen
sharing
and
do
mine
yeah
yeah
I'll.
Stop
that.
A
So
it
shows
alerts,
but
it's
got
a
spinner
that
doesn't
finish.
Oh
interesting,
strange.
C
A
B
Right
yeah,
yeah
yeah,
so
that
was
about,
looks
like
it's
at
least
fixed
for
now.
B
Yeah
and
now
there's
now
there's
another
bug
that
that
second
bug
that's
interesting.
There
is
a
chance
that
that
is
a
environment
issue.
B
C
B
A
B
A
B
B
C
B
Cool
yeah,
so
that
that
looks
like
it
works
yep,
so
it
should
be.
It
should
be
okay
to
go
ahead.
B
The
fix
and
this
test
right
yes,
I-
can
I
can
share
again
if
I
want
to
have
a
quick
little
last
look
at
the
these
tests
yeah.
So
we
want
to
show.
B
Metrics
tab,
actually
we
don't
even
care
about
the
description
right
and
we're
not
clicking
the
tab
yet
so
really
all
we
need
is
just
this
line.
A
B
I
think
oh
no,
that
is
the
right
whoops!
That's.
A
A
B
Here
yeah,
so
this
should
be
interesting.
I
have
a
prediction
about
this:
that
my
environment,
since
my
environment
isn't
running,
and
this
test
needs
the.
B
It
might
have
not
work,
but
what
we
could
do
is
push
the
test
and
see
what
happens
on
the
pipeline.
Yeah.
B
Be
fine,
yeah,
I'm,
I'm,
reasonably
confident
that
the
pipeline
will
pass
and
or
you
could
you
could
check
it
out
and
run
the
test
on
yours,
true
yeah,
oh
I
should
say:
I
have
no
idea
what
to
say
now.
B
A
Oh
yeah
I
guess
it
would
create
if
it
was
running
all
of
the
aspect
tests,
it
would
create
the
environment
once
and
then
yep
yeah.
That
makes
sense.
C
B
Just
speak
or
I'll,
let
it
triple
image
tab.
This
will
be
that
commit
will
be
squashed
anyway.
So
I'm
not
too
worried
about
the
commit
message,
yeah
and
then
I'll
push
it
if
actually
I
just
cancel
that
if
we
want
to
not
run
the
pipeline
I
believe
we
can
do
this
fancy
thing
where
we
go
option:
CI
dot,
skip.
B
A
B
B
And
then
I'll
you
can
propose
and
run
it
yeah
yeah
I'm
interested
to
see
if
this
is
the
exact
space
tests
not
to
add
I'll
turn
around
the
Chrome
driver
all
up
yeah.
So
let's
try
pushing
this
and
then
in
the
gitlab
UI.
We
should
see
under
pipelines.
So
it's
existing
one.
Oh
my
gosh,
that's
still
running.
B
B
Think
my
environment
just
isn't
working
it,
so
it's
probably
not
gonna,
but
all
sorts
of
stuff
is
breaking.
B
A
B
So
yeah
just
interactive
rebase
fix
it.
It
might
be
a
faster
way
to
do
that,
but
now
I
have
to
force
push
with
release
because
I've
already
pushed
it
was.
A
B
Usually
this
is
what
you
want
yeah,
as
opposed
to
force.
Push
like
the
full
force
push
if
you
like,
deliberately
trying
to
overwrite
someone
else's
commit
so
I
like
to
I
like
to
use
that
yeah.
B
Yeah,
that's
that's
90
of
the
time
anyway,
but
yeah.
The
other
thing
yeah,
the
other
use
case
I
suppose,
is
like
sometimes
you're
working
on
a
major
place
and
you've
done
like
slash
rebates
and
in
the
UI
like
the
gitlab
UI,
and
it's
like
trigger
and
rebase,
and
then
a
fast
push
will
just
overwrite
that
yeah,
actually
a
force
bushel
at
least
will
not
are
for
special
at
least
May
override
that
as
well
I'm,
not
sure
but
yeah
at
least
some
of
the
time
it's
safer
interesting.
B
B
B
B
B
I'll,
let
you
pull
pull
that
and
run
it.
James
yep.
C
A
B
A
C
A
Have
you
seen
the
new
gitlab
front,
end
Copilot?
While
this
is
running
no
I?
Haven't
it's
pretty
cool
some.
A
B
A
I
think
no
it's
no
I
yeah
I
met
one
of
the
guys
working
on
it
and
he
said
like
I,
don't
I,
don't
think
it's
a
problem,
that's
cool!
Maybe
this
is
an
issue
because
it's
a
I
didn't
call
it.
A
So
then
you
can
do
like
a
tab
and
cool
it'll
like
predict
what
you
want.
A
B
So
that's
similar
to
GitHub,
copilot,
I,
suppose
yeah
exactly
yeah.
C
A
No
I
did
have
it
running
foreign
yeah.
It's
supposed
to
just
predict
yeah
same
as
GitHub.
C
A
And
it
was
a
bit
funny
because
it
yeah,
like
I,
created
a
HTML
page
and
I
was
trying
to
do
this,
and
then
it
was
giving
this
information
as
if
I
was
writing
it
from
a
back-end
service.
Writing
HTML
like
to.
C
A
C
B
There's
some
elastic
search
and
exercise
takes
a
little
bit
of
time.
Did
you
know
that
it's
possible
to
Cache
that
if
you're
running
didn't
I
speak
a
lot,
there's
a
I
think
it's
a
gdk.yaml
option
to
education
and
then
yeah?
It
seems
to
be
it's
far
enough
that
when
you,
if
you
do
like
ddk
update
at
all
switch
off
it'll
like
reset
location,
so
let's.
A
A
Or
maybe,
if
a
level
above
this
anyway.
B
Yeah
I
forget
what
the
details
are.
What's
that.
B
This
is
a
good,
a
good
test
of
a
test
setup
from
scratch.
A
B
A
What's
the
reason
why
we're
not
I
think
this
will
do
it?
What's
the
reason
we're
not
running
this
on,
like
on
gitlab.com.
B
B
Days
but
half
an
hour
at
least
so
yeah
and
Theory
running
it
locally
should
be
faster,
but
we're
we're
just
seeing
it
that
that
if
you
got
and
that
here.
A
B
B
A
A
Otherwise,
we
can
have
other
interesting
chats.
B
The
other
option
could
be
just
to
end
the
stream,
because
it's
not
might
not
be
particularly
engaging
particularly
interesting.
That's
true
to
wait
around
for
another
few
minutes,
but.
A
Posted
the
link
to
the
Mr
anyway,
yeah
yeah
cool.
Let's
stop
it
then
I'll
do
that,
but.
B
Yeah
we've
looked
at
so
we
made
a
fix,
we
updated
some
feature
specs,
we
talked
about
different
ways.
We
could.
B
A
B
Yeah
I,
just
actually
just
noticed
a
problem
as
well
that
we
I
didn't
rename.
The
variable
incident
tabs
should
be
alert
tabs,
so
I'll
just
make
that.
A
B
C
C
A
C
C
C
B
A
B
B
B
A
C
A
A
Yeah,
so
it
must
have
automatically
cached
that
elasticsearch
just
have
it
run
an
aspect
test
in
the
long
term.
Yep
nice.
C
A
B
A
A
All
right
can
I
just
do
fixed
tests,
fix
aspect.
B
Tests
so
yeah
that's
going
to
be
that's
going
to
be
squashed
anyway,
so
yeah
yep.
B
Cool,
so
that
the
email
is
actually
pretty
close,
I
just
needs
the
description.
I
need
the
description,
some
screenshots
some
how
to
validate
the
it
for
the
reviewer,
like
some
steps
to
reproduce
it
and
stuff,
but
yeah.
It's
pretty
close.
So.
A
B
Nice,
because
neither
of
us
are
allowed
to
review
it
since
we're
both
pushed
to
it
now
most
committed
yeah,
cool,
perfect,
well,
yeah
I
think
that
that's
a
good
place
to
wrap
it
up.
Yeah.
A
Perfect,
it's
been
our
most
like
best
wrapped
up
stream,
I
think
yeah.
A
Thanks
for
watching,
oh,
if
you
have
questions
for
Tristan
or
I
instead
of
asking
in
the
YouTube
channel,
you
can
ask
in
the
issue
or
the
Mr
that
we're
linked
to
yeah
and
then
we'll
actually
see
it.
Yeah.
B
And
there's
a
community
Discord
where
you
can
ask
questions
as
well:
more
general
questions
about
oh
yeah,
how
all
this
works
and
contributing
and
stuff
sweet.