Titanium JIRA Archive
Titanium SDK/CLI (TIMOB)

[TIMOB-13491] CodeProcessor: Hack around messaging limitation

GitHub Issuen/a
TypeBug
PriorityCritical
StatusClosed
ResolutionFixed
Resolution Date2013-04-09T17:28:05.000+0000
Affected Version/sRelease 3.0.0
Fix Version/sRelease 3.1.0, 2013 Sprint 08 JS, 2013 Sprint 08
ComponentsCode Processor
Labelscode-analyzer, qe-testadded
ReporterBryan Hughes
AssigneeBryan Hughes
Created2013-04-09T00:40:59.000+0000
Updated2013-12-03T20:59:02.000+0000

Description

The messaging protocol is broken in node 0.10, and I can't find a way around it. For now, the safest option is to simply remove it and instead just dump the results straight to the console. Fortunately studio isn't using any features of the messaging protocol that precludes this move. Hopefully this will fix TISTUD-4148. If not, it will at least unblock testing.

Comments

  1. Bryan Hughes 2013-04-09

    PR: https://github.com/appcelerator/titanium-code-processor/pull/155
  2. Bryan Hughes 2013-04-09

    1_0_X backport: https://github.com/appcelerator/titanium-code-processor/pull/156
  3. Shyam Bhadauria 2013-05-09

    Is there any way to verify this?
  4. Bryan Hughes 2013-05-09

    @Shyam Yes, check if the code processor works in Appcelerator Studio :) This bug workaround prevented it from working at all.
  5. Shyam Bhadauria 2013-05-10

    Code processor is working now.So closing this bug. Used environment for verification SDK - 3.1.0.GA Appcelerator Studio : 3.1.1.201305072102 Titanium Code Processor v1.0.0

JSON Source