{ "id": "113024", "key": "TIMOB-13607", "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": [], "resolution": { "id": "5", "description": "All attempts at reproducing this issue failed, or not enough information was available to reproduce the issue. Reading the code produces no clues as to why this behavior would occur. If more information appears later, please reopen the issue.", "name": "Cannot Reproduce" }, "resolutiondate": "2016-08-29T21:59:44.000+0000", "created": "2013-04-17T20:52:52.000+0000", "priority": { "name": "Low", "id": "4" }, "labels": [ "qe-3.1.1" ], "versions": [ { "id": "14162", "description": "Release 3.1.0", "name": "Release 3.1.0", "archived": true, "released": true, "releaseDate": "2013-04-16" } ], "issuelinks": [], "assignee": { "name": "emerriman", "key": "emerriman", "displayName": "Eric Merriman ", "active": true, "timeZone": "America/Los_Angeles" }, "updated": "2017-03-24T21:57:44.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": "h5. Problem description\r\n\r\nAfter updating to 3.1.0 (Alloy 1.1.0), I found out that my Alloy installed version was not reflecting the displayed version number and was not the 1.1.0 correct one, but a previous one.\r\n\r\n'alloy -v' command was displaying the correct version (1.1.0) but the code in '/usr/local/lib/node_modules/alloy/Alloy/commands/compile/index.js' @lines 330 to 343 was wrong, not reflecting changes made for 1.1.0.\r\n\r\nCleaning npm cache (sudo npm cache clean) fixed the issue and I was able to install the correct Alloy 1.1.0 version using 'sudo npm install -g alloy' command.\r\n\r\n\r\nh5. Note\r\nThe code from in '/usr/local/lib/node_modules/alloy/Alloy/commands/compile/index.js' @lines 330 to 343 should be:\r\n{code}\r\n// Load the style and update the state\r\n\t\tif (files.STYLE) {\r\n\t\t\tvar theStyles = _.isArray(files.STYLE) ? files.STYLE : [{file:files.STYLE}];\r\n\t\t\t_.each(theStyles, function(style) {\r\n\t\t\t\tif (fs.existsSync(style.file)) {\r\n\t\t\t\t\tlogger.info(' style: \"' + \r\n\t\t\t\t\t\tpath.relative(path.join(dir,CONST.DIR.STYLE),style.file) + '\"');\r\n\t\t\t\t\tstate.styles = CU.loadAndSortStyle(style.file, manifest, {\r\n\t\t\t\t\t\texistingStyle: state.styles,\r\n\t\t\t\t\t\tplatform: style.platform\r\n\t\t\t\t\t});\r\n\t\t\t\t}\r\n\t\t\t});\r\n\t\t}\r\n{code}", "attachment": [], "flagged": false, "summary": "NPM: version downloaded may not the correct one, but reports accurate version", "creator": { "name": "fcasali", "key": "fcasali", "displayName": "Federico Casali", "active": true, "timeZone": "America/Los_Angeles" }, "subtasks": [], "reporter": { "name": "fcasali", "key": "fcasali", "displayName": "Federico Casali", "active": true, "timeZone": "America/Los_Angeles" }, "environment": "NPM version 1.2.14\r\nAlloy 1.1.0\r\nTitanium 3.1.0", "comment": { "comments": [ { "id": "248007", "author": { "name": "emerriman", "key": "emerriman", "displayName": "Eric Merriman ", "active": true, "timeZone": "America/Los_Angeles" }, "body": "We are seeing this on Olga's machine. Not currently seeing this on mine. Her steps:\n1) \"sudo uninstall -g alloy\"\n2) Studio launch, prompt for install of alloy\n3) Install alloy\n4) \"alloy -v\" gets you 1.1.0\n\nCode snippet shown above not present on her machine. It is accurate on mine.\n", "updateAuthor": { "name": "emerriman", "key": "emerriman", "displayName": "Eric Merriman ", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2013-04-17T21:02:18.000+0000", "updated": "2013-04-17T21:02:18.000+0000" }, { "id": "274197", "author": { "name": "ingo", "key": "ingo", "displayName": "Ingo Muschenetz", "active": true, "timeZone": "America/Los_Angeles" }, "body": "Deferring for now as there appears to be a workaround. Likely this is a Node.js/NPM bug.", "updateAuthor": { "name": "ingo", "key": "ingo", "displayName": "Ingo Muschenetz", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2013-10-08T17:30:48.000+0000", "updated": "2013-10-08T17:30:48.000+0000" }, { "id": "394704", "author": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "body": "I tested this with NPM 3 and the globally installed Alloy and everything worked as expected. This sounds like a bug in NPM. Neither here nor there, this is pretty a non-issue with the Appc CLI and will certainly be a non-issue after we roll out the new build pipeline.", "updateAuthor": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "created": "2016-08-29T21:59:44.000+0000", "updated": "2016-08-29T21:59:44.000+0000" }, { "id": "415808", "author": { "name": "lmorris", "key": "lmorris", "displayName": "Lee Morris", "active": false, "timeZone": "America/Los_Angeles" }, "body": "Closing ticket as the issue cannot be reproduced and with reference to the previous comments.", "updateAuthor": { "name": "lmorris", "key": "lmorris", "displayName": "Lee Morris", "active": false, "timeZone": "America/Los_Angeles" }, "created": "2017-03-24T21:57:44.000+0000", "updated": "2017-03-24T21:57:44.000+0000" } ], "maxResults": 4, "total": 4, "startAt": 0 } } }