2012-02-19 100 views
8

當我把默認快遞應用的Heroku我碰到下面的錯誤。我已經確保我與Herokuku-toolbelt等最新,但它似乎是從heroku方面的錯誤?有沒有人看過這個?它推動正常,並按預期工作,但我懷疑這可能會導致未來的問題。錯誤推到的Heroku(node.js的)

Counting objects: 7, done. 
Delta compression using up to 4 threads. 
Compressing objects: 100% (3/3), done. 
Writing objects: 100% (4/4), 404 bytes, done. 
Total 4 (delta 1), reused 0 (delta 0) 

-----> Heroku receiving push 
-----> Node.js app detected 

/app/slug-compiler/buildpacks/nodejs2/vendor/json/json:425 
    return runInNewContext("(" + JSON.stringify(datum) + ")" + lookupCode); 
     ^
TypeError: Cannot read property 'node' of undefined 
    at evalmachine.<anonymous>:1:118 
    at lookupDatum (/app/slug-compiler/buildpacks/nodejs2/vendor/json/json:425:10) 
    at Socket.<anonymous> (/app/slug-compiler/buildpacks/nodejs2/vendor/json/json:628:24) 
    at Socket.emit (events.js:61:17) 
    at Socket._onReadable (net.js:656:51) 
    at IOWatcher.onReadable [as callback] (net.js:177:10) 

/app/slug-compiler/buildpacks/nodejs2/vendor/json/json:425 
    return runInNewContext("(" + JSON.stringify(datum) + ")" + lookupCode); 
     ^
TypeError: Cannot read property 'npm' of undefined 
    at evalmachine.<anonymous>:1:118 
    at lookupDatum (/app/slug-compiler/buildpacks/nodejs2/vendor/json/json:425:10) 
    at Socket.<anonymous> (/app/slug-compiler/buildpacks/nodejs2/vendor/json/json:628:24) 
    at Socket.emit (events.js:61:17) 
    at Socket._onReadable (net.js:656:51) 
    at IOWatcher.onReadable [as callback] (net.js:177:10) 
-----> Resolving engine versions 
     Using Node.js version: 0.4.7 
     Using npm version: 1.0.94 
-----> Fetching Node.js binaries 
-----> Vendoring node into slug 
-----> Installing dependencies with npm 

     [email protected] /tmp/build_1m5t2ah1oglfb/node_modules/express 
     [email protected] /tmp/build_1m5t2ah1oglfb/node_modules/express/node_modules/connect 
     [email protected] /tmp/build_1m5t2ah1oglfb/node_modules/express/node_modules/qs 
     [email protected] /tmp/build_1m5t2ah1oglfb/node_modules/express/node_modules/mime 
     [email protected] /tmp/build_1m5t2ah1oglfb/node_modules/express/node_modules/connect/node_modules/formidable 
     [email protected] /tmp/build_1m5t2ah1oglfb/node_modules/express/node_modules/mkdirp 
     [email protected] /tmp/build_1m5t2ah1oglfb/node_modules/jade 
     [email protected] /tmp/build_1m5t2ah1oglfb/node_modules/jade/node_modules/commander 
     [email protected] /tmp/build_1m5t2ah1oglfb/node_modules/jade/node_modules/mkdirp 
     Dependencies installed 
-----> Discovering process types 
     Procfile declares types -> web 
-----> Compiled slug size is 3.1MB 
-----> Launching... done, v7 
+1

是看起來對我來說太喜歡它是Heroku的錯誤。報告給他們? https://support.heroku.com/home – 2012-02-23 23:07:59

+0

需要檢查這是否仍在發生。將盡快報告。顯然,Heroku問題出在 – 2012-03-06 13:25:19

+0

。問題解決 – 2012-03-15 13:53:39

回答

1

這是一個Heroku的問題,似乎已經消失。

0

我打算在這裏一瘸一拐地說它和解析你的package.json有關。看看Specifying a version of Node.js/npm。一切都是valid JSON

我的猜測是,這是evalmachine評估您package.json在沙箱環境(見vm.runInNewContext)和lookupCode是一些方法,首先,檢查engines.node,然後engines.npm。這些都可以訪問嗎?如果這是事實,那麼可恥的Heroku的離散事件對於沒想到這個錯誤,佔它的一些有用的消息。他們通常擅長這樣的事情。

+0

沒有錯,我的東西 - 這是樣板和適用於多種環境。需要檢查這是否仍然很快發生。 – 2012-03-06 13:25:04