[TIMOB-13861] Code Processor: Fatal errors need to be sent to stderr, even when output format is json or stream
GitHub Issue | n/a |
---|---|
Type | Bug |
Priority | High |
Status | Closed |
Resolution | Fixed |
Resolution Date | 2013-05-15T20:46:35.000+0000 |
Affected Version/s | n/a |
Fix Version/s | 2013 Sprint 10 JS, 2013 Sprint 10, Release 3.1.1, Release 3.2.0 |
Components | Code Processor |
Labels | n/a |
Reporter | Bryan Hughes |
Assignee | Bryan Hughes |
Created | 2013-05-15T04:34:45.000+0000 |
Updated | 2013-05-29T02:17:31.000+0000 |
Description
When a fatal error occurs during parsing (anything that results in a call to process.exit()), the error needs to be hard-printed to stderr, not just to the logger (which may or may not print to stderr).
PR: https://github.com/appcelerator/titanium-code-processor/pull/184 1_0_X PR: https://github.com/appcelerator/titanium-code-processor/pull/185
Testing instructions: Run "titanium analyze -p iphone -o stream" in a directory that is not a Titanium project. With the fix, you will see "
Passes code review and functional testing. Merged both PRs.
Verified as fixed with titanium-code-processor 1.0.1-alpha3 Closing.