{ "id": "133317", "key": "ALOY-1099", "fields": { "issuetype": { "id": "1", "description": "A problem which impairs or prevents the functions of the product.", "name": "Bug", "subtask": false }, "project": { "id": "11113", "key": "ALOY", "name": "Alloy", "projectCategory": { "id": "10400", "description": "Tools for developing applications", "name": "Tooling" } }, "fixVersions": [ { "id": "15909", "description": "Alloy 1.5.0", "name": "Alloy 1.5.0", "archived": false, "released": true, "releaseDate": "2014-09-29" } ], "resolution": { "id": "1", "description": "A fix for this issue is checked into the tree and tested.", "name": "Fixed" }, "resolutiondate": "2014-11-26T19:34:16.000+0000", "created": "2014-07-17T11:29:06.000+0000", "priority": { "name": "High", "id": "2" }, "labels": [ "qe-3.3.0", "qe-manualtest" ], "versions": [ { "id": "15758", "description": "Alloy 1.4.0", "name": "Alloy 1.4.0", "archived": false, "released": true, "releaseDate": "2014-07-17" } ], "issuelinks": [], "assignee": { "name": "skypanther", "key": "skypanther", "displayName": "Tim Poulsen", "active": true, "timeZone": "America/New_York" }, "updated": "2014-11-26T19:34:16.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": "13602", "name": "Appcelerator Studio", "description": "Appcelerator Studio specific issues" } ], "description": "Code Analyzer fails to analyze Alloy Project from Studio on Windows system only. But working fine from CLI. \r\n\r\n1. Create a default alloy project.\r\n2. Execute the Code Analyzer against Android/Mobileweb platforms.\r\n\r\nActual Result - Shows error message. Please refer the attached log file and screen shot for more clarification.\r\n\r\nExpected Result - Code Analyzer should work fine for Alloy project from Studio.\r\n\r\nNotes - \r\n1. The same works fine for Classic project.\r\n2. Code Analyzer works fine for Alloy Project from CLI.\r\n3. Code Analyzer works fine for Alloy/Classic on Mac and Ubuntu systems.", "attachment": [ { "id": "49863", "filename": "alloy code analyzer fails.png", "author": { "name": "schowbey", "key": "schowbey", "displayName": "Shreya Chowbey", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2014-07-17T11:29:06.000+0000", "size": 129069, "mimeType": "image/png" }, { "id": "49864", "filename": "code analyzer fails on alloy-log file.txt", "author": { "name": "schowbey", "key": "schowbey", "displayName": "Shreya Chowbey", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2014-07-17T11:29:06.000+0000", "size": 22930, "mimeType": "text/plain" } ], "flagged": false, "summary": "Alloy: Code Analyzer fails to analyze", "creator": { "name": "schowbey", "key": "schowbey", "displayName": "Shreya Chowbey", "active": true, "timeZone": "America/Los_Angeles" }, "subtasks": [], "reporter": { "name": "schowbey", "key": "schowbey", "displayName": "Shreya Chowbey", "active": true, "timeZone": "America/Los_Angeles" }, "environment": "OS: Windows 7, 8, 8.1\r\nAppcelerator Studio, build: 3.3.0.201407111535\r\nSDK: 3.3.0.v20140711123603\r\nacs: 1.0.15\r\nalloy: 1.4.0-rc5\r\ntitanium: 3.3.0-rc4\r\ntitanium code processor: 1.1.1\r\n", "closedSprints": [ { "id": 159, "state": "closed", "name": "2014 Sprint 15 Alloy", "startDate": "2014-07-21T15:07:15.114Z", "endDate": "2014-08-04T15:07:00.000Z", "completeDate": "2014-08-02T18:09:47.110Z", "originBoardId": 124 } ], "comment": { "comments": [ { "id": "315570", "author": { "name": "pinnamuri", "key": "pinnamuri", "displayName": "Praveen Innamuri", "active": false, "timeZone": "America/Los_Angeles" }, "body": "On Mac, analyzing a Alloy project runs without any issues. However, while analyzing a Alloy project on Windows, Alloy writes the debug output onto the console along with the code processor. Since Studio expects only the output from the code processor, having the output from both Alloy and code-processors results in the parsing failure.\r\n\r\nAlloy should not output the logging on Windows, similar to Mac. Re-directing the ticket to Alloy team to suppress the output on Windows.", "updateAuthor": { "name": "pinnamuri", "key": "pinnamuri", "displayName": "Praveen Innamuri", "active": false, "timeZone": "America/Los_Angeles" }, "created": "2014-07-24T00:30:22.000+0000", "updated": "2014-07-24T00:30:22.000+0000" }, { "id": "316136", "author": { "name": "skypanther", "key": "skypanther", "displayName": "Tim Poulsen", "active": true, "timeZone": "America/New_York" }, "body": "[~pinnamuri] I think Studio might be sending the wrong launch command to Alloy. It should be something like:\r\n\r\n{{alloy compile -b -l 0 --config platform=android}}\r\n\r\nTo get no log output. The -b says \"no banner\" and -l sets the logging levels, use 0 to get no log output.\r\n\r\nIs there a way I can test this on Windows? Like, is there some config file that controls the launch settings Studios uses that I could modify?", "updateAuthor": { "name": "skypanther", "key": "skypanther", "displayName": "Tim Poulsen", "active": true, "timeZone": "America/New_York" }, "created": "2014-07-29T15:25:33.000+0000", "updated": "2014-07-29T15:25:33.000+0000" }, { "id": "316181", "author": { "name": "pinnamuri", "key": "pinnamuri", "displayName": "Praveen Innamuri", "active": false, "timeZone": "America/Los_Angeles" }, "body": "The config file used to launch code processor contains information only specific to the plugins of the code analyzer. The code analyzer doesn't explicitly invoke Alloy command to compile the source. It fires off the event \"codprocessor.pre.run\" before it starts to analyze the source code - and alloy adds the hook for this event to compile the source code.\r\n\r\nThe alloy.js file has added the hook for \"codprocessor.pre.run\" event to run before the code analyzer kicks off to analyze the source code.", "updateAuthor": { "name": "pinnamuri", "key": "pinnamuri", "displayName": "Praveen Innamuri", "active": false, "timeZone": "America/Los_Angeles" }, "created": "2014-07-29T18:29:58.000+0000", "updated": "2014-07-29T18:29:58.000+0000" }, { "id": "316311", "author": { "name": "skypanther", "key": "skypanther", "displayName": "Tim Poulsen", "active": true, "timeZone": "America/New_York" }, "body": "PR https://github.com/appcelerator/alloy/pull/495 \r\n\r\nFunctional test:\r\n\r\n1. On a Windows system, use Appcelerator Studio to create a new Alloy project.\r\n2. Right-click the project's name in the Project Explorer, choose Code Analysis, Android (or MobileWeb). Code analyzer should run without errors; you can optionally display the results by clicking on the notification in the bottom-right of the window.\r\n3. On a Macintosh system, repeat the above steps to confirm that the changes do not break anything there.\r\n\r\nNote: If using an existing project, you will need to re-install the Alloy plug-in. From the command line, in the project's directory, enter {{alloy install plugin}} prior to running the code analyzer.", "updateAuthor": { "name": "skypanther", "key": "skypanther", "displayName": "Tim Poulsen", "active": true, "timeZone": "America/New_York" }, "created": "2014-07-30T16:00:21.000+0000", "updated": "2014-07-30T16:00:21.000+0000" }, { "id": "316313", "author": { "name": "skypanther", "key": "skypanther", "displayName": "Tim Poulsen", "active": true, "timeZone": "America/New_York" }, "body": "[~fmiao] would you test this PR?", "updateAuthor": { "name": "skypanther", "key": "skypanther", "displayName": "Tim Poulsen", "active": true, "timeZone": "America/New_York" }, "created": "2014-07-30T16:10:53.000+0000", "updated": "2014-07-30T16:10:53.000+0000" }, { "id": "316394", "author": { "name": "fmiao", "key": "fmiao", "displayName": "Feon Sua Xin Miao", "active": true, "timeZone": "America/Vancouver" }, "body": "Tested on Windows, code analyzer runs with no errors. \r\nTested on Mac, looks good.", "updateAuthor": { "name": "fmiao", "key": "fmiao", "displayName": "Feon Sua Xin Miao", "active": true, "timeZone": "America/Vancouver" }, "created": "2014-07-31T05:11:49.000+0000", "updated": "2014-08-01T03:43:34.000+0000" }, { "id": "316643", "author": { "name": "skypanther", "key": "skypanther", "displayName": "Tim Poulsen", "active": true, "timeZone": "America/New_York" }, "body": "PR merged", "updateAuthor": { "name": "skypanther", "key": "skypanther", "displayName": "Tim Poulsen", "active": true, "timeZone": "America/New_York" }, "created": "2014-08-01T14:41:12.000+0000", "updated": "2014-08-01T14:41:12.000+0000" }, { "id": "320254", "author": { "name": "eharris", "key": "eharris", "displayName": "Ewan Harris", "active": true, "timeZone": "Europe/Dublin" }, "body": "Verified fix on:\r\n\r\nWindows 8.1\r\nMac OSX 10.9.4\r\nAppcelerator Studio, build: 3.4.0.201408210941\r\nTitanium SDK build: 3.4.0.v20140813022514 \r\nTitanium CLI, build: 3.4.0-dev\r\nAlloy: 1.5.0-dev\r\n\r\nCreated a new alloy project on a Windows 8.1 machine and ran code analysis on the project, the code analyzer runs with no problems. Ran the same test on a OSX 10.9.4 machine and the code analyzer runs with no problems.\r\n\r\nClosing ticket.", "updateAuthor": { "name": "eharris", "key": "eharris", "displayName": "Ewan Harris", "active": true, "timeZone": "Europe/Dublin" }, "created": "2014-08-26T01:31:01.000+0000", "updated": "2014-08-26T01:31:01.000+0000" } ], "maxResults": 8, "total": 8, "startAt": 0 } } }