►
From YouTube: GitLab Runner Open Office Hour
Description
This call is part of our quarterly GitLab Hackathon - https://about.gitlab.com/community/hackathon/
First reviewing MR: https://gitlab.com/gitlab-org/gitlab-runner/-/merge_requests/2582
Second Reviewing MR: https://gitlab.com/gitlab-org/gitlab-runner/-/merge_requests/2597
A
Right
going
live,
I
guess
we're
live
hello!
Everyone
good
morning
afternoon
evening,
I'm
christas
a
senior
called
contributor
program
manager
and
with
me
I
have
steve
like
an
engineer
for
the
running
program.
A
We
are
on
the
beginning,
let's
say
of
our
hackathon
here.
It's
great
to
have
you
all
with
us.
Welcome
welcome
just
some
logistics
reminder.
Let
me
just
briefly
share
my
screen.
Didn't.
A
All
right,
can
you
see
my
screen?
It
has
a
weird.
Let
me
change
the
orientation
of
the
screen,
the
size
of
the
screen,
great,
so
just
a
quick
reminder
of
the
call
of
conduct
we
take
the
here
at
gitlab.
We
take
the
safe
and
inclusivity
of
our
event
seriously.
So
just
just
a
brief
reminder
that
all
the
events
that
we
run
are
under
the
community
code
of
contact
that
can
be
found
on
the
link
here
on
the
slider.
A
A
We
keep
an
eye
on
all
our
communication
channels
and
merge
requests
on
the
channels
as
well
so
yeah,
but
if
we
miss
something
or
if
you
something
just
let
us
know
earlier
today,
we
began
with
our
hackathon
kickoff.
It
was
just
a
brief
introduction
of
the
hackathon.
How
the
day
is
gonna
go.
A
The
two
days
are
gonna
go,
and
this
is
the
first
of
the
five
sessions,
the
rest
of
the
five
sections
that
we
have
scheduled
for
today
and
tomorrow
it's
the
runner
office
hour
on
the
hackathon
on
the
hackathon
page.
You
can
find
more
information
about
the
hackathon,
for
example,
the
number
of
the
merger
quests
that
have
already
been
submitted,
which
are
25
yay
37.
Sorry,
this
is
amazing,
if
you
do,
if
you're
new
at
gitlab
into
the
products
as
well
feel
free
to
check
out
the
contribute
page.
A
The
contribute
page
consists
a
bunch
of
information
on
how
to
contribute
specifically
about
development,
which
is
the
hackathon
about
it's
all
the
necessary
information
about
finding
issues
and
also
setting
up
the
development
environment.
A
special
highlight
in
the
new
addition,
which
is
the
git
pod.
B
A
A
If
you
need
any
help,
we
have
the
the
contributors
guilty
room.
It's
a
jitter
channel
where
all
the
community
members,
the
core
team
within
gitlab
and
also
gitlab
members,
are,
are
there.
So
we
can
provide
real-time
support
in
case
that
you
need
anything.
It's
also
bridged
with
gitlab's
internal
slack
room
room
yeah.
So
there
is.
There
is
also
the
opportunity
for
other
members
to
join
whenever
needed,
so
yeah
welcome,
and
with
that
I
will
stop
setting
my
screen
and
I
will
pass
it
over
steve.
C
Thank
you
so
much.
Thank
you
for
that
kind
introduction.
So
these
officers
are
usually
very
very
freeform
from
our
end.
It
will
be
either
answering
or
asking
answering
questions
from
the
community.
I
see
some
people
already
joined
our
call,
so
if
they
have
any
questions
or
anything
they
want
to
discuss,
this
is
the
time
to
do
it.
C
We
can
discuss
issues,
merge,
requests
or
anything
like
that,
and
then,
if
we
still
have
time-
and
there
are
no
answers-
no
questions
anymore-
I
will
choose
some
merch
quests
that
are
opened
by
the
wider
community
and
I'll
do
some
live
code
review.
The
point
for
that
is
mostly
to
show
the
other
side
of
what
a
code
review
looks
like
from
from
a
maintainer
perspective,
so
there's
no
like
barrier
between
the
community
contributor
and
us,
and
it's
a
bit
more
transparent
on
what
goes
on
and
to
reviewing
code
review.
C
C
A
A
C
Example:
okay
go
to
review
in
general,
so
if
there
is
no
any
other,
if
there
isn't
any
other
questions,
I
can
get
started
with
one
of
them
that
I
have
in
mind
and
we'll
go
from
there.
You,
when
I'm
doing
code
review,
feel
free
to
jump
in
at
any
point
in
time.
Ask
questions
or
like
say
something
else.
So
I
don't
mind.
C
So
the
merge
request
I
had
in
mind
is
merch
press
two,
two
five,
a
two
and
this
one
is
mostly
follow-up,
merge
request
that
we
had
from
the
same
community
contributor
where
this
is
talking
about
the
kubernetes
executor.
So
if
you're
not
familiar,
kettleberry
supports
multiple
executions
infrastructure,
so
one
of
them
is
stock.
Another
one
is
kubernetes,
so
we
run
your
ci
job
inside
of
kubernetes
cluster
and
one
one
of
the
things
that
we've
been
working
on
at
the
moment
is
adding
support
for
host
aliases.
C
C
That
means
that
the
job
that
is
running
your
test,
that
is
connecting
to
the
database
is
starting
services
right.
So
it's
starting,
for
example,
postgres
database
mysql
database
whatever,
and
then
your
tests
need
to
communicate
with
this
database
right
over
the
network.
Now
I
won't
go
into
too
much
technical
details,
but
basically
we
need
to
have
here.
Is
these
keywords?
The
yes
keywords
where
you
can
specify
give
me
a
second
to
find
a
good
example
on
this.
This.
A
C
Awesome
thank
you
for
that.
So
you
can
specify
alice's
right.
You
can
either
communicate
with
the
postgres
via
the
my
postgres
address
or
the
db
postgres
right.
It
is
mostly
like
convenience,
sick
and
there's
also
host
aliases,
so
I'm
not
sure
if
you
ever
try
to
modify
your
etc
host
directory.
C
You
might
point
a
certain
ip
address
to
a
domain
manually,
so
it's
like
an
internal
dns
server,
it's
very,
very
useful
for
like
internal
applications
and
so
on
and
so
forth.
So
we
did
this
in
a
previous
merger
press.
But
when
we
were
doing
this,
we
found
a
new
where
we
were
always
adding
the
localhost
ip
address.
So
it's
12
0,
0
1..
C
There
are
all
the
time,
no
matter.
If
you
had
services
defined
in
your
gitlab,
cim
and
file
or
not,
which
is
it
wasn't,
causing
any
problems,
but
it
shouldn't
be
therapist
while
it
might
cause
problems
in
the
future
and
though
it's
like
somewhat
of
an
unexpected
behavior
right.
So
the
main
goal
here
is
to
remove
us
to
only
add
this
host
alias
inside
of
atc
hosts
when
we
actually
needed
to
and
I'll
show
you
an
example
of
what
we're
trying
to
solve
here.
C
A
Can
you
please
paste
the
merge
request
link
here
to
the
top
that's
out,
maybe
so
I
can
distribute
it.
Thank
you.
C
Now
so
I
started
the
runner
locally,
and
this
is
just
the
development
I
have.
The
gitlab
runner
code
base
checked
out
locally
and
I
can
just
run
the
main
go
binary
main
file,
and
now
I
can
see
that
I
have
zero
port
at
the
moment
running.
C
C
Cat
ptc
hosts
and
you
can
see
entries
added
by
host
addresses
this
is
kubernetes
feature
and
then
we're
just
saying
port
one.
Two,
oh
twelve,
one
two
seven
point:
zero
zero
one
right,
which
is
not
what
we
want
we
want.
We
only
want
to
add
this
when
we
actually
need
it
right,
and
this
is
how
it
works
when
we
have
a
service
defined.
So
let
me
go.
C
B
C
C
It's
running
and
I'm
just
gonna
cut
the
edc
host
files
again
and
I
should
see
the
following,
so
it
added
the
localhost
and
the
host
analysis
right.
So
when
you
ping
db,
it
will
bring
the
localhost
and
the
coop
energies
will
run
out
everything
for
you
to
the
database
service
right
so
to
rear.
To
reiterate,
we
don't
want
to
add
this
when
we
don't
have
any
services
or
we
don't
need
it
at
all
right.
C
So
this
is
what
this
community
contribution
is
trying
to
achieve
and
we'll
take
a
look
at
it
together.
So
you
saw
me
that
I
got.
I
got
all
the
context.
C
I
tried
it
manually,
we're
producing
it
manually,
and
this
is
like
one
of
the
first
steps
I
do
when
I
do
a
code
review
just
because
I
want
to
understand
what
the
problem
is
and
where
the
problem
relies
before
actually
reviewing
the
code,
because
if
I'm
just
reviewing
code-
and
I
don't
really
know
what
the
problem
is-
it's
mostly
doing
reviewing
of
the
changes
instead
of
actual
actual
code
review,
of
what
we
need
to
do
to
achieve
this
program
right.
C
C
And
we
have,
this
is
what
we
have
on
the
master
branch
at
the
moment.
So
just
a
quick
rundown.
Actually,
I
won't
run
through
it
manually,
just
because
it's
a
lot
of
context
driven
so
I'll
check
the
branch
locally.
C
C
So,
let's
start
looking
at
the
diff,
what
changed
here
and
then
we'll
we'll
test
it
out
as
well
so
host
aliases
before
we
always
used
to
have
the
local
host
alice
here
and
probably
this
is
where
the
issue
was
happening
right.
We
were
just
defaulting
to
the
local
host
host,
alias
and
like
done
just
appending
to
it.
C
Whenever
we
need
to
which
is
not
what
we
want,
we
only
want
to
append
it
or
add
it
when
we
actually
meet
it
right,
so
we're
creating
an
empty
slice
here
and
then
here
we
are
host
aliases
host
name
and
alice.
So,
where
is
this
host
name
being
defined
and
where
is
this
alias
being
defined?
Let
me
check
it
out
here
so
host
name.
C
It's
just
appending
to
it
the
offers
and
then
it's
adding
the
alias.
So
this
one
is
for
services
and
hostnames
and
then
it's
literally
just
appending
to
the
host
names
when
we
actually
need
it.
If
it's
valid
for
there's
a
specification
for
dns,
it's
called
1123.,
we
validate
it
and
then,
if
it's
valid
we
add
the
alias
and
the
service
values
as
well,
and
then
we
do
it
at
the
bottom
here
if
we
have
any
aliases.
C
C
C
Here
so
this
is
good
and
now,
let's
move
to
the
next
file-
and
this
is
where
we're
actually
adding
tests
so
no
hostname
analysis
when
servers
only
with
parts,
so
first
before
doing
that,
actually,
let's
check
where
it's
adding
it,
because
sometimes
everyone
even
me-
I
do
it
like
we
end
up
adding
tests
to
cases
to
test
where
it's
not
doesn't
really
belong
to.
So
this
is
online
76.
C
B
C
So
this
is
adding
a
case
where
there
is
a
service
defined,
but
it
has
a
port
to
define,
and
this
is
for
the
check
in
this
one.
So
we
go
to
host
statuses,
we're
checking
if
this
the
services
imports
now
the
ports
are
not
really
useful
for
the
user.
These
are
mostly
for
web
ide
settings,
so
gitlab
itself
is
a
web
ide
and
then
you
can
define
certain
services,
so,
for
example,
you
can
have
file
syncing
and
so
on
and
so
forth.
C
So
this
is
what
it's
checking
here:
we're
still
defining
a
service,
but
we're
defining
a
port
for
it,
and
we
want
to
make
sure
that
there
are
no
no
host
aliases
right.
C
And
then
we're
also
adding
another
one
here:
hostile
uses
with
no
services,
so
the
user
specifies
their
own
host
aliases
inside
of
their
config
tunnel
file,
but
they
didn't
define
any
any
any
services
right.
So
we
don't.
We
only
expect
this
one.
So
I
see
two
two
improvements
that
we
can
make,
so
the
first
one
would
be.
We
are
not
really
like.
Well,
I'm
just
looking
at
this.
C
If
I'm
just
coming
through
this,
I'm
not
really
seeing
what
is
the
expected
result
right
now,
if
you're
familiar
with
go,
if
you
don't
define
a
variable,
if
you
don't
define
a
value
to
the
variable,
it
will
use
the
zero
value
and
in
this
case,
for
a
slice
it
isn't
on
this
slice
always
so
since
we
never
defined
it,
it
was
asserting.
A
C
Here
we're
just
checking
that
the
host
values
we
got
from
create
host
values
and
the
expected
one
are
the
same,
so
basically
we're
doing
a
quality
check
right.
C
So
I
think
it's
good
to
be
explicit
here
in
this
case,
just
because,
if
I'm
just
reading
through
the
test
cases,
I'm
saying
okay,
if
there's
only
a
service
defined
with
port,
I
expect
no
host
alexis
right.
So,
instead
of
not
having
it
it's
it's
a
bit,
you
have
to
know
what's
going
on
in
the
test,
so
that
is
one
suggestion
I
will
suggest
right
now.
C
C
C
B
A
C
Usually
like
to
play
suggestions
or
show
the
diff
of
it.
So
if
someone
do
the
change
for
the
user,
but
also
I'm
very
clear
of
what
I'm
expecting
or
what
I
think
it
should
look
like
just
so,
it
prevents
a
lot
of
back
and
forth
and
things
like
that,
and
sometimes
it's
easier
to
explain
code
with
code
instead
of
just
trying
to
explain
it
in
english
right
so
I'll.
Do
this
and
then
the
community
contributor
will
see
this
one
and
either
d
agree
or
disagree,
and
then
we'll
have
a
discussion.
C
Now
this
one
hosts
aliases
with
no
service.
I
have
feeling
we're
already
somewhat
testing
this
somewhere
else.
So,
let's.
C
That
we
have,
we
have
aliases.
C
C
So
services
is
empty.
B
C
C
A
C
C
C
Here
now,
one
word
scenario
I
see
is
like
we
here
we're
returning
an
empty
slice,
and
here
we're
returning
a
note
right
is
that
something
that
we
should
be
bothered
about,
or
not
at
the
moment.
I'm
not
sure
this
is
where
I
usually
just
either
think
about
it.
A
bit
like.
C
I
don't
know,
try
to
make
a
decision
within
an
hour
or
so
or
like
spend
some
time
thinking
about
it
just
to
see
if
it's
actually
a
good
idea
or
not
or
try
to
fix
it
and
see
if
that's
a
something
that
we
should
do
so
that
let's
see
why
it's
returning
unknown
here,
so
we
forgot
to
host
alice's
and,
let's
add
the
debug
breakpoint
here
and
run
to
and
debug
this
specific
test
case.
B
C
C
B
C
Me
a
bit
and
it's
called
empty
slice
declaration
for
violator
now
I've
I'll
apply
the
hint
that's
basically
doing
this
now.
I
won't
go
into
detail
why
this
needs
to
be
done
this
way,
but
what
I
will
do
is
I
will
give
you
a
link
that
explains
this.
This
is
like
an
internal
detail
about
go.
If
we
go
on
the
wiki
and
look
at
the
code
review.
C
C
Sometimes
like,
for
example,
when
we're
encoding
json,
which
in
this
case
we
actually
are
right,
we
have
to
remember
that
kettlebell
is
talking
to
kubernetes
over
the
api
and
the
api
is
written
in
json,
it's
a
json
api,
so
we
send
it
json
and
it
gives
us
json
and
when
we're
declaring
declaring
an
empty
slice,
we
should
always
prefer
the
var
keyword
instead
of
this
one
since
it's
empty
it
creates
and
then
slice
and
stuff
there's
less
memory
allocation
and
so
on
and
so
forth,
and
things
like
that.
C
So
in
this
case,
that
is
fine
now,
so
this
is
what
we
want
now.
What
I'm
curious
about
is
if
we
can
get
this
to
know
as
well
like.
Why
is
this
return?
Actually,
this
should
be
named
as
well.
Let
me
check.
C
Yeah,
I
was
wrong
here
and
these
are
like
normal
rabbit
holes.
I
end
up
going
down
to
when
doing
code
reviews
just
because
I'd
like
to
understand
the
problem
and
why
things
are
going
a
certain
direction.
Just
so
sometimes
it
helps
me
uncover
other
problems.
We
have
with
the
code
base
or
helps
me
find
an
issue
with
the
change
request,
so
this
should
be
near.
So
let
me
update.
C
C
So
let
me
do
that
quickly,
again,
I'm
showing
to
get
them.
So
it's
super
explicit
to
what
I'm
thinking
we
should
do
and
now
it's
up
to
the
contributor
to
say:
okay,
I'm
just
gonna
copy
paste,
the
code
or
I'm
just
implementing
something
differently,
because
I
can't
think
of
as
a
something
differently
right
and
that's
like
the
beautiful
beautiful
thing
about
core
review.
C
To
achieve
one
goal,
instead
of
like
hey,
I'm
telling
you
what
to
do
and
things
like
that,
so
it's
always
good
to
think
of
code
review
as
pairing
two
works
on
something
together
instead
of
like
I
did
the
work
now
you
review
the
work
and
I
go
back
to
my
corner
to.
A
C
So
I'll
add
this
to
the
review,
and
that
is
all
for
this
one.
So
what
I
like
to
do
is
also
run
manual.
Qa
right
and
I
like
to
document
what
I
run
as
a
manual
qa
one
as
steven
brought
ground
for
myself.
So
if
I
come
later
either
tomorrow
or
friday,
when
the
community
contributor
submitted
the
changes,
I
was
asking
for
or
suggested
I'll
come
back
here
copy
paste.
What
steps
I
ran
and
it
would
be
much
quicker
right,
so
no
services
to.
C
C
C
Okay,
I
will
not
write
the
manual
qa
just
because
it's
very
very
boring
to
see
me
type
on
screen
so
I'll
do
that
later
today,
myself.
C
C
So,
to
reiterate,
just
two
comments,
mostly
tests,
because
the
implementation
itself
looks
like
what
we
need
and
that's
pretty
much
it
for
this
one.
C
A
It
depends
on
whether
you
want
to
use.
We
have
10
minutes
left,
but
if
you
want
to
use
them
or
not
it's
up
to
you,
I
also
am
not
monitoring
the
guitar.
There
are
no
questions
there.
Neither
on
youtube.
C
On
we
will
see
that
we
have
this
one
from
fabio,
so
this
is
quite
quite
interesting.
So
previously
we
were
testing
some.
We
wanted
to
attest
about
like
long
characters
right
and
we
were
using
a
really
long
project
id
to
make
sure
that
is,
it
is
being
concatenated
properly.
C
Actually,
yeah,
it's
being
concatenated
properly
like
this
one
right.
But
if
we
look
at
this
issue,
this
task
is
actually
failing
on
32-bit
systems.
Now
we
do
support
32-bit,
but
we
do
not
run
our
ci
on
32-bit
systems
right
and
it's
causing
overflow
into
overflows,
because
this
number
is
too
big
for
32-bit
systems.
C
Luckily,
this
was
only
in
tests.
It
was
never
a
production
application,
so
it
was
still
running.
The
debian
folks
are
kind
enough
to
run
all
their
tasks
on
22-bit
and
64-bit
and
they
flag.
C
This
flag
did
for
us,
and
this
contribution
is
pretty
much
removing
the
test-
and
I
agree
with
this,
because
this
is
such
a
nut
case-
that
that
is
longer
than
63
characters,
project
id
as
the
id
of
the
project
inside
of
the
database
that
is
sent
to
us
and
it's
a
really
really
a
really,
really
short
chance,
a
small
chance
that
sorry,
that
was
a
translation,
english
translation
problem,
a
really
short
chance,
slight
chance
that
this
will
happen
right.
C
So
I
think
I'm
fine
removing
this
test
because
it
does
not
really
add
any
value.
So
I
think
I'm
just
gonna
merge
it
as
this.
C
C
C
And
we
have
just
basically
testing
the
project,
unique
name
right.
It's
just
making
sure
that
we
get
the
expected
value,
and
that
is
unique
for
that
specific
project.
C
So
and
let's
check
so
that
the
pipeline
is
failing.
So,
let's
see
if
that
is
related
to
this
change
or
not.
C
Now
this
one
is
a
flaky
pipeline,
so
I'm
not
sure
if
I
can
rebase
no,
I
cannot
replace
it.
So
what
I
will
ask
the
contributor
is
to
rebase
the
smart
request.
So
then
we
can
just
merge
it.
I
like
to
merge
something
in
one
that
has
a
green
pipeline.
So
if
you're
opening
up
a
community
contribution
like
this
would
be
one
of
your
first
chocolate
chat,
chocolate
checklist
right
make
sure
that
the
pipeline
is
coming
before
you
send
it
over
to
a
review.
C
C
C
It's
I
wouldn't
say
it's
a
breaking
change
for
production
or
anything
like
that,
but
this
is
still
something
we
really
really
wanted
to
do,
and
I
I
really
appreciate
people
just
spending
their
own
time
doing
this,
so
I
really
enjoy
reviewing
these
and
I'm
really
really
thankful
for
all
the
community
work
on
this
kind
of
stuff,
because
this
is
what
keep
what
makes
a
project
very
healthy,
teaming
with
talking
contact
dealing
with
these
small
educations,
so
we
fix
them
up
and
make
sure
everything
is
working
as
expected.
A
Thank
you.
I
have
a
question:
where
can
where
can
people
find
some
issues,
easy
issues
to
begin
with
or
yeah.
C
Yeah,
I
would
say
we
follow
the
same
methodology
as
the
main
gitlab
project.
So
if
I
share
my
screen,
I
don't
have
a
link
handy
to
what
the
official
guidelines
say
so
christmas.
You
might
be
able
to
find
that
but
like
if
you
look
at
our
issue
tracker
here
and
if
you
label
by.
C
Accepting
merchandise
I
would
say
most
of
them
are
accepting
merger
burst,
so
you
can
look
at
this
one
and
I'm
pretty
sure
we
also
have.
A
Yeah,
I
was
primarily
talking
about
the
gitlab
runner
project.
C
Yeah,
this
is
on
the
kidlaprunner
url,
so
we
have
our
own
issue
tracker.
Let
me
zoom
in
a
bit
more
sorry
about
that
under
the
kit
lebron
project-
and
these
are
all
our
issues
for
gridlock
runner,
perfect.
If
you
have
any
suggestions
or
ideas
or
things
you
want
to
improve
or
things
that
are
bothering
you
feel
free
to
open
an
issue.
You
can
ping
us
directly
my
username
as
steve
a.
A
C
Set
so
you
can
easily
ping
me
and
like
I'll,
either
direct
it
to
someone
else
or
we'll
discuss
it
together
on
like
if
this
issue
is
something
that
we
want
to
solve
or
not,
sometimes
we
get
merged
requests
without
an
issue,
and
that
is
completely
fine.
C
We
just
need
first,
we
need
to
discuss
on
the
problem
and
if
we
want
to
solve
the
problem
and
how
then,
how
we're
going
to
solve
it
and
if
we're
just
opening
up
a
merge
request
with
that,
that
is
somewhat
already
late
in
the
process,
but
it
is
still
completely
fine
with
us
that
sometimes
sometimes
just
showing
the
changes.
What
needs
to
be
done
to
express
what
needs
to
be
solved
right
so
take
it
case
by
case
basis,.
A
Thank
you.
Thank
you.
So
much.
I'm
gonna
put
that
link
on
the
hackathon
page
as
well.
With
the
gitlab
issue,
tracker
and
issues
accepting
we
have
a
master
issue
where
we
track
all
the
merge
requests,
and
we
also
have
some
easy
some
labeled
issues
to
begin
with,
for
people
so
make
sure
that
it's
surfaced
there
as
well.
A
Let
me
just
repeat
it
for
the
stream:
how
are
these
issues
found
test
case?
Removal
seems
like
something
that
would
remain
and
seems
difficult
for
a
user
to
motivate,
as
it
would
not
use
many
cables.
C
Yeah
so
the
first
part,
the
issue
was
found
by
the
w
community,
actually
so
debian
the
debian
project,
which
is
a
specific
flavor
of
linux.
Actually,
packages
gitlab
runner
for
us
and
they
run
their
tasks,
their
own
tasks
and
package,
gitlab
runner
in
their
own
way,
and
they
actually
run
their
ci.
So
they
run
our
tests
on
a
32-bit
system
and
that's
how
that
issue
is
found.
They
filed
an
issue
on
our
issue
tracker.
C
C
Removal
seems
like
something
that
would
remain
and
seem
difficult
for
a
user
to
motivate.
So
I'm
not
sure
I
understand
your
question,
but
what
I
think
you
are
saying
is
removing
test
cases
might
not
be
what
users
might
want
to
do
right,
and
that
is
completely
fine.
I
think
there
are
multiple
aspects
of
the
project
that
can
motivate
you
to
work.
Some
people
enjoy
fixing
the
tests.
Some
people
enjoy
adding
new
features.
Some
people
enjoy
updating
documentation.
So
I
think
we
have
everything
we
cover
every
aspect
that
you're
interested
in.
A
Thank
you
all.
Thank
you
all
for
participating.
Thank
you,
steve
hi
darren
as
well.
Thank
you
all
for
coming.
We've
already
updated
the
website
with
the
recording
in
case
that
people
want
to
see
it
retrospectively,
steve
any
last
words.
C
A
Thank
you
so
much
and
again,
if
you
have
any
any
wider
questions,
you
can
find
all
of
us
on
the
getter
channel
on
github,
so
jitters,
dot,
im,
slash,
gitlab,
slash
community,
so
feel
free
to
join
us
there.
You
can
find
all
the
information
information
on
their
hackathon
page
and
for
the
people
who
are
going
to
join
the
next
session.
The
release
stage
tutorial
that
is
coming
up
in
10
minutes,
see
you
soon
for
the
rest.
Happy
hacking.