►
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
We
have
declaration
just
second,
I
need
to
open.
A
B
B
Ticket
honestly,
it
looks
like
we
need
to
close
this
ticket
because,
based
on
our
declaration,
we
should
operate
with
object.
B
Maybe
something
was
changed,
but
in
general,
when
we
was
working
on
a
synchronous,
import
and-
and
some
look
some
very
very
familiar,
but
in
generally
we
are
working
with
object
instead
of
this
array,
because
it
was
an
initial
idea
like
object.
Has
all
strict
rules
is
declaration
instead
of
arrays,
so
with
some
kind
of
contract.
B
So
we
we
can
make
one
more
look,
maybe
not
today,
but
during
between
meetings
make
you
can
look,
make
one
look
how
it's
work
now.
Maybe
something
was
changed,
but
in
general
for
me
it
looks
like
need
to
close
these
tickets
and
describe.
B
B
B
B
A
I
think
it's
yeah,
it's
more,
like
teacher
request,
isn't
like
like
a
backer,
because
you
can't
produce
objects
for
our
in
our
publisher
but
yeah.
It
looks
like
it's
requested
to
support
all
success
associated.
B
Also,
it
will
be
great
to
have
a
description
of
some
advantage
like
I.
I
don't
want
to
use
object
because
because
for
me
it's
it's,
it's
not
so
big
difference.
So
even
if
it's
a
feature
request,
I
cannot
say
that
there
are
some
big
priority.
B
A
A
A
A
B
It's
yeah,
it
should
not
be
so.
As
I
said
you
take
tickets,
so
old
it
was
created
in
2019
18,
so
I
recommend
to
recheck
on
last
code
base
because
we
had
a
lot
of
changes
during
mechanisms
of
interception
generation.
First
of
all,
it
was
related
to
performance
fixes.
Also,
there
are
was
some
fixes
to
proper
work
or
visual
types,
so
yes
need
to
recheck
this
ticket.
After
that
we
will
back,
but
in
general.
A
Like
one
like
much
after
yeah,
I'm
not
from
after.
A
B
Comments,
maybe
somebody
already
checked
it
like.
We
have
the
same
issue,
but
one
more.
A
B
B
Because
also
not
clear,
where
was
declared
this
virtual
time.
B
B
B
It's
very
interesting,
so
I
think
we
need
first
of
all,
pin
after
because
you
see
that
a
couple
of
months
ago
I
asked
the
same
question:
it's
a
big
difference.
If
you
declare
it's
the
same
front
entry,
it
will
be
one
behavior
is
the
different
area.
It
will
be
another
areas.
So
for
me
it
looks
like
very
looks
like
it's
just
a
issue
with
misconfiguration
just
wrong
plug-in
declaration.
A
A
A
A
B
A
A
A
B
First
of
all
need
to
check
current
declaration
hi,
it's
work
under
the
hood.
I
am
not
sure
that
we
can
provide
answer
right
now,
so
I
will
check
each
issue
and
will
have
some
answer
till
next
meeting,
because
it
looks
like
p2,
because
it's
very
strange,
if
you
provide
declaration
for
subscriptions
but
according
to
description
like
we
take
a
column
from
another
declaration,
so
I
would
like
to
recheck
reject
this
declaration.
How
it's
work
under
the
hood.
Maybe
there
are
makes
sense.
B
So,
first
of
all,
it's
not
clear
what
is
here
or
just
you
declare
another
column.
It's
not
work,
or
we
have
some.
I
don't
know
my
sql
error,
or
maybe
some
php
take
so
you
can
assign.
If
you
would
like
to
me-
and
I
will
recheck
this
and
provide
some
resolution
at
friday.
A
Okay,
so
let's
move
this
ticket
to
the
friday.
If
I
correct
understand,
currently,
we
will
not
set
any
priorities
already.
It
depends
on
implementation
of.
B
Also,
I
think
maybe
we
can
increase
time
like
30
minutes,
because
it's
so
hard
during
the
first
look
to
understand
what
what
is
happening
with
this
issue.