►
From YouTube: Community Contribution Triage 07/27/2020
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
B
A
Hour,
like
10
0,
3,
10,
13,
10,
23
and
further
when
we
pla
when
we
plan
something
with
such
expressions,
the
task
is
absent
in
the
current
channel
and
the
job
is
not
executed.
Let's
go
step
by
steps
then,
first
of
all,
we
need
to
plan
a
current
job
with
express
with
such
expression,
three
half
intent
and
then
run
in
magento,
chrome
and
after
that
actual
result,
chrometastic
expression
was
not
shadowed
and
zpr
has
been
already
created
for
this
issue.
A
C
Let
me
just
add
about
a
little
bit
from
product
perspective
and,
as
you
know,
we
have
a
lot
of
tasks
in
magento
schedule
it
by
some
period
of
time
it
could
be
like
asynchronous
execution
queue,
execution
and
chrome
and
so
on.
It
could
be
update
products
during
index,
update
promo
rules
whatever
and
previously.
C
A
Yeah
yeah,
it's
it's
quite
specific,
current
shadow.
It
begins
from
three
minutes
and
every
ten
minutes.
Job
of
the
shuttle.
D
A
Because
actual
results
not
shadowed
task,
we
have.
B
They
have
the
chronology
that
failed.
Currently
imagine
to
do,
but
it's
not
a
picture.
It's
real
bug,
because
we
should
capability
and
usually-
and
I
mean
drawn
jobs-
allowed
to
use
this
behavior-
we
don't
use
it
imagine
to
do
directly,
but
our
extension
developer
can
use
it
program.
Jobs
is
really
important
for
china
for,
from
extension
developers
perspective
because
yeah
a
lot
of
rain
index
and
different
stuff.
They
do
by
the
at
the
crown
job.
B
B
D
B
A
A
So
this
issue
is
the
problem
with
the
possibility
to,
in
light,
translate
some
phrases.
Let's
move
to
the
steps,
we
should
disable
all
shipping
methods
available
and
create
simple
product
now
to
reproduce
the
issue.
We
should
go
to
the
stores
and
once
developer,
translate
in
line
and
enable
translate
inline
for
storefront.
A
D
Got
it
okay,
so
this
isn't
changing
the
ux
at
all,
like
the
experience
is
just
modifying
the
logic.
To
get
those
to
be
able
to
be
translated.
Is
that
correct.
D
Got
it
all
right
yeah?
So
let's
do
p3s3
for
this
as.
A
This
issue
about
the
backup
is
still
located
in
the
menu
after
disabled
it
to
reproduce
this
issue.
We
should
go
to
the
stores,
configuration
advanced
and
simple
and
disable
disable
backup
functionality,
then
clear,
cache
and
go
to
admin
panel
to
system
block,
and
we
can
see
that
block
backups
is
present
in
menu
and
and
even
we
and
when
we
move
on
to
it.
We
have
such
information
that
backup
functionality
is
disabled
and
the
pr
has
already
been
created
for
this
issue.
D
I
don't
know
if
we
want
to
do
that.
It
may
be
expected
behavior
how
it's
working
currently
like
it's
available
and
then,
when
you
click
on
it,
it
just
says
that
it's
disabled,
like
I
don't
know
if
that's
necessarily
a
bad
thing
like
I'm
thinking.
If
there's
like
multiple.
B
Okay,
it
can
confuse
customers
because,
usually
when
we
see
some
options,
it
means
that
we
can
use
it.
But
in
current
case
we
see
that
menu
item
like
backups,
but
that
I'm
not
available.
So
it's
not
make
it
not
make
sense
to
show
it
really,
because
it's
confusing
me
as
a
number.
If
I
see
some
buttons
that
I
can
click,
I
thought
that
I
can
press
it
and
then
something
quick
happens.
I
mean
it's.
B
D
That
I
basically
went
one
to
make
the
design
pattern
consistent,
so
I
think
you
guys
are
right
in
other
places
of
magento,
if
you,
if
you
disable
it,
it
would
actually
remove
the
whole
like
the
whole
clickable
link
is,
is
that
correct
or
does
it
do
something
where
it
still
shows
it?
But
then
it
says
that
it's
disabled,
or
is
this
a
an
anti-pattern.
D
D
D
Yeah
this
is,
you
know,
I
think
this
is
they're
a
lower
than
a
p3
s3.
Let
me
look.
A
A
A
And
after
that
I
change
the
shipment
id
from
url
and
we
should
use
the
id
which
does
not
exist
and
run
the
url
and,
as
a
result,
we,
the
fatal
error
page
occurs
as
we
can
see
from
the
video
when
we
change
view.
A
D
I
struggle
with
this
one
like
this
just
seems
like
it's
like
strange
behavior.
Why
would
anyone
want
to
change
the
url.
B
A
Yeah,
but
when
we
got
steps
with
order,
it's
more
correct
message
that
this
order
no
longer
exists,
and
it
also
it
with
a
shipment
and
invoice.
A
C
C
B
D
Yeah,
that's
fine.
We
can
do
this
as
a
p3
s3
then,
and
do
we
have
what
the
a
proper
like
when
changing
order?
Yeah,
that's
fine.
A
D
A
C
D
Stock,
that's
a
good
question.
I'm
not
sure
how
yeah
that's
logical,
but
I'm
not
sure
if
that's
the
expected
behavior
for
some
reason,
maybe
well
how
about.
If
someone
has
like
back
ordering
available
or
something
like
that
so
like,
if
they
had
backorder
available,
you
would
be
able
to
purchase
it,
but
then
you
know
it
would
just
be
like
a
long.
You
know
you
won't
get
it
for
two
to
three
weeks
or
something
like
that.
So
there
are.
I.
D
D
Then
that
doesn't,
could
you
do
something?
Do
a
favor
for
me:
there's
a
guy
working
on
search
right
now
and
in
product.
Did
you
ping
this
guy?
I
just
put
it
in
chat
and
see
if
he
can
think
of
any
reason
why
we
sh.
We
should
be
allowing
that
use
case
but
yeah.
It
seems
to
me
that
that
that
is
a
problem,
and
then
you
know
for
right
now
I
think
just
making
it
a
p3.
S3
is
probably
fine.
D
B
Yeah
but
but
so
yeah
is
a
little
bit
things.
I
believe
that
in
the
case
with
search
this
case
is
fully
valid,
because
in
search
we
shouldn't
be
relevant
with
out
of
stocking
stock
and
the
other
options.
We
can
show
that
almost
I
mean
by
the
search
query
most
related
to
the
output
swatch,
but
with
filtering
it's.
A
Okay,
thank
you
and
the
last
one
is
the
issue
about
failing
to
read
session
data
user
to
reproduce
this
issue,
which
should
configure
ready
server
and
set
radius
as
a
session
handler
in
environment
php.
A
Yeah
to
reproduce
this
issue,
we
should
use
the
radius
for
session
storage
with
default
settings
and
to
reproduce
the
issue
we
should
log
into
the
admin
area
open,
for
example,
16
tabs
with
the
order
page,
for
example,
in
the
order
space,
for
example,
and
click,
the
left
most
tab
and
right
click
and
right
click,
the
right
right,
most
tab
and
select
reload
reload
the
pages
at
the
same
time
same
time,
and
after
that
we
check
the
tabs
after
they
have
all
rolled
it,
and
only
as
a
result.
A
We
have
that
only
six
tabs
will
successfully
load
and
others
will
have
errors
such
this
attention.
Something
went
wrong.
A
That
means
that
six
was
successfully
load
and
tenths
attend
the
tabs.
With
this
error
and
in
the
in
the
report,
we
have
such
errors
that
warning
session
star
it
to
react,
and
it
is,
as
I
remember,
the
solution
for
this.
Its
change
radius,
max
concurrency
from
6
to
32
and.
D
A
A
I
read
that
this
case
is
used
when
compare
products
or
something.
C
B
Really
not,
but
I
think
it's
it's
looks
like
to
request
to
the
same
entity.
I
mean
they
currently
try
to
reload
the
same
entity.
I
mean
just
the
same
same
one
order.
In
the
same
time,
I
think
if
we
will
open
a
few
12
different
apps
and
try
to
reload
it,
we
will
not
receive
this
message
and
we
will
not
receive
this.
So
it's
not
really
use
case,
as
you
mentioned
in
regression
or
some
for
some
content
manager.
I
think
it's
simulated,
so
just
simulated
example
added.
C
B
C
C
D
I
think
I
think
that's
a
great
idea.
That's
that's!
That's
exactly
what
I
would
tend
to
agree
with
as
well.
D
B
Yeah
and
eager
to
mention
the
good,
the
good
things
that
I
don't
know,
but
someone
can
use
this
behavior.
I
mean
that
we
allowed
to
set
it
to
requests
for
one
user
at
the
same
time
to
broke
break
out.
The
production
store
just
set
up
some
both.
B
C
D
Yeah
I
mean
like
this
is
just
one
like
to
me.
This
is
an
edge
case.
I
don't
see
us
needing
to
fix
it.
I
mean,
if
you
guys,
think,
there's
to
me
there's
little
business
value
in
it.
I
guess
if
we
have
a
pull
request
and
we
don't
think,
there's
going
to
be
repercussions
from
this,
we
can
go
ahead
and
do
it.
I
just
like
to
me.
D
It
seems
like
something
that
doesn't
need
to
be
fixed
and
then
I'm
always
concerned
with
us
modifying
things
and
and,
like
you
know,
with
our
with
our
monolith
application
every
time
we
change
something
there
could
be
something
breaking
somewhere
else
in
it
that
relies
on
redis
that
we
didn't
think
about,
and
now
we
basically
fixed
a
very,
very
edge
case
and
now
we're
breaking
other
areas
of
the
application.
So
if
you
guys
don't
think,
there's
any
risk
in
this,
then
we
can
go
ahead
and
accept
it
if
there's
any
risk
whatsoever.