►
From YouTube: Magento MSI Open Demo. September 14, 2018
Description
Agenda:
1. Async Bulk Operation for Transfer Source by @TheRick
2. Fixing Low Stock Report during MM18PL by @aleron75
3. Grouped Product support for MSI by @Ivan Pletnyov
4. Status of regression preparation. Fixing all Jenkins builds @alex
A
A
Today,
I
really
wanted
to
Alexander
loom
to
visit
this
demo,
because
Alexander
is
an
owner
of
a
synchronous,
API
and
the
bulk
API
track,
which
is
religious
implemented
by
community,
because
today
we
will
show
how
a
synchronous,
API
introduced
and
used
in
in
the
business
functionality
of
MSI
and
the
probably
we
will
start
from
from
this
feature,
which
is
going
to
be
demonstrated
by
Ricardo,
who
made
this
functionality
in
the
scope
of
contribution
day
during
the
meet
magenta
in
Poland
previous
rivers
weekend
so
record
the
feel
free
to
share
your
screen
and
go.
Thank.
B
Ok,
you
should
see
my
screen
so
basically,
yes,
what
what
I
did
is
to
add
the
synchronous,
bulk
operation
to
this
mass
separation.
So
previously
this
was
approached
by
a
single
synchronous
operation
that
was
acting
at
low
level,
so
it
was
basically
using
a
resource
model
to
apply
the
modification
and,
of
course,
when
you
use
such
approach,
we
have
a
lot
of
issues
with
relaxing
and
whatever,
because
basically
you're
not
engaging
the
plugins.
B
So
what
it
is
to
convert
all
this
old
approach
to
one
single
item
update
so
I
created
API
to
update
each
single
item
and
then
all
this
process
is
made
in
a
synchronous
call
and
I
used
the
work
that
needs
one
I
hope
this
is
the
right
phone
session
actually
did
with
the
bulk
API.
So
we
still
have
something
to
to
fix,
but
just
make
an
example.
If
I
choose
these
two
products
and
ask
for
a
sign
inventory
bulk
operation,
the
interfaces
is
almost
the
same
as
before.
So
we
select
what
are
the?
B
As
you
may
probably
notice.
The
description
is
not
so
good,
but
we
are
working
with
it
soon
to
to
fix
it,
because,
as
far
as
now,
it's
limitation
of
the
bulk
API
operation,
so
one
of
the
main
change
as
I
said
before,
is
that
we
are
not
going
to
process
the
operation
as
one
single
resource
model
operation,
but
basically
I
created,
I,
don't
know
if
you
can
see
my
phpstorm.
Can
you
see
it
or
are
you
stuck
on
my?
We
have
stuck
with
the
area?
B
Oh
I'm,
sorry
just
give
me
a
minute
I'm,
stopping
you
sure
and
showing
you
again
desktop
3.
Okay.
Now
you
should
see
it.
So
what
I
did
is
to
create
three
classes
for
source
assign
source
on
assign
and
metal
transfer
that
are
playing
this
operation
for
each
single
item
and
the
bulk
API
basically
is
calling
this
operation
for
each
single
item,
and
thus
it
is
almost
working
and
basically
I
was
able
to
reduce
either
the
codebase,
because
now
I
can
rely
on
existing
features
and
is
much
way
better.
A
A
Actually,
there
is
no
guarantee
that
we
will
have
the
scalable
enough
operation,
because
potentially
our
operation
can
not
scale
like.
Maybe
we
will
have
a
bottleneck
on
a
level
of
database
or
something
so
it's
better
to
have
performance
friendly
API,
which
accept
an
area
of
entities
but,
for
example,
to
skill.
The
separation
we
can
perceive
not
not
like
are
saving
all
the
entities
at
once.
It's.
B
A
Actually,
what
happens,
for
example,
now
if,
if
transferring
of
the
single
source
items
will
fail?
You'll
probably
just
ignore
it,
because
it's
independent
work,
which
you
can't
influence
any
how
others
others
of
item
working
so
I,
believe
you'll
just
keep
it,
and
you
will
tell
the
agent
that
something
went
wrong
actually
in
the
bulk
API,
currently
yeah.
B
C
B
B
Okay
and
how
do
you?
What
do
you
think
about?
Well,
when
I
run
on
a
synchronous
operation
I
got
that
report
on
the
top
of
the
page
as
notification
in
which
I
see
your
task
was
executed
and
I,
updated
and
items.
So
it
reports
the
number
of
items.
Now
we
got
numbers
the
number
of
operation,
so
I
don't
know.
If
we
can,
we
still.
A
B
If,
for
example,
if
my
bulk
update
is
made
by
100
products
and
I
select,
let's
say
150
products,
I
can
only
see
two
items
has
been
successfully
updated.
Yeah
it
can
be
misleading.
Actually,
so
it's
very
stupid,
of
course,
but
I
think
it
can
be
a
problem
from
the
user.
From
the
usability
perspective,
maybe.
A
B
C
A
The
way
tomorrow,
we
will
have
a
contribution
they,
actually
you
can
see
that
I'm
not
in
the
office.
I
am
now
the
the
Western
Ukrainian
city,
where
we
supposed
to
start
in
the
top
in
a
half
an
hour
and
tomorrow
will
have
a
contribution
days.
So
if
you
have
a
spare
time,
you
can
join
us
and
we
can
talk
more
closely.
A
A
E
A
D
D
Let's
take,
for
example,
this
back
and
let's
say
that
we
have
quantity
of
15,
that's
below
the
20
question
that
we
have
seen,
and
this
is
the
actor
out
of
the
report
without
applying
without
applying
the
fix.
So
we
don't
get
that
product
I
cheated
a
bit
because
I
forced
my
feet.
You
know
right.
So
let
me
just
lie
it.
D
D
This
is
still
a
work
in
progress.
I
show
you
also
the
table
where
we
have
this
destroy
populated,
whereas
before
we
didn't
have
it,
this
is
a
still
a
work
in
progress
who
requests,
because
working
on
that
I
also
realized
that
we
still
have
an
issue.
If
we,
for
example,
apply
a
mass
update,
let
me
show
you
if
I,
for
example,
change
quantity
below
20
for
these
two
products.
D
Lost
Oh,
creeper
steal,
don't
show
any
data
related
to
those
two
products
that
I
just
updated
and
what's
more
I,
also
have
a
suspect
that
import
won't
work
as
well.
So
this
is
the
first
step
of
my
fix
and
I
will
likely
work
on
that
in
the
next
week
and
hopefully
give
you
an
update
about
this
about
this
issue
in
progress.
That's
actually
all
from
my
side,
if
you
have
any
questions,
feel
free
to
ask
I'm
here.
A
A
F
F
F
A
Thank
you
so
in
the
scope.
Actually,
that
was
a
finalization
of
all
the
work.
We've
done,
the
voltage
for
the
grouped
product,
support
of
multi-source
inventory,
and
currently
we
have
just
a
gap
in
one
product
type,
in
the
bundle
as
it
is
only
product
type.
We
don't
have
supported
motor
source
inventory
for
all
other
product
type.
Since
now
we
either
support
is
a
Maltese
or
semantic
functionality,
and
actually
that
was
present
in
buy
one,
and
it
was
all
regarding
the
functionality
which
was
implemented
in
scope
of
this
week.
Another
update
would
be
shown
by
Alex.
A
We
will
show
you
the
preparation
for
aggression
and
the
preparation
for
the
quad
freeze
of
magenta
to
the
tree
branch
and
what
was
done
from
MSI
side
to
meet
this
requirement
of
the
feature
freeze
and
because
we
are
supposed
to
complete
our
work
to
provide
to
provide
the
features
to
provide
the
stable,
stable
piece
of
code
of
MSI.
We
supposed
to
be
delivered
in
the
scope
of
magenta
to
date.
Three,
please
so
Alex
the
stage
is
yours.
A
E
E
It
means
that
test
is
not
that
this
test
is
randomly
failing
because
of
some
conditions
we
have
in
this
test,
but
from
MSI
standpoint
from
MSI.
For
it
we
did
everything
to
make
this
build.
Green
and
I
also
want
to
share
with
you
a
different
builds,
which
were
run
not
by
me
by
core
engineers
and
I
can
show
you.
The
same
failure
is
happening
on
magenta
mainline
right
now,
so
the
same
figuration
page,
the
same
problem,
the
same
button
cannot
be
click
the
other
build.
Also,
this
is
Matt,
and
this
build
flood
containing
MSI
tests.
E
We
have
six
unstable
tests.
We
currently
in
my
gentle
working
on
making
such
tests
table.
We
have
a
group
of
people
who
is
working
on
these
issues,
so
in
Magento
as
soon
as
in
magenta,
this
will
be
fixed.
We
can
say
that
MSI
build
is
100%.
Green,
but
from
MSI
standpoint
we
don't
have
any
issues.
All
mi
site
has
are
stable
and
green.
We
can
see
I'm
aside
multimode
test,
you'd
has
86
green
tests,
MSI
single
mode
has
15
tests
and
somewhere
in
this
suit
least,
we
have
msi
sort
order
caste.
E
Mtf
tests
all
green
right
now,
while
we
were
stabilizing
this
build,
we
skipped
several
of
tests
because
they
have
much
more
complex
problems,
but
currently
Jones
tenets
working
on
making
these
tests
on
skipped
working
properly.
So
he
can
share
more
info
on
how
on
skippin
is
going
right
now
and
what
what
what
we
want
to
accomplish
in
next
step
of
making
this
build
reliable
for
everybody
that
are.
C
C
Having
flaky
behavior
that
we
had
to
go
in
and
actually
get
updates
on
them
for
most
of
them,
we
were
able
to
update
them
and
actually
stabilize
them,
but
there
was
a
handful
of
msi
tests
that
we
actually
did
have
to
lip
skipping
along
with
those
msi
tests.
We
found
some
in
core
that
was
having
issues
when
combined
with
msi,
so
we
ended
up
also
skipping
those
tests
and
we're
going
to
actually
work
on
getting
them
stable.
One
of
the
biggest
issues
that
we
are
running
into
with
these
tests
is
test
isolation.
C
There
are
several
tests
that
exist
in
say,
like
b2b
and
EE,
and
even
and
we've
had
a
few
in
msi,
where
the
test
is
not
being
it's
not
cleaning
up
after
itself.
So
the
test
is
messing
with
config
variables.
Turning
settings
on
and
off
when
they
actual
after
step
runs.
There
are
no
cleanup
steps
in
the
African.
This
is
incredibly
important,
something
that
we
want
to
remind
everyone
to
be
more
diligent
on
I'm
gonna.
Definitely
it's
an
improvement
on
myself
too.
We
all
do
we
all.
C
C
So
that's
right
now
we're
working
under
test
1631
here
these
are
the
handful
of
msi
tests
that
we
weren't
able
to
actually
stabilize
before
we
decided
to
actually
skip
them
and
work
on
them
over
this,
the
rest
of
this
week
and
for
next
week.
So
these
are
the
msi
tests
we
weren't
able
to
fix,
and
then
these
are
all
the
ones
from
B
to
B
or
EE
that
are
having
conflicting
issues
again
for
test
isolation
introduced.
C
E
Basically,
what
is
happening
with
my
gentle
b2b
and
you
have
much
more
modules
to
install
in
Magento
and
infrastructure-
has
a
really
small
timeout
to
wait
until
magenta
will
be
installed.
So
basically,
what
is
happening,
build
reach
in
timeout
and
Magento
didn't
install
until
this
time
out.
We
we
are
looking
for
for
the
guy
who
can
increase
this
time
out
to
wait
until
magenta
will
be
installed
after
this
I
believe
when
gentle
sample
day
that
has
will
be
green
either
and
the
I
believe.
A
This
question
could
be
pretty
interesting
for
Anton
cream,
because
actually
there,
this
issue
is
a
simple
date:
installation
on
shallick
for
Enterprise,
Edition
and
b2b.
We
experienced
it
before.
We
have
quite
a
lot
of
configurable
products
to
be
beyond
installed
there
and
currently
on
an
MSI
branch.
We
have
a
dependency
price
index
on
inventory
index
and
the
catalog
search
index
on
price
limit
and.
A
The
time
of
the
installation
of
a
lot
of
products,
we
have
a
lot
of
green
dictation,
of
dependent
indexes
and
actually
they
seem
to
introduce
some
performance
degradation
at
the
time
of
new
product
being
created,
were
inventory,
updated
for
prices,
updated
and
actually
I
believe
this
is
the
main
result.
Why.
G
A
G
So
it
should
be,
it
should
be
pluggable
behavior,
so
you
don't
need
to
have
the
dependency
and
that's
that's
one
part
that
sold
as
out
and
I
would
I
think
if
it
makes
I'm
not
sure
which
is
better
to
fix
how
it
happens.
I
believe
performance
I
propose
there
for
me,
okay,
but
let's
figure
out
its
performance
team
and
the
other
thing
is
degradation
and
performance
degradation
that
we
mentioned.
Is
that
so
I'm
either
doing
installation
install
sample
date,
and
there
is
a
lot
of
ringlets
or
indexation
happening.
A
A
A
A
Intone
probably
is
not
in
a
very
good
mood
because
he
missed
the
fermentation
by
retarder,
but
I
will
I
will
send
him
a
recording,
so
he
can
enjoy
regardez
presentation
after
the
demo,
as
well
as
mark
present,
who
is
not
present
on
today's
Dima
but
for
all
others.
Thank
you
very
much
for
your
time
and
you
made
a
great
drop.
We
have
a
pretty
great
progress
and
thank
you
for
your
times.
Thank
you
for
your
effort.