bespoken / bst Goto Github PK

Opening this issue to capture where this occurs so we know where to tighten code:
BSTProxy #http() Starts and Stops Correctly With Options:
Error: timeout of 2000ms exceeded. Ensure the done() callback is being called in this test.

Add any other observed cases as comments.

UPDATE - this first one should be taken care of.

Include Windows in automated testing

.git, .idea, etc.

Should allow the user to write a phrase and have it run against their skill

https://github.com/alexa/alexa-skills-kit-sdk-for-nodejs

Need to add a header into the payloads?

From the Developer console:
Error: There was a problem with your request: The intent 'LatestAudio' was not found in the domain definition. Occurred in sample 'LatestAudio latest' on line 7.

This was for a case where an intent was in the sample utterances but not in the intent list.

Ensure errors are printed out. It should also be more lenient on blank lines

Convenience method to kill background running processes

Related - figure out why commander.js starts two processes for sub-commands

People seem to do this - figure out how

Via -v flag passed to client?

Add a command to get the current version

For npm, both

$ npm -v

and

$ npm --version

provide the current version.

One candidate:
https://github.com/skywinder/github-changelog-generator

Per conversation below. We should print out any errors on loading to the console.

Additionally, may be worth considering doing this synchronously - the async loading may not be a worthwhile efficiency.

io.marco.valente @iomarcovalente 13:02
@jkelvie just to let you know that I tried the new version and it gives me this error instead

1. | Event Handlers Testing | Plays The First Podcast and Then Goes To Next:
   Error: Session must be started before calling spoken
   at Error (native)
   at Alexa.spoken (node_modules\bespoken-tools\lib\alexa\alexa.js:47:19)
   at BSTAlexa.spoken (node_modules\bespoken-tools\lib\client\bst-alexa.js:59:21)
   at Context. (test\indexSpec.js:23:11)
   at test\indexSpec.js:16:13
   at node_modules\bespoken-tools\lib\client\bst-alexa.js:34:17
   at done (node_modules\bespoken-tools\lib\alexa\interaction-model.js:27:21)
   at node_modules\bespoken-tools\lib\alexa\interaction-model.js:38:13
   at node_modules\bespoken-tools\lib\alexa\sample-utterances.js:21:17
   at ReadFileContext.callback (node_modules\bespoken-tools\lib\core\file-util.js:30:17)
   at FSReqWrap.readFileAfterOpen as oncomplete

jkelvie @jkelvie 13:04
Interesting, so the session is initialized inside the call to alexa.start()
I'm wondering if there is any error on it - if you make the callback like so:
alexa.start(function(error) {
console.log('Error: ' + error);
});
Does it print out anything?

io.marco.valente @iomarcovalente 13:08
let me try

io.marco.valente @iomarcovalente 13:13
it was my fault. I was addressing the folders incorrectly. Thank you a lot it works like a charm now!

jkelvie @jkelvie 13:14
Great!
And that may be something for us to address - I think I took out the default printing of error messages, but then that requires the implementer to go and actively print it out

http://docs.aws.amazon.com/lambda/latest/dg/nodejs-prog-model-context.html

For lambda based skills or new skills, a service endpoint may never exist or doesn't exist currently.

When generating the url using $bst proxy urlgen, there is nothing to pass for the second required argument alexa-url. Right now you just have to pass a dummy URL.

I recommend to either make it optional or remove it all together since the only thing that is actually required is the node-id.

It's time.....current dev environment should be used for testing new versions.

Also, figure out approach to using NPM for distributing test versions

bst should provide the ability to override/set the locale, both via command-line and in the API. Right now, it is currently hard-coded to "en-US":
https://github.com/bespoken/bst/blob/master/lib/alexa/service-request.ts#L120

It is annoying to have it as part of the test and coverage tasks

This is a nuisance

Exceptions should be handled and proxy should remain running

Bug in our boundary handling

To be run on first install

Currently set to one second. Try out 30 seconds instead (this should be safe)

Make sure to destroy session internally

What to do with these?

Could this work?
http://frightanic.com/computers/docker-default-container-names/

Go to http://docs.bespoken.tools/en/latest/ on mobile, the badges are 100% width of the screen.

This is what shows up now:

Error: listen EADDRINUSE :::10000
at Object.exports._errnoException (util.js:1007:11)
at exports._exceptionWithHostPort (util.js:1030:20)
at Server._listen2 (net.js:1253:14)
at listen (net.js:1289:10)
at Server.listen (net.js:1385:5)
at LambdaRunner.start (/usr/local/lib/node_modules/bespoken-tools/lib/client/lambda-runner.js:45:21)
at BSTProxy.start (/usr/local/lib/node_modules/bespoken-tools/lib/client/bst-proxy.js:52:31)
at Command. (/usr/local/lib/node_modules/bespoken-tools/bin/bst-proxy.js:45:11)
at Command.listener (/usr/local/lib/node_modules/bespoken-tools/node_modules/commander/index.js:301:8)
at emitTwo (events.js:106:13)

Just prints out the version

To ensure responses are properly handled

More sophisticated node framework

Only include essential stuff for users