Bug 789461 - Node V8 runtime causes FATAL error when used as JS runtime for site
Summary: Node V8 runtime causes FATAL error when used as JS runtime for site
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: OKD
Classification: Red Hat
Component: Website
Version: 2.x
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: ---
: ---
Assignee: Clayton Coleman
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-10 20:16 UTC by Clayton Coleman
Modified: 2015-05-15 01:03 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-09-07 19:49:05 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Clayton Coleman 2012-02-10 20:16:32 UTC 
Bug 789281 was caused when Node became available on the instance running the site: 

The website can not be acccessible, the following error came out:

Barista::CompilationError

CoffeeScript encountered an error compiling
/var/www/libra/site/app/coffeescripts/form.coffee: FATAL ERROR:
v8::Context::New() V8 is no longer usable

In order to fix the issue we specified the EXECJS_RUNTIME we wanted to use.  This defect is to investigate the FATAL error when V8 is used so that we could switch to using a single JS runtime (if Node is installed on all platforms).
Comment 1 Clayton Coleman 2012-09-07 19:49:05 UTC 
In rails 3.2 there is a specific format type required.
Note You need to log in before you can comment on or make changes to this bug.