[TIMOB-17007] CLI: Node process stuck in loop when another process is sending analytics

GitHub Issue	n/a
Type	Bug
Priority	High
Status	Closed
Resolution	Fixed
Resolution Date	2014-05-21T17:18:39.000+0000
Affected Version/s	Release 3.3.0
Fix Version/s	2014 Sprint 10, 2014 Sprint 10 Tooling, Release 3.3.0
Components	CLI
Labels	module_cli, qe-3.3.0, qe-testadded
Reporter	Samuel Dowse
Assignee	Chris Barber
Created	2014-05-21T17:00:55.000+0000
Updated	2014-07-02T06:43:57.000+0000

Description

Running 'ti project' creates a new node process and get stuck in a loop, pushing it's CPU usage to ~100%. Running 'ti project' again will create another node process. This can be repeated an endless number of times.

Steps To Reproduce

1. Use an old project that is likely to have some old unsent analytic data. 2. Run 'ti project'

Expected Result

Should send off the old data and print information about the project

Actual Result

Creates a new node process at ~100% CPU usage, and fails to send any data.

Comments

Chris Barber 2014-05-21

node-appc master pull request: https://github.com/appcelerator/node-appc/pull/92
Olga Romero 2014-05-30

Tested with Mac osx 10.9.3 Mavericks Appcelerator Studio, build: 3.3.0.201405271647 Titanium SDK, build: 3.3.0.v20140528144113 Node.JS Version: v0.10.13 NPM Version: 1.3.2 acs@1.0.14 alloy@1.4.0-beta npm@1.3.2 titanium@3.3.0-beta titanium-code-processor@1.1.1 ti project sends app data with no stuck in loop

JSON Source