►
From YouTube: GDK office hour June'2020
Description
Recording from the GDK office hour on June 16, 2020
B
B
No,
no,
that's!
Okay!
You
joined
us
in
perfect
time,
so
we
got
rajendra
and
Lee
on
the
call
just
northie
yeah,
just
one
over
the
agenda
and
what
we,
what
I'll
do
is
quickly
go
over
the
second
topic,
some
of
the
Docs
improvements
that
have
been
happening
over
the
past
several
weeks
and
then
that
we
can
go
back
talking
about
the
GDK
survey
and
actually
feel
free
to
add
your
thoughts
here.
I
mean
I.
Just
did
a
quick
query
on
documentation
related
at
Mars
over
the
past.
B
B
Mri
here
this
one
in
particular
way
he
did
a
lot
of
work,
restructuring
the
documentation
to
make
it
more
readable.
Just
quickly
show
you,
the
EMR
I
think
this
was
merged
like
a
few
weeks
ago,
but
I
mean
there
are
a
lot
of
changes
here
in
1mr.
But
you
know
not
just
a
readme
file
but
several
places
he
made
a
lot
of
great
updates
and
I
think
we're
slowly,
but
surely
we're
making
good
progress
in
terms
of
how
documentation
czar
I
mean
not
only
up-to-date,
but
you
know
structured
in
a
way.
B
C
Yeah
yeah
Evans
done
some
great
work,
he's
currently
the
the
technical
writer
for
the
GDK,
or
at
least
the
sort
of
official
one
we
are
having
a
new
technical
writer,
become
responsible
or
primarily
responsible
for
the
GDK
not-too-distant
future,
but
Evans
been
doing
awesome
job
keeping
on
top
of
everything
and
also
proactively
improving
things.
So
yeah
I
must
have
been
I
wanted
to
spend
a
bit
more
time
on
the
the
docs
than
I
was
able
to,
but
still
definitely
have.
You
know
a
lot
of
work
to
do
around
the
install
documentation.
C
So,
whilst
you
know
there
are
some
great
improvements
around
sort
of
the
how-to
section
which
you
know
includes
specific
topics
and
then
how
to
you
know
how
to
set
them
up
and
troubleshooting
and
things
like
that,
but
we
still
have
a
fairly.
You
know
big
task
around
improving
them
the
install.
So
it's
it's
currently
two
pages,
which
is
the
prepare
stage,
which
is
kind
of
installing
all
the
dependent
libraries
and
things
and
then
there's
the
set
up
the
JDK.
So
definitely
that's
that
should
be
the
next
yeah.
C
B
D
1001
and
then
there
was
one
again
I
think
it
was
Frank
that
helped
him
suggest
or
someone
that
suggested
that
there
was
a
little
where
there
was
references
to
to
go
version.
1.1
2,
as
well
as
1.1
for
so
I,
was
trying
to
sort
of
consolidate,
remove
some
of
those
references
really
its
yeah.
Let
me
see
if
it
hasn't
made.
D
A
D
A
C
A
a
challenging
one
to
have
to
have
documentation
and
you're
like
commands,
and
things
like
that
in
sync,
so
that
particular
one
I
remember
reviewing
it
and
yeah
it's
you
know.
We,
we
update
one
area
of
the
documentation
to
say
you
know
the
the
new
sort
of
minimum
go
version
is
one
by
14,
and
then
there
was
some
some
areas
that
we
left
behind.
Yeah
be
great.
E
C
Yeah
be
great,
it's
you
know,
I'm
experimenting
with
with
a
system
called
asdf
which
can
manage
dependencies
kind
of
separate
from
IBM
and
the
individual
tools,
for
example,
and
the
way
that
works
is
that
you
kind
of
check
in
a
file.
It's
called
tools
version
instead
of
like
IBM
version,
for
example,
and
you
can
have
multiple
sort
of
it's
a
software
and
the
versions
that
you
require,
so
we
might
be
able
to
if
that
works
and
in
the
ends
up
being
something
that's
suitable
for
both.
You
know,
Mac,
Linux
and
even
potentially
Windows.
C
We
could,
you
know,
have
that
checked
in
and
then
you
know,
maybe
we
do
have
some
options
in
the
documentation
to
kind
of
dynamically
bring
kind
of
logic
in
we're
not
were
not
take
advantage
of
it
currently,
because
the
main
doc
documents
are
in
markdown,
but
we
can
use
a
doc,
which
is
a
ski
doc,
and
you
can
say
well,
you
know,
instead
of
hard-coding
the
version
of
go
or
Ruby
or
whatever
in
the
docs.
You
say
to
pull
this.
C
D
I
must
admit
when
I've
managed
to
get
it
installed
on
Windows
10.
My
temptation
is
to
put
the
whole
guide.
You
know
exactly
step
by
step
what
I've
done
into
the
documentation
but
85%
of
its
probably
the
same
as
the
ubuntu
install
or
the
any
other
install
so
I,
don't
kind
of
want
to
duplicate.
That
I
mean
that
there's
even
more
to
to
maintain.
So
it's
a
tough
balance,
I
guess
yeah.
D
I
think
it
is
a
safer
feel
free
to
with
the
go
version.
One
just
I
would
get
me
to
pop
the
version
back
in
or
pop
it
back
in
yourself
and
get
it
man,
I
I
thought
I'd
rather
eat
arid,
then
installed
and
then
halfway
down
the
line,
you
get
an
error
that
you
don't
understand,
because
you've
got
the
wrong
version.
Yep.
D
B
A
B
I
mean
lots
of
work,
I
mean
obviously
to
be
done
like
you're,
saying
ash,
but
I
was
a
lot
of
contribution
both
from
the
team
members
and
the
community
members
of
the
fest
several
weeks.
So
getting
pinged
on
a
lot
of
em
are
sub,
but
I'm
not
complaining.
So
alright,
so
I
think
that's
I'll.
Add
some
notes
under
the
docs
improvements
under
the
agenda.
But
I'll
turn
things
back
over
to
you
and
if
you
want
to
tell
us
the
latest
on
where
things
are
with
the
survey.
C
Sure
and
yeah
so
that,
just
for
some
context
there
it
started
life
as
the
the
GDK
survey,
and
then
it
was
a
Google
form
and
then
it
sort
of
has
now
expanded
out
to
being
how
hell
does
you
know?
How
does
one
contribute
to
get
labs
are
not
being
GD,
not
asking
the
question
about.
You
know
how
you
use
the
GDK,
but
how
do
you
contribute
so
opening
it
up
widening
the
kind
of
question
and
now
it's
in
a
different
system?
C
So
it's
it's
dragged
on
a
bit.
I
will
say
it's.
It's
definitely
very
close
to
being
finished.
I
just
am
conscious
of
sending
out
something
that
doesn't
ask
the
right
questions,
but
it
definitely
asks
more
broader
questions
like
how
do
you
use
the
GDK?
Do
you
use
review
apps,
which
is
another
system
we
have,
that
is
very
automated
and
you
don't
need
to
clone
anything
locally
or
this
genus.
C
The
ek
the
get
lab
compose
kit,
which
is
another
project,
is
very,
very
docker
centric
and
just
trying
to
I
guess
get
a
better
sense
of
how
people
both
within
a
get
lab
and
also
the
wider
community.
How
people
are
using
these
various
tools
and
are
there
other
ones
that
we
don't
know
about,
and
one
of
the
pain
points.
What
are
the
good
parts?
Yeah
I
can
share
I'm
happy
to
share
a
little
bit.
There's
nothing
yeah
sort
of
I
think
to
not
show
I'll
just
bring
it
up
and
then
share.
E
C
That
by
a
little
bit-
but
it's
been
great-
we've
had
lots
of
at
this
stage
just
internal
feedback
upon
the
questions
and
been
you
know
really
trying
to
incorporate
a
lot
of
those,
and
there
are
some
you
know
so
requirements
around
the
types
of
questions
we
can't
ask
or
that
we
should
ask,
and
so
there
were
sort
of
contributing
to
some
of
the
bit
of
that
delay.
So
the
first
question
is
in
trying
to
get
an
understanding
about
the
the
role
in
which
you
know
the
person
filling
out.
C
C
E
C
Just
describing
a
role
team
member,
so
we
really
want
to
try
and
have
the
same
survey
for
every
what
everybody.
So
it's
it's
and
that's
presents
a
bit
of
a
challenge
and
trying
to
make
sure
that
all
the
different
permutations
of
people's
sort
of
demographic
and
and
how
they
operated
it
covered.
So
I'm
going
to
be.
E
C
If
we
can
easily
go
back,
which
was
a
bit
of
a
problem,
I
don't
know,
I
haven't
purposely
left
that
off,
but
yeah.
It
can't
seem
to
go
back,
but
I
think
this
page
here
is
very
much
similar
for
the
JDK
gck
or
any
other
kind
of
local
type
development
environment,
so
operating
system.
How
much
RAM
reason
for
that
is
you're
trying
to
better
understanding
about
is
the.
C
C
Apologies
yeah
true
I
whip
through
this
and
then
we'll
get
to
that,
and
maybe
some
some
hope
for
how
that
might
be
improved
in
the
future.
Yes,
asdf
is
interesting.
It's
it
can
offer
some
other
benefits
that
we
might
realize
in
the
future,
but
typically
most
people
I
think
are
being
for
our
VM.
But
in
this
case
you
choose
multiple.
There's,
no
reason
why
you
couldn't.
How
do
you
manage
node
I?
C
Think
if
something
we
use
homebrew
or
depending
on
the
state
of
the
package
manager,
it
could
be
fairly
well
behind
or
but
a
lot
of
people
use
node
in
and
then
agreed
around
I'm
going
to
be
very
biased
here,
I'm
very
happy
with
everything,
clearly
not
reliability.
Let's
have
that
as
somewhat
dissatisfied,
because
that's
probably
a
fair,
fair
judgments
at
this
stage
and
yeah.
This
is
another
interesting
in
silence,
this
Qualtrics
tool.
It
makes
suggestions
on
how
accessible
the
forum
is.
C
How
likely
you
know
people
are
to
choose
various
answer,
various
questions
and
things,
and
this
is
one
that
flagged
as
being
not
a
very
usable
question,
even
though
it
offers
it
as
a
kind
of
it's
a
ranking
question.
So
how
would
you
rank
in
order
of
things
that
could
be
improved
so
installing
you
know,
which
is
in
the
time
making
it
more
reliable,
might
sort
of
dragging
them
into
position.
C
So
it's
it's
I,
think
the
there
is
value
and
having
this
sort
of
auto
ranking,
but
the
way
the
the
tool
implements
is
is
a
bit
wonky,
but
we'll
leave
it
at
that.
Some
other
information
there
you
can
offer
and
that's
the
end
for
the
GDK
and
the
jck
similar
asking
similar
types
questions,
but
there's
a
bit
of
a
more
heavier
sort
of
docker
perspective.
C
D
C
E
D
Sorry,
you
get
I
think
we
really
want
to
know
who's
using
vagrant
and
also
I
suspect
that
there's
a
reasonable
percentage
who
are
using
VMs
of
some
sort,
whether
it
be
VMware
or
VirtualBox,
or
you
know,
KVM.
There's
there's
a
lot
of
tools
like
that.
So
I
don't
know
how
easy
it
would
be
to
ask
that,
but
I
think
I'd
be
interested
to
know
like
okay.
What's
your
what's
your
actual
native
operating
system,
you're
you're
running
and
then
are
you
running
GDK
on
that
or
or
not
necessarily
GDK
gck?
C
That's
a
great
point
yeah.
So
in
all
of
these
you
could
run
the
GDK,
the
gck
and
like
a
vm,
especially
for
windows
or
necessary
Dockers,
pretty
pretty
reasonable
on
Windows
these
days.
Both
of
these,
you
could
run.
Excuse
me
in
a
VM,
but
a
very
good
one
is
interesting,
because
again
you
could
run
that
in
a
VM.
Do
we
break
it
out
at
this
point
to
say
it
really
needs
to
be
a
question
within
I,
think
deeper
inside,
say:
yeah
the
JDK
yeah.
A
C
D
D
C
And
yeah,
with
some
of
the
most
of
the
questions
being
optional,
it's
it's
trying
I
mean
the
rationale
behind
that
is
to
try
and
improve
people
filling
out
the
form,
but
it
also
means
that
we
may
get
a
lot
of
incomplete
data,
but
that's
I
think
the
trade-off.
We
want
people
to
to
not
feel
like
they
have
to
answer
a
question
and
and
be
blocked
and
kind
of
walk
away,
but
just
take
it
take
any
sort
of
any
kind
of
input
we
hope
we
can
get.
So
that's
a
great
suggestion.
We
thank
you.
I'll.
D
C
Your
asset
for
Windows-
it
definitely
is
for
Mac
and
Linux.
You
know
these
sort
of
you
lean
very
heavily
on
the
native
side,
because,
through
there
are
a
lot
more
tools
out
there,
but
yeah
for
Windows
you're.
Exactly
right,
we
could.
There
are
a
lot
of
different
methods,
and
probably
the
native
would
be
the
least
of
the
methods
of
people
using.
B
No
I'm,
sorry
yeah
I,
don't
know
if
this
is
gonna
help
like
coz
here
when
we
say
Mac,
Windows
and
Linux,
because
I
was
assuming
these
are
all
like.
I
was
assuming
these
are
all
just
native
OS.
That
I
was
assuming
and
then,
if
you're
running
a
be
running
on
a
VM
of
some
sort,
likely
saying
I,
wonder
if
that
goes
under
other
I.
Don't
know
if
that
simplifies
things
in
terms
of
the
structuring,
the
survey
or.
C
B
C
B
C
B
When
you
said,
like
I,
mean
I
think
it
makes
sense
to
try
this
out
like
what
limited
people
to
get
lucky
initial
feedback
on
the
survey
like.
Are
you?
Were
you
just
thinking
like
get?
Let
team
members
only
or
like
we
should
be
open
to,
including
some
like
select
a
lot
of
community
members,
because
I'm
concerned
that,
like
we
get
it
like
a
skewed
point
of
view,
just
for
the
other
team
members,
but
yeah.
C
A
B
B
C
Yeah,
so
the
Ruby
upgrade
was
a
good
example
of
how,
when
dependency
changes
are
made
kind
of
outside
of
the
the
workflow
or
the
sort
of
outside
of
JDK,
because
the
currently
just
for
some
context
and
apologies.
If
everyone
knows
that
the
decays
Ruby
version
when
you,
when
you
install
it
a
fresh
bouquet
by
a
GDK
in
it
or
you
clone
the
repository,
there
isn't
actually
a
ruby
version
as
such.
At
that
point
in
time.
C
What
happens
is
it
is
brought
in
at
symbolically
linked
as
part
of
the
the
install
phase,
and
it
takes
the
Ruby
version
that
is
currently
residing
inside
the
get
lab
the
main
get
lab
project
and
symlinks
30,
and
so
so
what
happened
was
the
ruby
version
was
bumped
to
266
and
it
happens
happen
to
65,
and
it
will
probably
happen
with
267.
If
we're
not
quick
enough
about
resolving
this,
is
that
the
dependency
upgraded,
sorry
updated
without
the
GDK
being
updated.
So
it
was
an
implicit
dependency.
C
I
think
it's
important
to
note
that
it's
it
is
important
to
keep
evolving
with
the
Ruby
versions
so
that
the
GDK
or
the
the
the
environment
that
the
GDK
is
running
in
is
as
close
as
possible
to
how
the
stable
versions
of
get
lab
deployed
so
not
just
to
get
lab
calm.
But
you
know
the
latest
stable,
like
13
zero,
for
example,
I,
believe
that's
still
to
65,
but
yeah.
It's
important
to
be
as
close
as
possible
development
wise
with
the
production
versions,
possibly
a
little
a
little
bit
ahead,
but
yeah.
C
So
we,
it
happened
pretty
quickly
without
much
ability
for
us
to
where
we
do.
We
currently
don't
have
a
facility
to
other
than
using
the
forums
and
the
Godot
groups
are
the
Gillard
channels
to
advise.
You
know
that
there
has
been
a
a
dependency
in
this
case.
It
dependency
upgrade,
but
I
think
it
still
would
have
been
a
little
too
late
at
that
point,
so
to
sort
of
close
the
loop
on
it
a
little
bit,
maybe
I
would
just
share
my
screen,
so
we
can.
C
C
E
E
E
D
That
issue,
but
remind
me,
was,
were
you
thinking
of
that
being
sort
of
a
main,
a
manual
process
but
sort
of
you
guys
or
the
community
to
to
sort
of
add
these
steps
in
to
say?
Oh,
if
you're
you're
going
from
this
veg
here,
are
there
sorry
nothing
I
broke
up
a
bit
there.
That's
really
I
got
the
gist,
be
go
so
him
yeah.
Was
it
gonna,
be
a
manual
process
or
you
hope,
into
some
magical
way
to
identify
when
versions
are
changing
and
dependent
season.
C
If
we
know
we're
going
to
bump
the
version
in
the
future,
we
can
offer
steps
to
get
to
sort
of
prepare
because
you
can
install
a
new
version
of
Ruby
and
not
make
it
the
default
and
prepare
it
so
that
when
the
version
is
bumped,
it's
already
ready,
but
I
think
I'd
prefer
to
have
as
part
of
the
Judi
ki.
We
either.
C
You
know,
offer
the
heads-up
just
informational
and
then
say
that
any
Ruby
bump
here
you
know
press
enter
or
do
wish
to
upgrade
your
Ruby
bit
of
a
it's,
probably
not
really
an
option
to
say
no,
because
that
will
break
them
through
the
GDK,
but
yeah
that
at
this
stage,
we're
looking
to
automate
automated
as
much
as
possible
and
that's
where
the
I've
got
the
bridge
here.
But
the.
D
E
C
Request,
but
he
had
this
tool
version
versions
file
and
you
nominate
all
the
different
versions
and
I
don't
have
this
bridge,
but
the
idea
is
that
and
this
this
major
quest
goes
a
little
bit
further
in
trying
to
keep
the
asdf
install
relative
to
the
JDK,
because
part
of
the
problem
we
have
here
is
that
Ruby
upgrades
and
Ruby
versions
and
things
sort
of
install
at
a
global
level,
and
so
we've
got.
We
need
to
be
careful
in
how
we
kind
of
automatically
upgrade
rubies
for
people
and
things
like
that.
C
The
branch
locally
because
I
can
show
you
that
it
will
install
all
the
like
Ruby
go
lang
node
all
of
these
things.
It
installs
that
sitting
under
the
GDK
in
the
dot
asdf
directory.
So
it
means
all
the
dependencies
are
self-contained
within
that
GDK
they're
not
installed
like
a
new,
a
local
or
they're,
completely
kind
of
contained.
So
it
gives
us
greater
control.
Okay,
so
it
gives
the
GDK
greater
control
and
greater
certainty
around
you
know.
If
the
versions
of
Ruby
you're
upgraded,
the
versions
of
golang
are
upgraded.
C
We
can
be
fairly
confident
that
we're
not
going
to
impact
other
things.
It's
just
going
to
apply
to
that
that
Judi
case
so
yeah,
it's
working,
I,
don't
I'm
sort
of
I'm
a
bit
uncertain
about
how
to
proceed
with
this
because
yeah
we
don't
I,
don't
want
to
be.
You
know
to
say
this
is
the
only
way
you
can
install
all
these
things,
but
it
would
make
life
a
bit
easier.
You
know
if
we
say
this
is
the
recommended
way,
because
asdf
from
what
I
understand
is
is
cross-platform-
and
you
know
so.
C
You
can
offer
automation
of
these
installs,
which
we
still
had
the
same.
You
know
problem
of
managing
the
version,
so
it's
just
substituting
the
Ruby
version
for
a
tool
version.
But
if
I
can
get
this
branch,
you
simply
run
asdf
install
and
that
is
don't
think
yeah.
It
just
goes
and
if
it's
a,
if
it
has
everything,
installed,
no
op
and
just
continues
on
so
we
could
simply
run
this
command
after
GDK
update
and
that
would
go
and
install
those
versions.
And
it's
a
do
it
automatically.
C
So
yeah
and
it's
not
just
a
really
problem-
it's
it's
a
you
know,
version
issue
that,
although,
in
the
case
of
Ruby,
it
is
specific
that
we
had
that
sim
link,
but
you
know
with
the
the
problem
would
exist
with
node
if
we
bump
the
required
version,
but
don't
bump
through
the
necessary
files
correctly.
I
think
that
would
exhibit
the
same
same
issues
but
I
like
the
idea
of
this,
the
single
file,
it
has
all
the
dependencies,
and
this
is
what
I
was
alluding
to
earlier.
C
You
know
we
could
draw
this
this
file
into
the
documentation
and
say
here
are
the
versions
and
there
you
know
we
don't
have
to
repeat
them.
We
just
know
that
these
are
the
versions
we
we
want
yeah.
So
it's
looking
promising
sort
of
I
don't
to
be
that
person
who
would
use
another
system
for
doing
things,
but
I
think
it
does
bring
a
lot
of
benefit
and
I'm
not
only
sort
of
including
the
versions
file
here,
but.
C
Niceties
around
bootstrapping,
so
I'm
experimenting
with
doing
a
lot
of
this
stuff
that
it's
sort
of
part
of
the
documentation
really
like
installing
gems
and
having
it
just
as
much
more
automated
so
that
it's
a
bit
of
an
easier
sell
to
say
here
is
a
new
system
called
SDF?
Yes,
I'm!
Sorry,
it's
another
one,
but
it
will
make
things
easier
because
it
will
be
a
protected
install
of
all
your
system,
languages
and
things-
and
you
know,
it'll
be
hopefully
easier
to
upgrade
going
forward.
Fingers
crossed
and.
D
C
E
C
With
with
Linux,
there
are
just
some
system,
library,
types
of
things
and
those
those
will
be
susceptible.
You
know,
if
they're
upgrade
it
outside
of
the
you
know
the
sort
of
flow
of
SDF
or
or
BN
for
whatever.
So
that's
when
things
like
JDK
doctor
try
and
step
in
and
offer,
you
know
solutions
and
at
least
acknowledge
or
a
detect
known
issues
which
yeah
there's
some
there's
some
good
discussion
around.
C
C
You
know
standard
way
of
doing
things,
and
you
know
you
can
you
could
do
it
with
our
Bienville
go
your
own
way,
but
this
sort
of
recommended
way
should
be
a
few
fewer
steps
and
you
know
we'll
be
able
to
better
support.
It
I
think,
but
we'll
still
continue
to
support
the
other
methods
like
having
a
ruby
version
file,
checked
in
etc,
conscious,
I'm
talking
a
lot
sorry.
So,
if
ya
feel
free
to
do,
yell
ask
questions.
C
E
C
D
E
C
So
that's
there's
a
few
of
these
working
progress.
Mode
requests
happening
to
try
and
yeah.
Probably
just
should
focus
on
this
one,
because
without
this
one
here,
if,
if
there's
a
bump
to
267,
for
example,
this
will
this
will
bite
again
and
I.
Think
you
know
there's
a
lot
of.
We
have
a
GDK
channel
and
slack
and
yeah
really
really
common
problem
for
people,
and
it
was
quite
hard
to
watch
because
it's
it's
really
hard,
seeing
people
being
blocked
and
disrupted
it
not
just
get
a
lot
of
people,
but
also
in
the
community
engineers.
C
C
We
merged,
maybe
put
on
the
next
next
term,
made
ups
agenda
around.
There
was
another
similar
one
to
this
one,
around
kind
of
an
interactive
and
sort
of
approach
on
more
on
the
installed
side.
So
asking
questions
at
install
time
and
instead
of
you
know,
running
GDK,
install
and
saying
some
things
are
missing
and
trying
to
be
a
bit
more
helpful.
But
maybe
that's
for
next
time.
C
Yeah
I
mean
that's
that's
good
to
hear,
but
yeah.
We
definitely
we
need
to
improve
our
communication.
I
just
I'm
not
sure
how
to
go
about
adding
this,
but
I
think
what,
in
hindsight,
what
should
have
happened
from
the
GDK
side
of
things
is.
We
should
have
read
I
believe
I
raised
an
issue
to
deal
with
it,
but
it
probably
should
have
raised
an
issue
and
tagged
at
p1.
C
Then
we
should
have
a
process
in
place
where
any
issues
tagged
and
labeled
as
p1
should
be
communicated
both
to
the
GDK
slack
channel
and
to
the
git
of
rooms
and
on
the
forum,
even
though
you
know
it's
possible
to
subscribe
to.
You
know
p1
issues
as
they're
created
so
for
the
GDK,
but
I
think
that
we
should
have
a
process
that
at
least
improves
the
communication
around
when
these
things
are
happening
because
yeah
that
can
be
can
be
missed
and
I.
C
D
C
Another
one:
that's
it's
possible
to
disrupt
is
the
moving
to
post
group
Postgres,
newer
versions
like
12,
for
example,
I
think
it
came
up
because
the
latest
have
one
too
stable
like.
If
you
just
do
the
docker
run,
one
tune
didn't
specify.
The
latest
is
20.
I
could
be
wrong,
but
the
default
Postgres
that
comes
with
that
platform
or
sorry.
C
We
need
to
be
mindful
of
communicating
that
one
so
yeah
I
think
I'll
put
together
a
credit
issue
and
I'll
see
you
all
on
it
and
get
some
feedback
around.
You
know
creating
a
process
for
communicating
these
types
of
things
in
the
future.
To
make
sure
we
at
least
the
messages
is
sent
as
wide
as
we
can
just
as
a
first
first
up.
D
D
What
it
was
so
the
different
various
default
egrant
file
for
was
been.
We
was,
it
had
been
two
fourteen
or
sixteen
and
running
Postgres,
maybe
nine
or
ten,
and
that
you
know
it
come
to
a
GD
cap
GDK
out
they
and
it
it
was
failing
and
looking
into
the
command
that
was
failing.
It
was
a
migration
script
and
then
you
know,
Google
was
telling
me
that
that
command
is
only
supported
by
a
version
10
or
11.
So
hopefully
that's
always
opening
or
anyone
yeah.
C
C
So
they
are
completely
two
completely
different
systems,
and
so
there's
a
real
disconnect
between
you
know,
say
in
thirty-one
we
generally
wouldn't
deprecated
or
make
something
obsolete
in
a
in
a
minor
release
but
say
fourteen,
for
example,
we
might
deprecated
support
for,
say
Postgres
ten.
That
would
require
sort
of
special
changes
to
the
jdk
to
have
that
reflective
reflected
there.
So
there
is
a
disconnect
I
think
we
could.
We
really
do
need
to.
C
D
It's
primarily
VI
each
of
the
the
vagrant
file.
To
be
honest,
I
mean
this
I
can't
remember
if
it
is
using
a
bin
to
14
or
16,
but
considering
when
L
120
I
think
that
that
needs
bumping
and
that's
the
same.
You
know
the
fact
that
that
image
doesn't
natively
support,
go
one
point
one
four
and
God
knows
what
other
issues
there
are
with
it
now.