►
From YouTube: Node.js Build WG 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).
A
A
C
A
A
Sure,
okay,
that's
a
good
idea!
Yeah!
Okay!
That's
great
forgot
about
that.
So
what
do
you
want
to
start
sure.
B
I
I've
been
investigating
the
the
failures
on
arm
in
CI,
some
raspberries,
sometimes
for
with
the
one
of
two
errors:
either
they
say
that
the
slave,
the
connection
was
already
closed
and
I
think
that
happens
when
the
slave
thighs
and
the
master
tries
to
reconnect
in
the
beginning
of
the
job,
maybe
and
there's
another
failure
that
happens
in
the
beginning
or
middle
of
jobs.
That
is
about
the
object,
IV
and
there's
a
number
and
I,
don't
know
what
to
investigate
it.
Further.
B
A
A
They
seemed
to
pass
on
the
big
endian
and
the
newer
little
endian
machine
that
I
created
as
part
of
the
debugging,
so
I've
added
those
into
the
regular
runs
and
we'll
watch
those
over
the
next
day
or
so,
hopefully
hoping
that's.
You
know
we're
gonna
see
that
they're,
stable
and
things
are
going
there
I
think
that's
most
of
the
builds
specific
things.
I've
been
working
on
miles
so.
D
When
working
on
a
couple
different
things,
I've
been
working
on
an
improvement
carrying
the
gold
mine
to
use
Q
for
jobs
to
allow
for
threading,
that's
been
showing
between
200
and
400
percent,
speed
increase,
but
there's
still
some
odds
and
ends.
I
need
to
I
need
to
fix
in
there
that
aren't
quite
working
as
expected.
I've
been
working
yesterday
and
today
on
getting
the
v8
test
suite
backported
to
v4,
so
that
we
can
run
the
v8
tests
on
LTS.
D
A
A
A
A
A
C
A
Ok,
so
I'm
going
to
look
down
at
the
last
issue.
The
last
things
so
I
know
from
the
last
issue.
There
was
some
discussion
of
you
know,
I
think
the
main
concerns
was.
It
was
another
vector
for
running
code
on
the
infrastructure
and
so
understanding
the
you
know.
The
scope
and
risk
of
that
was
kind
of
the
next
step.
I
can
see
that
you
know.
Johan
has
added
a
number
of
comments,
I'm
just
going
to
read
through
to
see,
if
there's
anything
that
we
should
discuss
specifically.
C
C
A
Maybe
yeah
we
need
to
you
know
when
we
have
more
of
the
the
build
team
in
the
meeting.
Hopefully
next
time
we
should,
you
know,
discuss
if
there's
any
other
specific
concerns
or
whether
things
can
just
move
ahead
I'm.
Possibly
we
should
talk
to
William
and
see
if
that
needs
to
be
expedited,
as
opposed
to
just
waiting
for
the
next
meeting
in
the
in
the
next
few
weeks.
But
I
don't
know
if
you
know
what
do
you
guys
think?
Is
there
anything
else?
We
should
talk
about
on
that
front
now.
A
A
Yeah,
okay,
yeah!
I
don't.
I
don't
know
that.
There's
enough
context
for
the
rest
of
us
to
push
anything
order,
order
even
know
if
there's
anything
that
we
need
to
push
immediately,
but
I
guess
we
can
reach
out
to
Joanna
and
volume
just
to
see
after
this
meeting,
because
I
feel
a
little
bit
bad
that
we
can't,
you
know,
give
the
yay
or
nay,
if
there's
something
that
we're
standing
in
the
way
up.
But
ok,
let's
move
back
to
the
agenda.
D
D
On
Mac
I'm
not
sure
what
the
problems
are
on
pc,
but
I
just
want
to
kind
of
bring
up
that.
I
think
I
think
this
has
gotten
to
the
point
that
we
we
need
to
maybe
completely
rethink
the
way
in
which
we're
handling
installers
and
have
begun
to
do
some
research
and
started
an
issue
on
the
potential
of
using
electron
to
build
an
installer
and
that
that
had
a
pretty
decent
response
from
people.
D
But
it
quickly
got
feature
creeped
into
turning
into
a
new
version
of
nvm,
which
I
think
is
not
necessarily
a
bad
idea.
But
just
you
know,
we
need
to
take
things
one
step
at
a
time,
but
so
I'm
doing
research
right
now-
and
I
found
this
thing
called
electron
builder,
which
I'm
you
know
digging
into
a
little
bit,
which
is
a
complete
solution
to
package
and
deploy,
deploy.
Electron
apps
I'll
just
drop
a
link
into
the
chat
I'm,
not
a
hundred
percent.
D
Yet
because
I
haven't
gotten
it
up
and
running
if
it's
meant
for
taking
electron
apps
and
building
installer
around
it
or
if
we
can
make
an
installer
for
arbitrary
things.
But
it
seems
to
support
mac
linux
windows.
It
can
make
Deb's
rpms
Pacman's
freebsd
SDM
geez
NSI,
a
squirrel
windows
like
as
a
whole
list
of
deploy
targets
that
it
can
make,
and
I
think
that,
if
we're
able
to
somehow
get
our
installer
at
the
very
least
out
of
these,
like
really
obscure
proprietary
tools
and
built
with
javascript,
we
could
have
a
whole
bunch
of
people.
D
You
know
coming
into
a
to
support
it
and
make
it
more
robust
in
and
more
feature
complete,
so
I'm
going
to
continue
kind
of
exploring
this
and
see
if
I
can
get.
You
know,
like
a
proof
of
concept
of
something
that
can
just
you
know,
installed
node
and
maybe
nothing
more
for
right
now,
but
I'd
be
interested
in
hearing.
You
know
those
that
are
on
the
call
right
now
their
thoughts
about
that.
B
The
windows
installer
has
been
working
quite
well,
I
think
there's
an
issue
with
installation
that
I
haven't
been
able
to
replicate
and
I'm
still
waiting
for
data
to
be
able
to
fix
it
and
sometimes
issues
pop
because
of
it,
but
for
most
ish
for
most
users.
It's
not
a
huge
problem,
however,
if
there's
something
that
can
be
done
to
make
this
Oh
process
more
Millennials
one
and
so
the
pain
that
is
happening
on
OSX
them
all
shall
be
happy
to
review.
I.
C
B
D
Ok,
so
the
electron
builder
has
an
issue
in
place
for
the
msi
they
had
support
and
they
regressed
on
it.
So
my
thought
process
is
the
very
least
we
can
do
a
proof
of
concept
for
OS
x
and
then
we
can
dig
into
fixing
the
msi
stuff
and
maybe
try
to
make
a
single
place.
I
know
in
Windows
I've
been
seeing
people
posting
issues
with
like
the
Installer
just
failing
and
then
I'm
not
really
knowing
what
to
do.
D
B
It's
a
problem
about
replacing
the
performance
counters
installation,
because
somehow
there
was
some
puzzle
with
a
movie
version
of
note
that
didn't
install
just
the
performance
counters
or
there
is
a
conflict
with
some
other
software
I.
Don't
know,
though,
it
points
that
it
was
probably
some
problem
with
IDs
in
the
change
from
note
why
ojs
and
back
to
load
I'm
still
trying
to
figure
that
out.
But
if
we
tell
the
users
to
install
without
selecting
the
performance
counters,
then
the
issue
was
resolved
for
all
the
issues
that
I
have
seen
so
far.
A
D
To
be
honest,
I
have
not
dug
in
far
enough
for
that.
I
think
the
big
thing
for
me
was
mostly
just
seeing
how
much
pain
people
were
having
and
the
fact
that,
like
the
package
utility
that
we're
using
right
now
is
actually
like
deprecated,
you
can't
even
like
download
it
from
apple.
We
have
to
like
get
it
from
a
really
old
version
of
xcode
utilities,
which
is
you
know
less
than
ideal.
I
have.
A
D
Replacement
or
so
that
there
is
a
replacement
and
evan.
I
think
it
was
either
evan
or
colin
opened
an
issue
with
an
attempt
at
using
the
installer
with
the
the
new
version
of
whatever
it
is,
but
they
weren't
able
to
get
it
to
work,
and
I
like
there's
two
or
three
different
issues
or
pull
requests
that
are
open
or
there's
one.
That's
open,
there's
three
or
four
that
have
been
opened
most
have
been
closed
in
kind
of
giving
up
to
try
to
try
to
fix
this,
and
it
just
seems
to
be
a
constant
blocking
point.
D
A
C
B
C
D
Well,
I
mean
so
it
goes
in
a
couple:
different
directions:
I,
don't
think
that
we
necessarily
need
an
installer,
but
I
mean
if
we
can
deliver
a
dabber,
an
RPM
or
like
whatever
I,
don't
see
that
being
a
problem,
I've
seen
issues
opened
up
where
people
are
like
I'm
on
linux
and
I
downloaded
the
tarball.
What
do
I
do?
You
know
yeah.
C
D
D
The
thing
that
I
like
the
most
about
this
approach,
though,
is
that
even
if
we
can
use
it
to
just
solve
the
one
pain
point
that
we're
having
right
now,
which
is
OS
X
I,
like
the
idea
that
we
could
solve
that
pain,
point
and
then
open
up
a
whole
bunch
of
opportunities
and
potentials
for
us
to
explore.
Instead
of
where
we
are
right
now,
which
is
like
every
time
we
want
to
try
to
do
something.
We're
like
limited
by
the
platform.
Instead
of
you
know,
enabled
by
the
platform
yeah.
A
D
Issue
with
it
is
that
I
believe
a
chrome
like
an
electron
deploy
is
going
to
be
like
a
hundred
megabytes
right.
Okay,
so
you're
making
it
significantly
larger
and
then
that's
where
people
started
saying:
oh,
maybe
we
can
make
it
something,
that's
self-updating
and
you
only
have
to
download
it
once
and
it
can
update
your
notes
for
you
and
that's
how
it
slowly
creeps
into
like.
C
C
D
And
that's
also
like
a
place
where
it
may
be
problematic,
because
you
know
like
we're
talking
about
a
4
to
5
X
growth
in
size
for
just
like
the
base.
The
base
package
there,
which
you
know,
is
kind
of
inappropriate
in
my
opinion.
But
if
we
can
make
it
that
people
only
need
to
do
a
one-time
download,
then
maybe
you
know,
maybe
it
could
be
better.
D
A
So
I
think
we'll
call
it
a
short
meeting.
We
only
have
a
small
subset
of
us
anyway,
if
miles,
you
can
just
update
your
what
you've
done
in
the
stand-up
of
the
I.