Skip to content
This repository has been archived by the owner on Jul 25, 2018. It is now read-only.

Server not starting correctly for Node 0.8 #41

Open
lonnen opened this issue May 25, 2013 · 9 comments
Open

Server not starting correctly for Node 0.8 #41

lonnen opened this issue May 25, 2013 · 9 comments

Comments

@lonnen
Copy link
Collaborator

lonnen commented May 25, 2013

It looks like the server is not actually starting for Node 0.8. When I remove web.start() we see the same failure pattern across all versions. When I explicitly add an additional web.start() to the first test or move it from the before() func into the first test the tests pass.

@lonnen lonnen mentioned this issue May 25, 2013
Closed
@lonnen
Copy link
Collaborator Author

lonnen commented May 25, 2013

The before() func is being called, the server does not appear to actually start. Strange, since it still logs the callback from the server start.

@lonnen
Copy link
Collaborator Author

lonnen commented May 25, 2013

It looks like the callback isn't being called at all. So strange. Locally I've updated to the same exact version and I still can't reproduce this.

@mythmon
Copy link
Owner

mythmon commented May 26, 2013

I ran the tests on the main Stackato instance. node --version says 0.8.14. The tests fail in the exact same way as on Travis. All of the tests involving calling Express views fail.

The API works on the same instance of CT, therefore I assume that this is purely a problem in the test harness, not the code.

@lonnen
Copy link
Collaborator Author

lonnen commented May 26, 2013

It's worth noting for posterity that the hubot plugin triggered a traceback similar to what see in these test error cases.

crimsonguardcommanders: onscreen reset Xomat

TypeError: Cannot call method 'indexOf' of undefined
at Array.exports.blacklistNoodle [as 0] (/app/app/app/modifiers.js:12:25)
at EventEmitter.ContentManager.contentForUrl (/app/app/app/manager.js:237:32)
at EventEmitter.ScreenManager.sendUrl (/app/app/app/manager.js:79:23)
at /app/app/app/web.js:43:21
at callbacks (/app/app/node_modules/express/lib/router/index.js:161:37)
at param (/app/app/node_modules/express/lib/router/index.js:135:11)
at pass (/app/app/node_modules/express/lib/router/index.js:142:5)
at Router._dispatch (/app/app/node_modules/express/lib/router/index.js:170:5)
at Object.router (/app/app/node_modules/express/lib/router/index.js:33:10)
at next (/app/app/node_modules/express/node_modules/connect/lib/proto.js:190:15)

@mythmon
Copy link
Owner

mythmon commented May 26, 2013

I don't believe that the noodle error in the last comment is related. I think this was because the hubot plugin was sending strings intended for the reset command (like "Xomat") to the sendurl api endpoint. The noodle modifier assumed it was a url and tried to parse it as such. This was since fixed.

@lonnen
Copy link
Collaborator Author

lonnen commented May 27, 2013

Aha! That makes sense too.

@lonnen
Copy link
Collaborator Author

lonnen commented Jun 9, 2013

was this fixed by dffad68?

@mythmon
Copy link
Owner

mythmon commented Jun 9, 2013

Yes, it was.

@mythmon mythmon closed this as completed Jun 9, 2013
@mythmon
Copy link
Owner

mythmon commented Jul 26, 2013

I think that the fix in dffad68 didn't actually fix the issue, as Travis still has problems with node0.8.

@mythmon mythmon reopened this Jul 26, 2013
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants