EX9 not working - Githubissues

jasnell / bluemix-workshop

Apache License 2.0

1 stars 0 forks source link

EX9 not working #3

Open cfjedimaster opened 8 years ago

cfjedimaster commented 8 years ago

Not sure what to say here. I followed the directions of setting the the environment variable via cf set-env and I restaged. I go to http://rayhelloworld.mybluemix.net/bluemix-debug/manage and I just get the default view for the app.

Also, bluemix-workshop verify rayhelloworld passes and obviously it should not.

jasnell commented 8 years ago

hmmm... ok, I'll take another look. It's possible that something changed on the bluemix side since I first put this together...

cfjedimaster commented 8 years ago

FYI, I think the issue is that you have to explicitly add the buildpack: https://developer.ibm.com/bluemix/2015/06/15/bluemix-node-js-buildpack-update/.

Checking now.

jasnell commented 8 years ago

Hmm... it shouldn't since that's the buildpack that is used by default. I'll see if I can find some time to take a look later on today.

cfjedimaster commented 8 years ago

Ok- I'm getting support in the Slack channel, so will update as I get info.

cfjedimaster commented 8 years ago

Ok, it is working now. This is what I believe the issue was. (And credit goes to various folks in the Slack channel. Any mistakes in what I say below is my fault, not theirs.)

a) You cannot use command in manifest.yml. It prevents debugging from working. b) You need more RAM to run the debug stuff. They suggested 512.

I thought I had more to add, but I think that is it.

I still can't get trace to work, but I'm still trying.

jasnell commented 8 years ago

Ok, I'll make note of those bits and get the examples updated!