Re: [IBMiOSS] gmake: *** virtual memory exhausted. Stop.

This sounds like what is being suggested is testing on a production system. Pete mentioned he has different folders and just picks the one(s) he wants to test with at that time. What if he accidently picks the wrong folder and makes changes to production code/objects? With the advent of cloud, we can deploy a partition in 10 minutes, having independent test environments wouldn't be that difficult.

Paul Fenstermacher | Sys Admin, Sr | ETS - POWER Systems
Administration | Jack Henry & Associates, Inc.
2135 E. Primrose | Springfield, MO 65804 | 417-235-4114 x177389 |
pfenstermacher@xxxxxxxxxxxxx


-----Original Message-----
From: OpenSource [mailto:opensource-bounces@xxxxxxxxxxxx] On Behalf Of Aaron Bartell
Sent: Wednesday, July 20, 2016 12:43 PM
To: IBMi Open Source Roundtable <opensource@xxxxxxxxxxxx>
Subject: Re: [IBMiOSS] gmake: *** virtual memory exhausted. Stop.

The e-mail below is from an external source. Please do not open attachments or click links from an unknown or suspicious origin.

I would think then you wouldn't have to worry much about updates to
Node

itself.

Multiple versions are still necessary because language features are changing. For example, I might install the latest PTF with the new Node.js version but I don't want to blindly accept the PTF won't cause issues with my existing app. I would instead want to run all of my unit tests against the new version without losing the old version. There's just too many things that could go wrong (i.e. a deprecated API warning coming to full fruition and is finally removed).


Aaron Bartell
litmis.com - Services for open source on IBM i


On Wed, Jul 20, 2016 at 12:31 PM, Kevin Adler <kadler@xxxxxxxxxx> wrote:

"OpenSource" <opensource-bounces@xxxxxxxxxxxx> wrote on 07/20/2016
12:03:10 PM:

From: Aaron Bartell <aaronbartell@xxxxxxxxx>
To: IBMi Open Source Roundtable <opensource@xxxxxxxxxxxx>
Date: 07/20/2016 12:03 PM
Subject: Re: [IBMiOSS] gmake: *** virtual memory exhausted. Stop.
Sent by: "OpenSource" <opensource-bounces@xxxxxxxxxxxx>

Are bugfix versions of Node.js that unstable/unpredictable that you

have

to really have to test this stuff?

Stability is only part of the reason. There's also changes to APIs
(iToolKit/DB adapter).

Ah, didn't know there were changes to iToolkit and DB adapter APIs and
the way they ship Node is different than how we ship Python, since we
separate out the packages in to separate PTFs from the Python runtime itself.
That's unfortunate, though hopefully that gets sorted out at some point.
It would be beneficial to get these projects (iToolkit and adapter) in
npm, so you could use whichever versions you want. I would think then
you wouldn't have to worry much about updates to Node itself.

--
This is the IBMi Open Source Roundtable (OpenSource) mailing list To
post a message email: OpenSource@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/opensource
or email: OpenSource-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
http://archive.midrange.com/opensource.

--
This is the IBMi Open Source Roundtable (OpenSource) mailing list To post a message email: OpenSource@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/opensource
or email: OpenSource-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/opensource.

NOTICE: This electronic mail message and any files transmitted with it are intended
exclusively for the individual or entity to which it is addressed. The message,
together with any attachment, may contain confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or distribution
is strictly prohibited. If you have received this message in error, please
immediately advise the sender by reply email and delete all copies.