►
From YouTube: 2022-01-26 meeting
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).
B
B
A
I
guess
we're
just
waiting
to
see
if
chris
is
gonna
join
us.
A
A
So
I
chris
should
be
joining
us.
Oh
this,
chris,
hey.
A
Good
stuff,
so
chris
did
you
have
anything
to
bring
up
besides,
like
the
project
board
today,
no,
I.
A
A
There,
it
is
okay,
so
looks
like
we
actually
have
a
few.
There
are
six
of
these.
I
guess
start
from
the
top.
We
had
a
user
that
was
unable
to
publish
this.
Has
some
comments
on
it?
Sorry
about
that.
B
I
think
last
time
I
saw
this
issue
robert
asked
additional
questions
about
that
yeah.
This
guy
is
silent,
so
we
need
some
more
information
from.
A
A
A
C
A
Because
I
know
that
robert
put
this
one
in
so
basically
just
more
documentation,
and
so
that
could
be
linked
together.
And
this
would
just
be
the
item
that
we
put
in
the
either
beta
or
ga.
B
A
Right
yeah,
so,
should
I
put
this
at
the
bottom
of
beta
or
like
very
top
of
ga
where's
rga.
A
So
I
can
put
it
yeah.
Probably
there,
okay,
I'm
situation's,
putting
standard
out.
It
seems
like
a
beta
yep.
A
Yeah
yeah
that
makes
sense
playing
this
in
beta,
so
we
definitely
need
to.
A
Oh
you're
right,
okay,
and
that
made
sense
why
these
all
have
the
milestone
he
already
assigned
a
beta
milestone
to
these
so
yeah.
That
makes
sense.
These
are
all
just
tasks
he
already
outlined.
Okay,
you
guys.
Are
you
fine
with
us
leaving
this
here
or
should
I
put
this
in
a
more
proper,
a
different
place.
A
A
So
that's
my
thinking,
do
you
agree
with
that,
or
should
I
put
it
back
on
here?
I
don't
know
a
good
place
on
here.
Maybe
like
ongoing
or
needs
investigation
could
be
a
category.
We
have.
B
A
A
C
Yeah
so
work
in
progress.
I
think
fingers
crossed
that
the
tests
are
in
a
better
state
now,
and
so
the
tests
were
kind
of
blocking
me
for
additional
work
on
the
work
that
I'm
doing,
because
I
want
to
add,
more
we'll
potentially
add
more
profiler
tests,
some
native
tests
and
those
don't
run
until
after
the
managed
solution.
C
And
so
I
feel
like.
I
can
finally
switch
gears
back
to
the
native
tests
to
continue
on
on
the
two
issues
that
I'm
working
on.
C
Yeah,
so
I
know
that
I
was
trying
to
start
keeping
track
of
the
timing.
I
saw
for
those
tests
and
so
sometimes
I'd
see
it
take
three
and
a
half
minutes
other
times
I
saw
it,
take
four
and
a
half
minutes,
so
it
I
don't
know
how
long
it
would
have
taken
to
run
if
we
allowed
it
to
to
run
until
completion.
C
D
D
C
D
And
the
second
thing
about
this
is
I'm
just
wondering
that
it's
actually
possible,
because
previously
we
were
waiting
until
the
port
is
open.
That
means
the
iis
service
itself
is
up
and
running,
but
now
taking
out
account,
that
is,
is
taking
usually
a
lot
of
time
to
bootstrap
and
we
are
not
waiting
for
it,
but
it
works.
B
B
C
I
know
with
new
relic
we're
solving
that
problem
slightly
differently,
so
is.
Has
this
hosted
webcore
concept,
where
we're
just
using
a
command
line
to
a
small
command
line,
app
to
leverage
that
functionality,
and
basically
you
can
publish
your
web
app
to
some
folder
and
then
using
this
command
line?
App
instruct
is
to
run
out
of
that
folder
with
its
own
app,
pull
and
and
so
on,
and
so
that
way
we
can
run
things
concurrently,
but
even
then,
from
time
to
time,
there's
been
some
wonkiness
with
is
and
things
getting
locked.
A
Yeah
we
do
something
similar
with
just
is
express,
at
least
in
the
datadog
integration
tests,
and
I
don't
know
how
many
issues
we
have
with
that
now
it
used
to
be
a
big
issue
with
like
ending,
like
closing
the
processes
correctly
stuff
like
that,
but
isa
express
is
also
another
way
to
go
about
it.
D
A
D
C
A
C
Yeah,
I
don't
really
have
anything
else
to
bring
up.
I
I
think
we're
all
working
through
things
yeah
in
the
backlog
or
that
are
already
marked
as
in
flight.
C
Nice
yeah-
and
I
don't
know
if
paulo
had
a
chance
to
reach
out
to
getting
the
passcode
enabled.
Although.