-
Notifications
You must be signed in to change notification settings - Fork 109
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No return from getAsync... #163
Comments
Does the same happen when using dynogels by itself? Side note, this is an anti-pattern: async function foo() {
try {
await bar();
} catch (err) {
return Promise.reject(err);
}
} A thrown exception in an async function is automatically converted into rejection. Just write: async function foo() {
await bar();
} The try/catch boilerplate in your function is just adding noise and not doing anything useful. |
+1 to this issue. |
@ekf3119 With dynogels or dynogels-promisified? |
@cdhowie I'm experiencing this issue as well. Here's what I was able to get from bunyan, although I'm having a little trouble configuring the proper loglevel:
|
Here's how I ended up coding it instead... Note the |
I am using
dynogels-promisified
(so please let me know if this should be in another repo) and I have the below snippet in anasync
function but for some reason it is not returning fromdynogels
...I am running in in AWS Lambda Node.js v8.10 and the Lambda always times out waiting for the return...
dynogels.AWS.config
is set and verified with AccessKey/Secret and region.Using "dynogels-promisified@^1.0.4" and "dynogels@^9.0.0".
I get no error message and no logging that helps me track this done... Any pointers?
Thanks for a very useful package!
The text was updated successfully, but these errors were encountered: