►
Description
Hey everyone, here is the delayed recording of our open Async Import meeting on Jan 9.
- Quick catch up after holidays
- Status of the async service prototype
- Bonus footage of Alex and Stepan after the meeting adjournment
C
No,
not
all
good
hi.
Everybody
welcome
to
the
first
meeting
of
2019
of
everybody,
had
a
good
vacations
and
now
already
ready
to
work.
We
have
some
some
update
times
last
three
weeks
and
I
was
really
surprised
that
we
got
so
much
updated
science.
Last
three
weeks.
I'll
guess
I'll
share
my
screen
and
we'll
start
from
the
beginning.
C
B
C
It's
currently
available
in
a
sinking
boat
repository,
we
generally
disabled
the
synchronisation
of
this
repository
with
main
two
points
redevelop,
so
it
will
not
go
there.
All
development
will
happen
only
in
this
one
and
yeah.
That's
done
that's
cool.
We
also
mentioned
one
small
issue
that
there
Travis
basically
didn't
report.
Some
fixes
I
mean
some
errors
which
attorney
he
had
to
report
because
next
pour
request
tiled
with
an
errors
and
I
provided
yesterday
yeah.
It
was
yesterday
the
another
pool
request
which
only
fix
the
issues
that
Travis
reported
to
us.
C
There
was
some
minor
one
like
by
convo
like
yeah
composure
file
like
edge
readme
file
at
extension,
attributes,
because,
generally
we
use
in
her
house
the
appropriate
interfaces
for
that.
That
was
his
him,
a
whitelist
missing
and
so
on.
So
it's
basically
are
also
done
and
now
all
green
and
it
can
be
merged.
C
Yep
then
we
have
an
old
full
request,
which
is
still
the
AIA.
By
the
way
that's
mean
that
Stoppa
parently
can
make
his
poor
request
with
a
applauding
of
the
local
file.
We
are
there
API
so
journey.
He
already
provided
this
pull
request
out
of
this
repository
and
waited
for
time
when
I
will
merge
this
base
implementation
and
now
it's
ready
and
he
can
journey
start
yep.
So
I'll
go
from
the
blue
request,
which
we
still
have
open
and
last
week,
I,
basically
fighting
with
the
trainees
for
them
and
slowly
winning
this
battle.
C
We
have
topic
to
you
service
contract
name.
We
still
have
some
failed
tests
on
it.
It's
basically
was
ready
to
merge
and
we
mentioned
there
was
some
static,
static
test
failed,
which
was
fixed
and
now
Travis
looks
almost
good.
There,
always
some
unit
tests
which
are
failing
and
I
almost
sure.
It's
not
related
to
to
this
group
flow
request,
but
I
still
need
to
make
it
green.
Well,
that's
still
in
progress
of
merging.
C
Then
we
have
repair
request,
process
or
full
implementation,
which
is
Enoch
and
again
and
on
this
one
also
was
ready
to
merge,
but
I,
but
JUnit
test
failed
and
I
like
eight
minutes
ago
found
the
problem
and
fixed.
It
just
didn't
push
it
yet
and
after
that
every
start
the
trellis
and
hope
that
everything
will
be
fine.
Then
then
we
can
also
merge
it.
C
Then
we
have
yeah
directly
after
the
Christmas
in
New
Year
time
we
receive
the
full
request
for
activating
or
journaling
making
the
delete
operation
possible,
executors
synchronously.
It's
still
in
review.
The
guy
basically
already
made
some
changes,
but
then
we
had
a
modern
issue
but
Johnny.
He
used
her
registry
that
was
deprecated
and
not
recommended
to
use
anymore,
but
that's
changes
which
he
still
have
to
do.
C
C
D
C
C
C
C
Generally
till
some
work
to
do
here,
but
hope
that
it
will
be
fixed
soon
and
in-1,
more
which
we
did,
which
we
discussed,
which
we
found
out,
that
we
have
a
swagger,
cashing
issue.
So
basically
we
have
to
api's
or
to
Swagger's
implementations.
One
is
a
standard
one
for
Magento,
REST,
API
and
then
another
one
is
for
a
synchronous.
C
Api
and
issue
was
discovered
that
when
you
first
load
the
usual
swagger
and
then
open
the
synchronous
wagger,
you
see
the
endpoint,
which
should
not
be
there,
and
it
was
caused
by
the
that
they,
both
using
the
same
caching
key
and
you
open.
The
first
one
is
cashing
your
you're,
like
output
of
your
service
contracts
and
then,
when
you
open
it
on
as
a
synchronous
trigger,
you
also
see
them
there.
So
yeah
this
pull
request.
Basically,
you
know,
I
also
gets
made
it
last
week.
C
It's
just
just
show
you
it
generally
here
on
it's
made
with
the
plugin
or
favority.
I
think,
and
it's
just
changing
the
caching
key
for
this.
A
synchronous
requests
and
yesterday
I
successfully
finally
run
all
tests
on
Travis
in
a
green
mode
like
and
I
guess,
I
sent
this
message
already
to
to
flatten
or
that
he
can
try
to
merge
it.
Voila.
E
E
C
Good
thanks
yep
so
journey
from
other
side
from
website
the
Alex.
Isn't
here,
I
guess:
if
we
were,
we
proceed
to
work
on
the
expert
in
the
entities
to
the
Magento.
We
are
the
API,
so
this
connection
here
zone
it
I,
cannot
give
you
more
details
on
that.
I
hope.
You'll
join
us
next
meeting,
just
to
provide
some
update
here,
yeah
and
I
also
between
those
Christmastime
I
created
some.
You
started
here
after
we
merge
the
base
extension,
so
we
now
can
already
start
to
implementation.
C
The
local
processor,
which
is
table,
isn't
it
remote
file,
basics
to
fall
order
pot,
helps
base64,
uploader
I
also
clean
up
the
stories
here,
a
little
bit
so
we've.
Basically,
my
idea
was
to
be
a
bit
more
prepared
for
the
for
this
year
so
and
maybe
take
part
in
more
contribution
event
that
we
can
and
we
invite
more
people,
but
we
have
more
strict
tasks
there
that
we
can
just
crop
and
stuff
to
do
that,
to
work
on
them
and
last
point
for
today
that
I
have
it's
just
two
questions
to
you.
C
C
C
C
F
F
D
It
was
always
a
security
recommendation
for
security
reason
to
not
work
with
any
folder
outside
magenta
root,
so
I
think
it
is
still
valid
request,
and
especially
it
comes
from
kasi
answer
is
probably
I
mean
that
there,
like
any
in
any
folder
outside
magenta
root,
is
potential
security
problem
with
combination
with
some
other
abilities.
So
yes,
it's
better
to
reduce
the
surface
attack
surface
by
working
only
with
a
problem
with
that.
No.
D
C
B
C
D
D
C
C
Had
we
had
stage
one
stage,
two
and
stage
three
stage:
two,
it's
mostly
the
UI,
so
that's
platform
for
Magento
monolid,
which
will
have
any
on
the
interfaces
to
communicate
with
with
our
model.
Basically,
we
are
on
stage
one.
We
pleaded
it
to
two
different
parts,
a
file,
upload
and
then
file
start
and
like
they
they
import
start.
So
what
we
have?
We
have
the
basics
extension
that
other
people
can
start
to
work
on
it
choose
on
the
implementation
phase.
C
We
have
currently
the
local
file
upload,
who
request
almost
ready
by
step,
and
we
have
a
remote
file
upload,
also
almost
ready
by
one
of
the
guide.
Who
is
not
here,
I
guess
nobody
know
him
in
any
case
and
we
have
base64
upload
open
and
we
have
also
Alex
Basilio,
who
is
working
on
generally
parsing
the
entities
and
sends
them
to
my
Center.
C
D
And
I
don't
remember
if
you
explicitly
defined
the
backlog
for
tests,
but
I
think
that
should
be
also
important.
Part
of
of
of
this
epic
and
I
think
it
would
be
a
good
experience
for
many
people
to
work
on
unfunctional
and
throughput
tests
because
import
of
course,
a
synchronous
import
is
a
bit
different
beast
from
from
from
synchronous
import,
but
it
could
be
good
to
demonstrate
some
throughput
some
high
throughput,
whether
the
continuous
with
a
desert
would
be
integrated
into
our
city.
B
D
B
D
We
have
this
work
in
progress
on
magenta
modularity,
so
it's
mostly
research
phase,
so
no
team
internally
magenta
is
working
right.
Now.
It's
only
architecture
team
doing
some
prototypes
and
research
and
I
have
this
branch
with
split
framework
and
again
it's
still
a
work
in
progress
and
to
really
use
it.
You
need
to
use
them.
Magenta,
Composer,
approach,
composer
installation
approach,
but.
D
B
D
The
sample
magenta
project
that
uses
a
code
base
so
in
this
code
base
we
have
some
big
improvements
in
to
magenta
framework
like
splitting
framework
components,
whitening
magenta
application
by
reducing
dependencies
between
components,
introducing
some
new
dependency
injection
configuration
features
significantly
whitening
caching
and
while
one
of
my
favorite
features
is
automatic,
cache
invalidation,
so
the
developers
will
not
have
to
think
about
cache
invalidation
when
they
edit
files.
So
it's
built
into
magenta
and
doesn't
require
to
link
also
to
this
a
PC.
D
You
cache
yes,
yes,
so
so
it
would
be
good
if
you,
if
you
can
play
with
that
and
give
me
some
feedback
or
if
you
can
join
working
on
that
later,
so
I
think
so
it's
somewhat
related
to
this
project
because
we
might
we
might
want
to
do
it
migrated
to
that.
So
this
branch
is
bye-bye
currently
and
this
branch
should
be
merged
into
that
four
branch.
When
we
create
it,
we
don't
have
to
look
for
it.