►
From YouTube: Magento MSI Open Demo. February 1, 2019
Description
Agenda:
1. Fix DB Backup/Rollback issue by @Stepan Furman / @iminiailo
2. Pre selection for SSA if there is only one source provided by @joshcarter
3. Localization update and Search by ZIP codes by @max
3.1 Interesting thread on MSI GitHub about the mutability of Product SKU by @iminiailo
4. Source Level Reservations extension by @Paul Hachmang
5. Update on Quality and Automated Test coverage by @Tom Erskine
A
A
Let's
follow
the
agenda
and
proceed
with
updates
I
shared
several
several
minutes
ago
in
the
metallic
channels.
So
they
let
me
share
the
screen
and
let
me
describe
you
pretty
interesting
issue
and
step
on
woman
started
to
work
on
this
issue
and
it's
not
yet
finished
so
step
on
going
to
to
finish
the
pull
request
and
create
this
pull
request
to
magenta,
actually
not
to
MSI,
because
this
is
not
really
a
Masai
issue.
But
MSI
makes
this
issue
happen
and
the
issue
is
you
producible?
A
The
next
way,
so
merchants
can't
actually
make
the
database
backup
and
after
that
restores
the
database
fears
that
become
because
and
actually,
if
you
see,
step
to
reproduce
and
the
actual
result.
So
the
raw,
my
sequel
errors
happening
at
the
time
of
the
at
the
time
and
the
when
the
guy
is
trying
to
restore
the
database
from
the
cup
and
the
main
reason
for
that
that
currently
magenta,
magenta,
backup
and
magenta
restore
system
actually
does
not
does
not
differentiate.
Anyhow
base
tables
out
of
my
sequel
views
and
taking
attack
on
that
before
MSI
in
magenta.
A
A
We
made
the
the
data
extraction
and
the
schema
schema
instruction
and
the
data
extraction
afterwards
and
after
that,
so
we
sort
of
that
to
file
and
after
that
we
re
restored
that,
but
taking
into
account
that,
in
the
scope
of
in
the
scope
of
magenta,
ms
I've
introduced
my
sequel
view,
and
in
our
case
so
my
sequel
view.
You
know
like
the
root
of
all
evils.
Currently
in
Emma
sighs.
A
This
is
my
secret
view
and
as
a
good
news
that
it
will
gone
as
soon
as
you
provide
support
for
bundle
product,
and
we
will
know
no
longer
need
to
make
this
synchronization
between
the
previous
previous
implementation
of
Hana
science,
so
that
till
we
have
it.
Now
we
have
this
my
sequel
view
for
default
stock,
so
default
stock
currently
represented
as
a
joint
between
a
catalog
product
entity
table
and.
A
A
A
Magenta
to
the
tree,
and
hopefully
the
six
will
be
delivery
to
to
the
3.1.
But
surely
so
this
fix
will
provide,
will
extend
the
possibilities
of
magenta,
backup
and
restore
utilities
and
will
provide
them
possibility
to
handle
view
because,
in
case
of
you
with
no
need
to
store
the
data,
you
just
need
to
to
store
the
schema
of
you.
So
the
representation
of
this
you,
because
in
Mexico
there
is
no
materialized
view.
All
the
view
supported
by
my
sequel,
our
virtual
view,
which
are
represented
by
particular
SQL,
join
query.
A
A
The
big
interesting
issue
to
face
with
so
now.
Let's
proceed
to
another
update
app,
so
I
hope
that
Stepan
will
join
us
next
week
and
he
will
provide
an
update
who
make
the
particular
Dima
how
he's
backing
up
his
database
and
how
he
is
restoring
the
database
from
the
neck
up.
So
now,
let's
proceed
to
agenda.
A
B
B
B
That's
why
only
26
out
of
40
or
41
MSI
modules
are
updated
as
part
of
this
task,
I
thought
that
I
didn't
have
a
tool.
I
would
say
to
to
go
through
this
modules,
MSI
models
and
find
this
phrases.
This
is
why
I
built
a
simple
bar
screen
and
I'm
going
to
share
with
all
of
you
guys.
Maybe
it
would
be
handy
for
your
work.
Basically
what
it
does
it
goes.
You
specify
a
pattern
like
in
my
case.
It
was
invent
a
pattern
or
like
module
name
pattern
and
based
on
you,
enter
a
module
name.
B
I
collected
all
modules
and
in
this
modules,
I
created
the
script
created
new
directory
called
high
18m
and
collected
all
phrases
with
bean
magenta
i18
and
collect
phrases,
command,
created
file
and
placed
all
this
phrases
into
a
file.
So
basically
it's
a
simple
one
line
command
which
goes
through
all
modules
and
collects
files
and
read
so
all
these
files
we
can.
We
can
use
it
like
for
all
Magento
turmoils
and
simply
update
policy
even
can
be
automated.
So
this
is
a
first
task.
B
It's
just
the
files
and
second
one
I
I
would
say
started
working
on
its.
This
is
an
issue
called
provide
bicycle
queries,
however,
as
part
of
this
task
I'm
going
to
create
an
API
which
will
allow
to
search,
calculate
search
and
provide
buy
back
via
API,
a
list
of
nearby
zip
codes
or
its
addresses
based
on
zip
code
provided
in
a
search
field.
B
This
is
going
to
be
part
of
store,
pickup
functionality
and,
yes,
all
checkout
functionality
and,
as
you
can
see
in
one
in
a
previous
demo,
we've
seen
how
this
functionality
kind
of
work
in
progress
and
I
am
going
to
join
this
sexuality
and
implemented.
Irish
will
allotted
a
list
of
nearby
addresses,
so
this
is
work
in
progress
and
I'm
going
to
show
you
some
codes
in
the
next
demo.
A
Cinco
marks
the
last
service
which
you
mention
is
especially
interesting
for
our
for
our
topic
of
functionality.
Good
is
probably
like
the
interesting
part.
How
will
you
know
all
the
nearby
zip
code
addresses
so
keep
us
keep
us
posted
about
this
update
and
if
you
need
any
any
technical
assistance
or
trust
emotional
assistance.
Just
let
me
know.
A
A
So
this
is
item
devoted
to
the
product,
sq
mutability,
and
it
is
pretty
interesting
because,
like
we
already
spent
some
time
to
discuss
this
issue
several
months
ago,
and
that's
that
time
like
we
agreed
that
probably
from
the
product
perspective,
there
is
no
any
reason
to
modify
that
product
SQ
and
currently
that
that
that
SQ
is
modifiable
in
in
Magento
admin
panel.
For
example,
we
can
consider
this
is
just
a
small
gap
and
like,
and
ideally
the
SQ
should
not
be
modified
during
the
life
cycles
of
product.
A
So
we
have
to
change
all
these
excuse,
or
maybe
excuse
of
for
particular
products,
and
for
this
particular
purposes
we
should
not
use
our
domain
services,
but
rather
our
other
son
tooling,
and
using
these
tools
we
can
proceed
with
update
the
excuse
and
these
two
supposed
to
guarantee
that
we
don't
don't
break
the
data
consistency,
because
we
have
too
many
relationship
on
the
SQ,
especially
if
the
magenta
is
not
is
not
the
source
of
true.
But
if
the
magenta
is
connected
to
the
external
system
were
like.
A
Earpiece
of
this
connection
is
linked
to
just
buy
the
product
SQ,
because
the
external
system
know
nothing
about
the
product
ID
in
this
case,
so
it
was
a
pretty
long
discussion.
But
now
we
were
getting
more
and
more
question
about
that,
and
one
of
that
was
raised
recently
and
this
question
was
raised
by
I-
was
raised
by
Michael.
A
So
you
can
join
the
discussion
in
in
the
issue
2001.
So
actually
Michael
here
describes
the
necessity
of
sq
changes
and
we
have
quite
a
long,
a
lot
of
thread
of
discussion
here
regarding
whether
s
key
products
Q,
should
be
mutable
or
should
be
immutable.
Alpha
yesterday,
we
had
another
pretty
long
thread
this
time
in
selectional,
and
this
long
thread
currently
has
more
than
let
me
find
it.
A
So
this
long
thread
currently
has
pretty
long
more
than
60
60
replies
already-
and
here
we
hear
it's
discussed
like
the
first
issue
brought
by
Joshua-
was
that
why,
in
our
in
magenta
database
schema,
the
SQ
field
could
be
knowable,
and
actually
the
answer
to
this
question
is
that
you
could
be
notable
and
we
use
this
for
our
product
application
functionality.
So
when
you
duplicate
the
product,
so
when
you
create
the
new
product
based
on
another
product,
what
we
actually
do
we
create.
A
We
create
product
copying
all
the
data
from
the
previous
one,
except
for
the
SQ,
and
we
provide
the
ability
to
do
merchant
to
fill
this
to
fill
the
SQ
data.
On
the
next
step.
We
have
the
admin
panel,
but
what
it
actually
means
that,
on
the
database
level,
we
create
the
record
for
this
newly
created
product.
But
there
is
no
guarantee
that
that
merchant
will
finish
filling
out
this
form
and
he
will
provide
the
new
SKU.
So
potentially
the
data
could
be
in
inconsistent
way.
So
what
did
what
Josh
proposed?
A
He
proposed
to
specify
the
USQ
at
the
time
of
the
product
application,
which
will
definitely
affect
the
UI
experience
in
the
user
experience
how
they
work
with
with
magenta.
So
another
idea
from
my
side
was
not
to
affect
existing,
look
and
feel
and
user
experience,
so
just
introduce
another
service
which
will
which
creates
the
product
based
on
based
on
existing
product,
and
here
is
actually
also
pretty
long
long
thread
here
and
also
in
this
tree.
A
We
also
started
to
discuss
the
question
whether
product
should
be
mutable
or
immutable,
and
Ben
told
us
that
he
has
own
experience
and
the
company,
where
bana
is
working,
actually
provides
an
alternative
admin
panel
for
magenta,
and
this
rule
is
admin
panel.
A
lot
of
their
merchants
actually
update
their
SQ,
and
this
is
especially
true
for,
like
for
fashion
industry
Benna,
like
committed
to
make
the
short
pole
between
between
shorts
array,
between
between
merchants
he's
working
on
just
to
gather
all
that
all
the
reasons
why
merchants
actually
update
askew.
A
So
if
you
have
two
cents
to
add
to
this
conversation
to
to
this
one
or
to
the
one
we
have
in
the
github
github
thread,
don't
hesitate
to
join
us
because,
currently
like
because
this
is
actually
is
a
cornerstone
topic
for
MSI,
because
in
MSI
we
can
see
there.
It's
like
it's
totally
isolated
service,
and
now
that's
why?
Actually,
we
don't
have
any
dependencies
on
a
product
ID
from
magenta.
We
don't
have
any
foreign
key
on
magenta
entities.
We
don't
make
any
join.
A
My
secret
join
to
the
magenta
tables
and
that's
why
we
don't
consider
that
we
we
can
like
make
reference
to
the
product
IDs.
That's
why
all
the
references
we
have
on
based
on
the
product
SKU,
but
what
it
actually
means
that
if
the
product
is
queue
is
updated
in
magenta,
the
inventory
data
would
be
affected
in
this
case.
A
So
if
you
feel
that
you
have
something
to
to
say
about
that,
if
you
consider
that,
for
example,
data
consistency
for
your
merchants
could
be
affected
with
this
behavior,
just
let
us
know,
and
we
we
can,
we
can
discuss
it.
We
can
consider
my
people
and
see
there
are
some
additional
possibilities
for
guaranteeing
consistency
on
the
application
level,
but
is
pretty
pretty
pretty
sophisticated.
Pretty
tough
threat
and
topic
so
don't
hesitate
to.
Let
us
know
what
you
think
about
that.
So,
okay,
that
was
all
what
I
wanted
to
say.
A
C
C
C
The
functionality
that
we've
built
is
source
reservations.
We
all
know
that
TDM
assign
module,
offer
stock
reservations
and,
and
that
allows
you
to
actually
have
a
difference
between
the
some
of
the
quantities
per
source
and
the
actual
saleable
quantity
that's
available
on
the
front
end.
This
is
any
one
you
place
an
order
that
if
in
this
and
for
example,
in
Mike
in
in
this
situation,
when
ten
products
are
ordered,
the
same
quantity
will
be
0
and
no
additional
products
can
be
ordered.
C
C
And
then
you
can
actually
see
that
any
order.
Well,
it's
the
one
quantity.
So
the
problem
we
were
running
into
is
that
that
done
in
this
specific
situation,
I
have
right
here
it's
pretty
easy
to
actually
build
a
warehouse,
connector
and-
and
that
was
the
main
problem
we
were
facing.
I
have
either
stock.
C
That's
called
one
day
only
that's
the
name
of
the
website
and
I've,
aware
of
that's
called
SNH
and
and
I
need
to
know
from
which,
where
I
was
actually
sent,
an
API
call
to
actually
place
a
fulfillment
request
and
to
warehouse,
so
I
need
to
know
which
warehouse
is
available
in
this
specific
case,
there's
only
one
source
available.
So
that
isn't
a
very
complex
answer.
But
if
there
are
multiple
sources
available
and
I
can
add,
one
right
now
assign
source
so
I
can
even
add
another
source
and
now
there's
five
available.
C
Which
would
work
yeah
right,
so
we
normally
when
you
are
when
you
are
ready
to
ship
in
order,
your
your
your
you
see,
the
result
of
the
source
selection,
algorithm
and
the
result
of
the
source
selection
algorithm
is
something
that
we
want
to
use.
So
we
want
to
know.
We
want
to
know
this
value
and
we
want
to
know
from
which
source
which
is
actually
deduct
and
the
product
form
and
baby,
and
we
want
to
note
before
we're
actually
shipping,
because
image
enter
the
shipment
to
see.
C
We
don't
actually
know
that
we,
we
don't
care
from
which
sources
is
coming
from
when
the
world
is
actually
paid,
and-
and
this
is
this
is
allowed
to
be
shipped-
then
we're
actually
going
to
start
to
care
when
it
for
from
which,
where
else
it
will
be
shipped
so
I'm
going
to
switch
to
do
my
database
for
for
a
second
and
show
you
how
to
reservations
are
looking
right
now
and
at
the
moment
we
happen.
We
often
we
have
to
normal
reservation
table
that
actually
does
doesn't.
C
The
actual
will,
the
actual
priority
is
wroking
and
then
slh,
so
it
has
created
a
reservation
and
roken.
The
result
of
this
page
will
always
always
give
give
back
the
results
that
are
already
present
in
this
table,
and
this
way
you
you
have
you
you
a
yes,
you
have
a
source
assignment
before
the
actual
order
is
shipped.
This
means
we
have.
We
have,
we
have
fixed
the
source
assignment
and
therefore
we
can
also
create
our
api
communication
to
our
warehouse.
There
are
any
questions
by
the
way.
C
The
source
has
been
assigned.
The
order
was
already
placed,
sir
we're
already
14
available
well
available,
but
now
the
source
has
been
assigned
a
and
you
can
see
that
are
still
5
available
in
roken
warehouse,
but
there's
one
reserved
the
actual
inventory
of
the
product
still
is
5
and
and
and
if
the
warehouse
doesn't
update
from
from
from
the
warehouse
and
update
its
to
6,
we
will
be
seen
at
the
actual
saleable
quantity
as
up
1,
but
are
still
one
reservation
available.
C
C
So
I'm
now
creating
a
normal
shipment
and
then
and
the
values
here
are
actually
the
values
from
the
actual
table
so
like
if
the
sources
that
they're
there,
the
search
algorithm
air
doesn't
really
do
anything
anymore
and
because
they
go
ahead,
will
always
return
the
normal
values
that
are
available
here.
All
right,
I'm,
crazy
shipping
right
now,
so
the
the
shipment
has
been
created,
it
has
ordered
in
person
shipped.
The
thing
I
should
be
seeing
right
now
is
that
the
saleable
quantity
is
is
still
the
same
on
the
on
the
webshop
only
it.
C
Greater
socialization,
it
is
now
actually
canceled
the
the
search
reservation
and
it
is
actually
deducted
the
actual
source
quantity.
So
it's
still
the
fifteen
and
I
just
updated
it
from
five
to
six,
and
now
it's
back
to
five
because
it
actually
has
has
implemented
the
reservations
the
way
it
makes
it
interesting.
They
said
at
the
moment
the
the
actual
functionality
that
actually
does
it
actually
moves.
The
did.
C
The
reservation
from
the
from
the
stock
to
the
source
is
a
single
method,
and
you
and
you
can
just
create
a
plug-in
on
this
method
to
actually
hook
into
it
to
actually
create
awareness
integration,
and
that
gives
you
all
the
data.
That
is
the
debt
that
you
need.
It
gives
you,
as
a
social
source,
reservation
result
that
actually
gives
you
all
the
information,
and
it
gives
you
the
actual
reservation,
item,
etc.
D
C
So
somewhere
doing
it
a
Singh,
then
there's
a
specific
reason
to
do
it,
I
think
so.
For
example,
when
you
ever
wear
out
that
two
points
oft
and
your
orders
before
a
certain
time
in
living,
they
they
want
to
do
it
once
one
today,
for
example,
or
our
yard,
or
you
want
to
do
it
multiple
times
a
day,
but
the
the
case
we
were
running
into
that
the
date
the
water
is
placed
in
doesn't
always
determine
the
actual
priority
that
the
sources
should
be
assigned.
So
we
have.
C
We
have
certain
and,
for
example,
certain
consumers
that
actually
have
higher
priority
the
searches,
certain
business
orders
or
the
other
way
around.
So
the
the
way
it
works.
It
has
a
source,
it
has
a
move,
move
reservation
from
stock
to
source
runner
and
any,
and
it
actually
fetches
all
the
orders
that
haven't
been
assigned
yet
and
will
be
and
when
and
will
be
assigned
to
actually
to
a
certain
to
the
source.
The
the
order,
selection
service,
yep,
the
order,
selection
service
and.
D
C
Example:
yes,
so
should
this
the
the
current
one
is
a
specific,
the
the
actual
method
that
is
called
error?
It's
it's
an
API
in
it
and
it
it
should
be
able
to.
You
should
be
able
to
call
it
from
from
the
REST
API
or
or
maybe
there
should
be
a
setting
to
actually
do
it
synchronously.
The
idea
to
do
it,
asynchronously
is
that
the
source
selection
algorithm
and
the
idea
behind
the
source
selection
algorithm
is
that
it
can
be
heavy
and
it,
and
it
is
allowed
to
actually
run
for
a
few
hundred
milliseconds.
D
A
D
C
D
C
C
So
that's
a
functionality.
We
we
have
built
right
now,
there's
an
and
there
will
be
able
to
do
give
a
quick
recap:
we've
built
it.
We've
created
two
modules:
the
orders
for
the
patient's
actually
handles
all
the
interaction
with
all
the
orders
and
then
actually
actually
actually
make
me
make
sure
that
everything
is
working
for
them,
for
the
credit
memos
for
all
the
returns
etc
and
the
other
and
the
other
module
is
the
is
actual
core
of
the
source
reservations
itself.
C
We
are.
We
are
currently
working
on
actual
building
trends
for
orders.
That's
all
the
way
around
by
the
inventories
in
coming
in
the
future,
and
we
and
we're
we're
we're
bill
building
on
top
of
the
other
functionality,
and
so
that
was
that's
a
function
to
be
currently
fi.
I.
Don't
have
anything
you
like
to
show
you
yet
for
the
transfer
orders,
but
it
is
and
all
the
tests
have
been
written
and
everything
should
be
and
should
be
working.
A
Have
a
question
yeah
to
do
instant
correctly,
that
because,
for
example,
in
magenta
in
like
MSI
out-of-the-box
mm-hmm
said
a
result
of
the
source,
selection
algorithm
is
just
a
suggestion
and
merging
and
update
it
with
own
value.
So
he
can
neglect
completely
what
was
proposed
by
the
algorithm,
but
as
I
understand
this.
So
the
migration
from
the
reservation
to
social
yeah.
C
E
C
Believe
it
is
I
believe
it
it
will.
Actually,
it
will
actually
cancel
the
reservation
that
it
has
on
the
order
item
and
actually
do
what
you
I
think
I
think
it
be
use
case,
wasn't
for
us
to
actually
be
able
to
do
to
for
further,
for
the
admin
user
actually
influence
it,
because
in
in
practice
we
don't
often
use
that
and
I'm
not
completely
sure
if
it's
currently
possible
or
or
if
it
will
break
mm-hmm.
A
C
A
So,
okay,
so
George
just
dropped
me
a
message
that
he's
unable
to
join
meeting
so
I
don't
have
my
magenta
set
up
on
his
PO
requests,
but
at
least
I'm
I
will
briefly
describe
what
he
did
and
the
initial
root
cause
of
this
issue
appeared
from
the
MSI
sectional.
This
way,
I
really
encourage
you
guys
if
you
have
any
problems
or
issues
or
just
ideas
regarding
the
inside
just
draw
a
line
into
the
MSI's
like
channel
we're
reading
it.
We
are
processing
your
messages
and
we
like
we
making
that
happen.
A
So
we
transform
your
ideas
into
the
software
and
the
actual
is
idea
was
so
the
guy
whose
name
is
Shahrukh
was
making
I
believe
his.
He
was
introducing
some
new
source
selection
algorithm,
and
so
he
introduced
one
more
algorithm
and
the
idea
that
this
new
August
was
introduced.
Some
filtering
on
the
sources
available
for
the
order
fulfillment,
thus
introducing
this
algorithm.
A
Actually,
the
source
availability
is
decreased,
so
currently
like,
for
example,
for
the
for
the
out-of-the-box
priority
based
algorithms
able
to
sources
and
as
soon
as
he
applied
own
algorithm,
there
was
a
filtering
for
sources,
for
example.
Maybe
some
particular
source
can
just
fulfill
a
particular
type
of
clients.
Maybe
there
are
just
there
are
stores
oriented
for
just
for
males
and
for
women.
A
That's
why
he
made
this
filtration
and
that's
in
this
case
it
was
just
one
source
which
can
fulfill
the
order,
and
in
this
case
it
was
some
user
like
usability
lock
in
this
case,
because
there
is
no
any
sense
to
so
to
show
the
drop-down
with
with
the
one
item
only
and
this
guy
is
requested,
asked
me
to
introduce
this
very
selecting
of
source.
So
this
actually
what
we,
what
George
did
Josh
introduced
all
UI
component
and
he
provided
own
implementation
of
the
Select
and
the
if
the.
A
A
E
Okay,
hopefully
you're,
seeing
that
there,
okay,
so
just
a
brief
presentation
just
should
be
doing
weekly
just
running
through
quality
and
testing
updates.
So
where
we
are
this
week
is
as
usual,
with
our
test
definitions,
a
manual,
we
have
increased
that
number
591,
it's
roughly
20
or
25
tests
per
week,
increase
we're
getting,
which
is
great,
a
lot
more
coverage,
a
lot
more
definitions
that
were
both
used
for
manual
testing
and
in
scope,
with
a
womano
release
and
as
basis
for
automation.
E
So
we
can
cover
the
SE
rows
going
forward
and
have
those
automated
I
Mayan
testing
results.
These
are
from
way
back
in
December,
but
we're
hoping
to
then
get
a
new
set
of
these
that
we
can
baseline
against
and
have
a
good
comparison
point.
So
once
we
run
more
full
manual
test
cycle,
we'll
have
a
good
comparison
against
this
last
result
and
we'll
see
how
we're
looking
from
there
and
automated
testing
then
so.
A
couple
of
headlines
in
this
severity
hasn't
changed
significantly
component
hasn't
gene
significantly.
E
These
are
just
flowing
from
the
manual
test
definitions,
but
where
we
do
have
a
little
movement
is
here,
so
we've
managed
unskipable,
mated
test
Suites
something
gets
kept
and
it
doesn't
get
unscripted
for
quite
a
while.
We've
done
a
significant
amount
of
work
on
some
of
our
tests
to
unskipable
is
covered
and
it's
important
both
in
terms
of
keeping
the
test
base
clean
and
also
where
tests
are
skipped.
They're
skipped
for
a
reason,
and
that
means
that
coverage
is
more
problematic
to
automate
so
actually
fixing
six
skip
tests
is
very
valuable.
E
It
also
taught
us
a
lot
about
how
we're
gonna
integrate
with
b2b.
One
of
the
main
problems
was
with
merge
files
and
UI
changes
around
Cee
in
b2b,
so
its
taught
us
a
little
more
about
that,
so
we'll
be
able
to
increase
our
coverage
in
those
areas
as
well.
So
that's
a
great
result
for
us
as
well,
and
we
have
managed,
in
terms
of
creation,
trans
we've
managed
to
merge
pr's
across
unscripted
unchanged.
The
automated
number.
E
The
automated
number
is
fully
automated
scenarios,
including
skips,
so
that
number
should
go
up,
but
it
doesn't
on
this
chart
and
our
PRS.
The
mainline
pending
have
been
approved
before
them
in
PR
1975.
That
should
be
going
through
immediately,
so
we're
going
to
tech
that
number
up
as
well
also
we've
discovered
that,
with
smaller
UI
changes
in
MSI,
there
are
internal
test
filters
that
we're
seeing
in
builds
so
20
test
cases
and
we're
feeling
them
internally.
As
of
Wednesday
and
Thursday.
Those
are
all
9
fixed
with
updates
and
emerged
PR.
E
So
we're
back
to
green
builds
and
unless
and
learn
from
that
which
we'll
see
in
this
is
we'll
be
running.
More
periodic
fool,
builds
or
I
will
particularly
to
ensure
that
the
test
cobia
stays
clean,
we're
staying
on
green
builds
and
we'll
see,
probably
some
more
PRS
or
smaller
changes
just
to
keep
that
task
base
and
the
selectors
and
all
of
our
flows
running
with
HPR
and
so
generally
good
news.
Some
good
progress
made
I'm,
also
working
with
Josh.
E
What
issues
you
run
into
him,
how
we
work
through
them
and
that'll
also
allow
me
to
engage
with
some
new
PRS
if
someone
wants
to
contribute
MF
TF
with
their
contributions
as
well
I'll
be
able
to
use
the
lesson
learns
there.
So
we
can
get
everyone
to
speed
quicker
and
make
it
a
fairly
friction-free
process.
A
A
F
C
F
There
we
go
so
this
is
a
quick
preview
of
what's
coming.
We
have
some
documentation
in
place
now
for
dev
Docs.
As
soon
as
we
have
the
package
ready
to
go
for
msi,
hopefully
next
week
we
will
also
be
adding
this
content
to
dev
dogs.
It
has
to
lag
behind
a
little
bit.
You
know
until
we
actually
go
live,
but
if
interested,
you
can
look
at
this
wonderful
information
here
that
Kevin
is
finished.
For
us.
F
So
as
soon
as
we
have
our
packages
ready
to
go,
we
will
also
update
and
make
live
all
of
the
documentation
and
we'll
be
posting
that
in
the
slack
Channel
and,
of
course,
tweets
and
everything
else.
Also,
if
you
haven't
looked
at
it
yet
here
is
the
wonderful
blog
post,
who
we
were
talking
about
last
week,
that
I
borrow
and
all
of
the
architects
really
loved
here
on
in
Magento,
and
it
looks
like
a
lot
of
people
have
also
started
to
enjoy.
It
goes
into
the
depths
of
you
know.
F
The
best
practices
for
working
with
our
API
is
some
designing
and
it
does
highlight
some
MSI.
Definitely
if
you
have
not
read
it
yet,
you
should
I'll
go
ahead
and
post
another
link
to
this
as
well
as
slack.
That's
all
I
have
at
the
moment,
but
if
you
have
any
questions
happy
to
give
some
more
information,
I
also
had
a
request
to
update
one
of
the
diagrams.
That's
going
to
get
updated
right
after
this
meeting.
F
F
And
as
soon
as
I
get
that
updated,
I'll
also
ping
that
in
the
slag
channel,
so
everybody
has
it.
So
no
a
lot
of
folks
use
our
diagrams
and
you're.
Welcome
to
with
that
in
mind,
if
you
do
see
a
screenshot
you'd
like
an
edit
to
or
a
different
kind
of
diagram,
we
do
have
quite
a
few
that
are
in
progress
to
better
describe
reservations
and
with
a
lot
of
the
changes
coming
through
I'm
happy
to
work
with
anyone
that
needs
some
help
on
that.
So
just
feel
free
to
contact
me
and
slack.