-
Notifications
You must be signed in to change notification settings - Fork 1
Make stop parse info more robust #9
Comments
cURLing this locally, I don't see this error anymore. Could you push to live and we can test that way? |
deployed. last commit msg 3e737bd On Tue, Nov 11, 2014 at 7:05 AM, Ryan Y. [email protected] wrote:
Stanley Zheng |
Strange, I don't get the issue locally for 0212, but it seems the number doesn't return anything yet. What do the logs say? EDIT: I cURLed http://hrtbus.herokuapp.com/msg and got a proper response, so I don't know what to make of that. |
might help with debugging to reestablish a new ssh key with your heroku I don't think i acn be helpful on debugging right now On Tue, Nov 11, 2014 at 8:10 AM, Ryan Y. [email protected] wrote:
Stanley Zheng |
I pushed up. Where do I find application logs? Also, I can cURL the right info from live, but help gets replaced with Also, you can now put in |
oh flubber. i forget still the heroku cli its 'heroku logs -t', similar to 'tails -f you can't directly ssh without the CLI it looks like. the bad answer is to use res and dump the error on the screen. Also. On Tue, Nov 11, 2014 at 9:34 AM, Ryan Y. [email protected] wrote:
Stanley Zheng |
fixed by ryan in e2b815a |
https://github.com/Code4HR/hrt-bus-text-my-bus/blob/master/app.js/#L52
evaluation is not as expected. (Stop 0208)
The text was updated successfully, but these errors were encountered: