►
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
A
B
A
Yeah,
this
is
all
to
make
it
like
easier
to
triage
issues
right.
So
what
we
are
seeing
a
lot
is
that
when
people
are
opening
issues-
and
we
get
like
one
lower
Vlogs-
and
these
things
are
always
missing,
so
we
have
to
go
ask
if
they
want
to
add
these
things
or
get
these
logs.
So
this
is
a
a
way
for
us
to
try
to
automate
getting
these
logs.
A
So
these
are
different
branches,
then
this
is
main.
This
is.
A
A
B
B
The
whole
crappy
thing
you
know:
I
worked
on
that
package
thing
that
we
go
from
sharp
one
to
shot
256
and
then
you
have
Xiao
one
and
then
within
quote
shot
256
and
then
do
the.
Maybe
that's
what
he's?
Maybe
that's
what
he's
saying
foreign.
D
A
B
D
A
B
Because
we
now
we
have
when
we
have
the
attribute
Char
one
we
put
in
there
shot
256
colon
the
hash,
yeah
yeah
I
understand,
instead
of
only
of
the
hash
and
that's
because
of
we
hard-coded
Xiao
one
so
much
everywhere
that
this
was
the
only
way
out.
A
B
A
D
B
D
A
Okay,
so
we're
gonna
keep
this
around.
D
B
A
A
A
Yeah,
so
this
is
the
CLI
part,
but
I
thought
that
we
already
approved
a
PR
or
was
this:
maybe
it
came
in
last
time
and
it
was
not
approved
yet
now
of
the
approvals.
D
C
B
A
D
A
A
B
A
Just
interested
in
knowing
why
that's?
What's
there
did
you
assign
reviewers
here?
Oh
you
have
to
leave
yours
out.
A
A
B
C
B
But
if
you
check
ABS
block
devices,
you
can
Define
the
type,
but
the
strange.
E
B
B
Like
in
the
go
mode,
it
seems
like
we're
using
rather
new.
B
A
Think
we're
running
like
yeah
we're
Auto
bumping,
but
we
also
Auto
publishing.
B
B
Do
a
go,
run,
Main
and
then
we
with
some
small
configuration
and
then
it's
done
so
I
thought
yeah.
Maybe
you
a
person
who
has
more
knowledge
of
this
code
base.
You
can
take
a
look
but
yeah
I.
B
A
A
A
A
E
Hello,
hello,
yeah,
so
we
invested
more
on
this
issue,
and
so
what
we
first
did
is
commit
by
commit
create
the
dev
release
to
check
which
commits
leads
to
that
issue,
and
we
find
the
committee
and
see
new
feature
which
rotates
the
Nets
credential
on
net
certificates
in
every
create
VM
step
or
update
VM
instance
step.
E
And
then
we
also
did
some
deep
dive
into
the
code
base.
Then
we
find
so
actually
the
rotation
of
the
certificates
lead
to
that
issue
and
refunds.
When
logic
is
so
there's
logic
to
rotate
the
password
and
also
configure
the
new
column
in
the
database,
so
indicates
whether
the
VM
should
use
the
new
feature
or
not.
But
the
configuration
is
not
quite
incident
with
the
to
say
the
the
database
content.
So
I
also
wrote
it
in
the
response
and
thank
you
be
home
to
review.
D
C
I
think
that
we
decide
somehow,
at
the
end
of
the
peer
to
invert
the
default
value
of
the
feature.
Okay
and
that's
why
it
is
so
so
in
the
table,
says
permanent
nuts
credentials.
C
E
E
B
Then
it
cannot
have
a
proper
communication.
E
I
do
not
know
so
because
I'm
not
familiar
with
the
push
and
push
agent
communication
code
part.
So
my
assumption
is
so
when
the
agent
rotates
the
certificate,
it
cannot
immediately
connect
to
the
watch
director,
because
what
I
see
for
the
next
configuration
honestly
Bosch
direct
side
is.
It
first
removes
the
old
instance
certificates
or
yeah
and
then
adds
a
new
instance
certificate.
So
I
can
the
file
lens
first
go
smaller
and
then
grow
bigger,
so
there
might
be
attempts
loads
at
this.
Agent
cannot
communicate
with
the
director
and
the
director.
E
A
Yeah,
so
what
what
I
can
imagine
happening
is
maybe
that
I
don't
know
if
that's
the
case,
but
so
a
new
instance
comes
up
with
a
new
disk
and
then,
while
still
bootstrapping
and
interacting
with
these
discs,
the
rotate
couldn't
or
the
new
Mass
credentials
come
in
right.
So
these
get
applied
and
then
the
agents
got
restarted,
but
it
was
maybe
halfway
through
some
process
or.
A
A
B
Well,
when
so,
when
he
comments
out
one
specific
part
of
that
PR,
then
it
all
works
and
it
has
specific
to
do
with
the
update.
E
A
A
A
Or
no,
that
that
should
be
a
Nets
method.
That's
message!
So
there
should
be
a
message
coming
from
from
the
director
to
go.
E
A
That
the
the
agent
will
restart
so
it
will
get
the
new
credentials
that
it
will
restart
itself.
Then
it
will
connect
and
but
and
then
it
will
get
the
message
to
start
migrating.
The
disks
okay.
A
So
I
have
based
on
the
the
reports
you
submitted
here
or
the
additional
information
you
supported
yesterday,
I've
created
in
a
story
in
our
backlog
to
look
at
this,
because
this
proves
at
least
that
this
really
relates
to
this
feature
so
that
work
will
start
beginning
next
week.
Hopefully,
okay,
thanks
but
yeah.
In
the
meantime,
it's
good
too
and
you
you
should
be
unblocked
right,
I
assume
you.
You
all
have
just
like
disabled
this
feature
for
now
and
no.
E
We
stay
on
the
old
version
because
so
and
we
also
want
to
upgrade
to
the
new
version
and
disable
the
new
feature,
which
is
also
acceptable,
because,
where
I
read
through
the
pr
I
think
see
first,
we
need
to
figure
out
whether
the
the
the
parameter
in
the
database
table
and
the
data
from
outside
from
the
config
should
be
two
different
Boolean
or
they
should
stay
the
same
Boolean,
because
that
Parts
also
confused
me
a
lot
yeah.
E
A
Yeah
I
I
have
nothing
more
to
add.
I.
Think
like
I
I
would
I
suspect,
there's
something
in
the
bootstrapping
code,
but
I
don't
see
it
right
now,
but
what
you
would
be
looking
for
is
finding
a
place
where
it
does
something
in
a
like
a
go
routine
or
something
like
something
asynchronous
that's
happening.
While
another
thing
like
there
must
be
a
race
condition
like
yeah.
That's
causing
this.
So
something
is
still
processing.
A
Then
the
agent
is
restarted,
so
it
doesn't
like
it's
still
in
that,
like
unfinished
State,
while
the
agent
gets
restarted
and
then
it
gets
the
message
I
think
it's
something
like
that:
okay,
so.
B
A
B
B
And
step
sap
is
using
Azure,
it's
working
perfectly
fine,
but
the
only
thing
I
don't
think
they're
doing
is
compilation.
It's
like
export
release.
B
They
have
like,
like
two
four
seven
one
SD
agent
and
then
you.
B
Also
something
with
the
disc,
it
could
be
the
new
what,
but
with
the
new
director,
it's
also
with
bionic.
So.
C
D
D
B
Instead,
my
first,
it
wasn't
like
how
how
would
Azure
agent
is
using
it,
but
in
Germany
we're
not
using
Azure
agent
anymore,
we're
switching
over
to
cloud
in
it.
So.
B
The
only
thing
is
that
big,
your
big
case
of,
of
course,
but
that's
the
only
thing
I
could
maybe
where
it
would
something
would
end
up.
D
C
A
C
Maybe
we
can
ask
to
find
the
exact
version
where
it
breaks
yeah
so
that
we
can
feel
like
we
don't
yeah.
C
Because
it
works
for
us,
we
don't
sap,
at
least
which.
A
E
This
is
a
dumb
block
for
the
database
migration
code
because
we
have
one
question
so
if
if
if
there
is
a
down
Block
in
the
database
migration
code,
but
in
the
old
version,
the
old
version
does
not
contain
that
that
have
database
migration
code
right
where
it
works
in
some
kind
of
like
stopping
or
post
stop
process,
or
it
will
fail
again.
That's
what
we
are
not
sure.
E
So
e,
if,
if
I
add
the
down,
do
and
block
here,
but
the
file
does
not
is
not
included
in
the
old
version
right.
So,
if
I
downgrade
the
Bosch
release
from
an
upper
version
to
a
lower
version,
the
file
is
not
there.
Will
it
still
executes
the
down
block
or
it
will
still
complain?
The
file
is
not
there.
A
E
Okay,
so
the
database
migrate,
so
it
will
detect
how
I'm
doing
and
downgrade
then
it
will
search
in
this
file
whether
there
is
a
down
block.
If,
yes,
it
will
exclude
it
into
database
and
then
recreates
the
VM
with
CO2,
which
okay,
because
yeah.
B
A
E
And
if
I
do
it
in
this
way
should
I
also
add
one
query:
something
like
deletes
the
migrated
file
in
the
schema
migration
table,
something
like
that
because
as
far
as
I
don't
know,
if
there
is
such
kind
of
file,
it
will
also
be
added
into
the
schema
migration
table
right
in
close
friends.
A
A
Yeah
I
understand
I
mean
like
that's
a
bit
of
the
I,
think
this
time
slot
was
chosen,
because
this
is
the
this
allows.
People
from
the
US
to
join
and
I
think
we
want
to
keep
that
that
option
like.
D
A
It's
not
often
but,
for
example,
Benjamin
sometimes
joins
who's,
doing
the
syslog
stuff,
so
yeah
I
I,
don't
think
it's
ideal
to
change
it
to
earlier,
because
that's
not
really
nice
for
our
U.S
colleagues.
D
A
I
think
you
missed
the
the
people
in
San
Francisco,
then
right
like
that
it
would
be
too
early
for
them.
Okay,.
D
A
By
I'm
time
zone
math.