{
	"id": "111576",
	"key": "TIMOB-13178",
	"fields": {
		"issuetype": {
			"id": "1",
			"description": "A problem which impairs or prevents the functions of the product.",
			"name": "Bug",
			"subtask": false
		},
		"project": {
			"id": "10153",
			"key": "TIMOB",
			"name": "Titanium SDK/CLI",
			"projectCategory": {
				"id": "10100",
				"description": "Titanium and related SDKs used in application development",
				"name": "Client"
			}
		},
		"fixVersions": [
			{
				"id": "15398",
				"description": "2013 Sprint 07 JS",
				"name": "2013 Sprint 07 JS",
				"archived": true,
				"released": true,
				"releaseDate": "2013-04-08"
			},
			{
				"id": "15105",
				"description": "2013 Sprint 07",
				"name": "2013 Sprint 07",
				"archived": true,
				"released": true,
				"releaseDate": "2013-04-08"
			}
		],
		"resolution": {
			"id": "2",
			"description": "The problem described is an issue which will never be fixed.",
			"name": "Won't Fix"
		},
		"resolutiondate": "2013-03-31T13:26:42.000+0000",
		"created": "2013-03-23T20:21:37.000+0000",
		"priority": {
			"name": "High",
			"id": "2"
		},
		"labels": [
			"qe-sdk3.1.0"
		],
		"versions": [
			{
				"id": "14162",
				"description": "Release 3.1.0",
				"name": "Release 3.1.0",
				"archived": true,
				"released": true,
				"releaseDate": "2013-04-16"
			}
		],
		"issuelinks": [
			{
				"id": "28402",
				"type": {
					"id": "10003",
					"name": "Relates",
					"inward": "relates to",
					"outward": "relates to"
				},
				"outwardIssue": {
					"id": "113064",
					"key": "TISTUD-4322",
					"fields": {
						"summary": "Node.ACS: \"Initializing Node.ACS\" process stuck at 30%.",
						"status": {
							"description": "The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.",
							"name": "Closed",
							"id": "6",
							"statusCategory": {
								"id": 3,
								"key": "done",
								"colorName": "green",
								"name": "Done"
							}
						},
						"priority": {
							"name": "High",
							"id": "2"
						},
						"issuetype": {
							"id": "1",
							"description": "A problem which impairs or prevents the functions of the product.",
							"name": "Bug",
							"subtask": false
						}
					}
				}
			},
			{
				"id": "30634",
				"type": {
					"id": "10003",
					"name": "Relates",
					"inward": "relates to",
					"outward": "relates to"
				},
				"inwardIssue": {
					"id": "116363",
					"key": "TIMOB-14387",
					"fields": {
						"summary": "Studio: Cannot update Alloy or CLI (Ti 3.0.2 -> 3.1.1)",
						"status": {
							"description": "The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.",
							"name": "Closed",
							"id": "6",
							"statusCategory": {
								"id": 3,
								"key": "done",
								"colorName": "green",
								"name": "Done"
							}
						},
						"priority": {
							"name": "Critical",
							"id": "1"
						},
						"issuetype": {
							"id": "1",
							"description": "A problem which impairs or prevents the functions of the product.",
							"name": "Bug",
							"subtask": false
						}
					}
				}
			},
			{
				"id": "27084",
				"type": {
					"id": "10003",
					"name": "Relates",
					"inward": "relates to",
					"outward": "relates to"
				},
				"inwardIssue": {
					"id": "111858",
					"key": "TISTUD-3977",
					"fields": {
						"summary": "Node.js: update to Node.js 0.8.22 with NPM 1.2.14",
						"status": {
							"description": "The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.",
							"name": "Closed",
							"id": "6",
							"statusCategory": {
								"id": 3,
								"key": "done",
								"colorName": "green",
								"name": "Done"
							}
						},
						"priority": {
							"name": "Critical",
							"id": "1"
						},
						"issuetype": {
							"id": "4",
							"description": "An improvement or enhancement to an existing feature or task.",
							"name": "Improvement",
							"subtask": false
						}
					}
				}
			}
		],
		"assignee": {
			"name": "csullivan",
			"key": "csullivan",
			"displayName": "Christian Sullivan",
			"active": true,
			"timeZone": "America/Los_Angeles"
		},
		"updated": "2017-03-22T17:26:33.000+0000",
		"status": {
			"description": "The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.",
			"name": "Closed",
			"id": "6",
			"statusCategory": {
				"id": 3,
				"key": "done",
				"colorName": "green",
				"name": "Done"
			}
		},
		"components": [
			{
				"id": "13103",
				"name": "CLI",
				"description": "Node-based command line interface"
			}
		],
		"description": "h3. Error\r\nWhen attempting to install the npm package for the CLI \"sudo npm install -g titanium@3.0.25-alpha\", I would get two lines, then the install seemed to hang:\r\n{code}\r\nnpm http GET https://registry.npmjs.org/titanium/3.0.25-alpha\r\nnpm http 304 https://registry.npmjs.org/titanium/3.0.25-alpha\r\n{code}\r\n\r\nnpm cache clean gave slightly better results:\r\n{code}\r\nnpm http GET https://registry.npmjs.org/titanium/3.0.25-alpha\r\nnpm http 200 https://registry.npmjs.org/titanium/3.0.25-alpha\r\nnpm http GET https://registry.npmjs.org/titanium/-/titanium-3.0.25-alpha.tgz\r\nnpm http 200 https://registry.npmjs.org/titanium/-/titanium-3.0.25-alpha.tgz\r\n{code}\r\n\r\nBut the CLI was not installed. We found this:\r\nhttps://github.com/isaacs/npm/issues/3058\r\n\r\nh3. Workaround:\r\nUpdate npm version with: sudo npm install npm -g\r\nThen retry install.\r\n\r\nh3. Steps to reproduce:\r\n1) Ensure you have the indicated versions of node and npm\r\n2) try to install alpha version with \"sudo npm install -g titanium@3.0.25-alpha\"\r\n\r\nh3. Result:\r\nThe install fails with 2-4 lines then hang\r\n\r\nh3. Expected:\r\nInstall succeeds",
		"attachment": [],
		"flagged": false,
		"summary": "CLI: Alpha package will not install with node v0.8.17 and npm v1.2.0 configuration",
		"creator": {
			"name": "emerriman",
			"key": "emerriman",
			"displayName": "Eric Merriman ",
			"active": true,
			"timeZone": "America/Los_Angeles"
		},
		"subtasks": [],
		"reporter": {
			"name": "emerriman",
			"key": "emerriman",
			"displayName": "Eric Merriman ",
			"active": true,
			"timeZone": "America/Los_Angeles"
		},
		"environment": "Mac OS 10.8.3\r\nNode v0.8.17\r\nnpm v1.2.0\r\n",
		"comment": {
			"comments": [
				{
					"id": "243817",
					"author": {
						"name": "emerriman",
						"key": "emerriman",
						"displayName": "Eric Merriman ",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"body": "Other QE team members data:\n\nworking as expected:\nnode: v0.8.16\nnpm: 1.1.69\n\nalso:\nnode: v0.8.3\nnpm: 1.1.43\n\nalso:\nnode: v0.10.0\nnpm: 1.2.14\n\nalso:\nnode: v0.8.17\nnpm: 1.2.15\n\nThe only configs that did not work included npm 1.2.0.",
					"updateAuthor": {
						"name": "emerriman",
						"key": "emerriman",
						"displayName": "Eric Merriman ",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"created": "2013-03-23T20:31:26.000+0000",
					"updated": "2013-03-23T20:31:26.000+0000"
				},
				{
					"id": "243828",
					"author": {
						"name": "ingo",
						"key": "ingo",
						"displayName": "Ingo Muschenetz",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"body": "We should see if there is a way _not_ to force the user to update NPM.",
					"updateAuthor": {
						"name": "ingo",
						"key": "ingo",
						"displayName": "Ingo Muschenetz",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"created": "2013-03-24T16:58:03.000+0000",
					"updated": "2013-03-24T16:58:03.000+0000"
				},
				{
					"id": "244151",
					"author": {
						"name": "dhyde",
						"key": "dhyde",
						"displayName": "Dustin Hyde",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"body": "The workaround was successful:\n\n{code}\nsudo npm install npm -g\nsudo npm install -g titanium@3.0.25-alpha\n{code}",
					"updateAuthor": {
						"name": "dhyde",
						"key": "dhyde",
						"displayName": "Dustin Hyde",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"created": "2013-03-26T19:28:54.000+0000",
					"updated": "2013-03-26T19:28:54.000+0000"
				},
				{
					"id": "244274",
					"author": {
						"name": "csullivan",
						"key": "csullivan",
						"displayName": "Christian Sullivan",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"body": "The problem is there is a bug in npm where it tries to install .gitignore as a package and is unable to resolve its package.json. See below verbose output for example full install log included also.\r\n\r\n{code}\r\nnpm verb read json /usr/local/lib/node_modules/titanium/node_modules/node_modules/package.json\r\nnpm verb read json /usr/local/lib/node_modules/titanium/node_modules/package.json/package.json\r\nnpm verb read json /usr/local/lib/node_modules/titanium/node_modules/README.md/package.json\r\n{code}\r\n\r\nThe way we would resolve this issue is by republishing the `titanium` node package with out the .gitignore\r\n\r\n{code}\r\n➜  titanium-master  npm install -g titanium@3.0.25-alpha -dd\r\nnpm info it worked if it ends with ok\r\nnpm verb cli [ '/usr/local/bin/node',\r\nnpm verb cli   '/usr/local/bin/npm',\r\nnpm verb cli   'install',\r\nnpm verb cli   '-g',\r\nnpm verb cli   'titanium@3.0.25-alpha',\r\nnpm verb cli   '-dd' ]\r\nnpm info using npm@1.2.0\r\nnpm info using node@v0.8.17\r\nnpm verb read json /usr/local/lib/package.json\r\nnpm verb read json /usr/local/lib/package.json\r\nnpm verb cache add [ 'titanium@3.0.25-alpha', null ]\r\nnpm verb parsed url { pathname: 'titanium@3.0.25-alpha',\r\nnpm verb parsed url   path: 'titanium@3.0.25-alpha',\r\nnpm verb parsed url   href: 'titanium@3.0.25-alpha' }\r\nnpm verb parsed url { pathname: '3.0.25-alpha',\r\nnpm verb parsed url   path: '3.0.25-alpha',\r\nnpm verb parsed url   href: '3.0.25-alpha' }\r\nnpm verb addNamed [ 'titanium', '3.0.25-alpha' ]\r\nnpm verb addNamed [ '3.0.25-alpha', '3.0.25-alpha' ]\r\nnpm verb lock titanium@3.0.25-alpha /Users/euforic/.npm/94ba33e8-titanium-3-0-25-alpha.lock\r\ninfo trying registry request attempt 1 at 02:23:04\r\nhttp GET https://registry.npmjs.org/titanium/3.0.25-alpha\r\nhttp 304 https://registry.npmjs.org/titanium/3.0.25-alpha\r\nnpm verb read json /Users/euforic/.npm/titanium/3.0.25-alpha/package/package.json\r\nnpm info install titanium@3.0.25-alpha into /usr/local/lib\r\nnpm info installOne titanium@3.0.25-alpha\r\nnpm verb from cache /Users/euforic/.npm/titanium/3.0.25-alpha/package/package.json\r\nnpm info /usr/local/lib/node_modules/titanium unbuild\r\nnpm verb read json /usr/local/lib/node_modules/titanium/package.json\r\nnpm verb tar unpack /Users/euforic/.npm/titanium/3.0.25-alpha/package.tgz\r\nnpm verb lock /usr/local/lib/node_modules/titanium /Users/euforic/.npm/b1e37a7e--local-lib-node-modules-titanium.lock\r\nnpm verb read json /usr/local/lib/node_modules/titanium/package.json\r\nnpm info preinstall titanium@3.0.25-alpha\r\nnpm verb from cache /usr/local/lib/node_modules/titanium/package.json\r\nnpm verb readDependencies using package.json deps\r\nnpm verb from cache /usr/local/lib/node_modules/titanium/package.json\r\nnpm verb readDependencies using package.json deps\r\nnpm verb read json /usr/local/lib/node_modules/titanium/node_modules/node_modules/package.json\r\nnpm verb read json /usr/local/lib/node_modules/titanium/node_modules/package.json/package.json\r\nnpm verb read json /usr/local/lib/node_modules/titanium/node_modules/README.md/package.json\r\n{code}",
					"updateAuthor": {
						"name": "csullivan",
						"key": "csullivan",
						"displayName": "Christian Sullivan",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"created": "2013-03-27T09:27:00.000+0000",
					"updated": "2013-03-27T09:27:59.000+0000"
				},
				{
					"id": "244467",
					"author": {
						"name": "csullivan",
						"key": "csullivan",
						"displayName": "Christian Sullivan",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"body": "One way we can avoid supporting many version of node.js and npm would be to just include the node binary and npm either in the cli tool or in a directory where the specific version can be accessed. We can also add ./bin to the users $PATHS allowing any usage of node or npm from within the folder to use the `bin`s node and npm version.\n \nexample\n\nInstall node version 0.8.15\n{code}\n$ (cd ~/.titanium && \\\n    curl -L# http://nodejs.org/dist/v0.8.15/node-v0.8.15-darwin-x86.tar.gz \\\n    | tar -zx --strip 1) \\\n   && ./bin/npm install -g alloy\n{code}\n\nShould output node v0.8.15 and npm v1.1.66\n{code}\n$ cd ~/.titanium\n$ node -v\n$ npm -v\n{code}\n\nShould output system installed version of node and npm\n{code}\n$ cd ~/\n$ node -v\n$ npm -v\n{code}",
					"updateAuthor": {
						"name": "csullivan",
						"key": "csullivan",
						"displayName": "Christian Sullivan",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"created": "2013-03-28T09:46:17.000+0000",
					"updated": "2013-03-28T09:46:17.000+0000"
				},
				{
					"id": "244812",
					"author": {
						"name": "ingo",
						"key": "ingo",
						"displayName": "Ingo Muschenetz",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"body": "We're not going to ship node with the NM package for now. For the average user, we are asking them to update to Node 0.8.22 which includes a newer version of NPM. Or they can upgrade NPM manually as noted in the workaround above.",
					"updateAuthor": {
						"name": "ingo",
						"key": "ingo",
						"displayName": "Ingo Muschenetz",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"created": "2013-03-31T13:25:06.000+0000",
					"updated": "2013-03-31T13:25:26.000+0000"
				},
				{
					"id": "414794",
					"author": {
						"name": "lmorris",
						"key": "lmorris",
						"displayName": "Lee Morris",
						"active": false,
						"timeZone": "America/Los_Angeles"
					},
					"body": "Closing ticket as the issue will not fix and with reference to the above comments.",
					"updateAuthor": {
						"name": "lmorris",
						"key": "lmorris",
						"displayName": "Lee Morris",
						"active": false,
						"timeZone": "America/Los_Angeles"
					},
					"created": "2017-03-22T17:26:33.000+0000",
					"updated": "2017-03-22T17:26:33.000+0000"
				}
			],
			"maxResults": 7,
			"total": 7,
			"startAt": 0
		}
	}
}