if you mean just to upload a function and make it available to receive events from other AWS Services, then yes
Thanks
We’ll push to NPM this week along with other features
got the following:
npm ERR! Darwin 14.1.0
npm ERR! argv "node" "/usr/local/bin/npm" "install"
npm ERR! node v0.10.28
npm ERR! npm v2.7.1
npm ERR! path /Users/rantonmattei/work/dev/lambdas/node_modules/lambdaws/bin/lambdaws-cli
npm ERR! code ENOENT
npm ERR! errno 34
npm ERR! enoent ENOENT, chmod '/Users/rantonmattei/work/dev/lambdas/node_modules/lambdaws/bin/lambdaws-cli'
npm ERR! enoent This is most likely not a problem with npm itself
npm ERR! enoent and is related to npm not being able to find a file.
npm ERR! enoent1.0.11 is going through just fine
Anyone experienced that?
Secondly, I'm having an issue sometimes when i restart or re-upload the server in ebs & local. I have 3 lambda functions and on every restart i always get one of them stuck with this message:
{ [Error: Function upload to AWS Lambda timed out.] code: 'ETIMEDOUT' }
I need to manually delete the lambda function from the aws console, then restart the server in ebs and pray that it works. its kind of random and i couldn't figure out why it happens.
Can you give me a hand?
{ [Error: Function upload to AWS Lambda timed out.] code: 'ETIMEDOUT' }
I need to manually delete the lambda function from the aws console, then restart the server in ebs and pray that it works. its kind of random and i couldn't figure out why it happens.
Can you give me a hand?
@lbertenasco thanks for your support. Lambdaws will get most of my attention tomorrow during the day, I’ll try to figure out what’s happening in there.
@EFF thx! I noticed the version is also off on master in the package.json it says
Another thing that could help to debug this would be to publish the tags on github, cause it is really hard for me to know what I actually pull. (I mean npm vs. github)
"version": "1.0.10" whereas the latest is supposed to be 1.0.12 according to NPM. I'll look into that error.Another thing that could help to debug this would be to publish the tags on github, cause it is really hard for me to know what I actually pull. (I mean npm vs. github)
credentials: {
accessKey: 'MYACCESSKEY', // string, AWS AccessKeyId.
secretKey: 'MYSECRETKEY', // string, AWS AccessKeySecret.
},
role: 'arn:aws:iam::999999999999999:role/lambda_exec_role', // string, AWS ARN. Must have full access to SQS.
region: 'us-east-1',
uploadTimeout: 30000
});
@slvnperron good info, i mistakenly thought the default was 20s. i've just changed my config adding "uploadTimeout: 120000" (just to be safe) and it seems it fixed the issue.
I re-uploaded it several times to give it a good try and it does not break, thank you very much!
I re-uploaded it several times to give it a good try and it does not break, thank you very much!
I am working with S3 events
and the way the user function is called does not allow that because you call :
func.apply(this, event.args);
If I change this to
func.apply(this, [event, context]);
this works fine
so, I was about to submit a PR for that
however I ran into another issue with this line
https://github.com/mentum/lambdaws/blob/master/lib/LambdaHelper.js#L46
event.args.push(doneCallback);https://github.com/mentum/lambdaws/blob/master/lib/LambdaHelper.js#L46
because in my case, the args property is not defined
Here is the event object I get back from the invocation
[ { eventVersion: '2.0', eventSource: 'aws:s3', awsRegion: 'us-east-1', eventTime: '2015-03-18T15:40:07.417Z', eventName: 'ObjectCreated:Put', userIdentity: [Object], requestParameters: [Object], responseElements: [Object], s3: [Object] } ] }
So, that line triggers an error
Failure while running task: TypeError: Cannot call method 'push' of undefined at __lambda__ (/var/task/index.js:13:20)
In your example, you do need args
var minus = function(a, b, callback) { /*...*/ };
With S3 events you need the entire event obj and the context
var myFunc = function(event, context) { /*...*/ };
So, if I add my change, it's going to break the scenario in your example
so, here is what I suggest:
function __lambda__ (event, context) {
var utils = require('./_utils'),
callbackHandler = require('./_callbackHandler'),
externalsHandler = require('./_externalsHandler');
var doneCallback = callbackHandler.getCallback(event, context);
if (event.args) {
event.args.push(doneCallback);
}
var externals = /*externals*/null; // The external libraries to install, injected below
var func = /*user function*/null; // The user function or module to run, injected below
var runUserFunction = function() {
try {
if (event.args) {
func.apply(this, event.args);
} else {
func.apply(this, [event, context]);
}
} catch(error) {
doneCallback(utils.objectifyError(error));
}
};
try { externalsHandler.installExternals(externals, runUserFunction) }
catch(error) { doneCallback(utils.objectifyError(error)) }
}