-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
CloudDirectory: TypeError on listIndex operation #1332
Comments
@k3karthic |
The following snippet is what i am using,
|
@k3karthic |
@k3karthic |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread. |
When i try to perform a listIndex operation (with or without RangesOnIndexedValues param) on my cloud directory the following error is thrown. The issue occurs on Lambda and on Node version 6.9.4.
The same operation when performed from the aws cli returns the expected result.
OS: CentOS 7
Node: v6.9.4
AWS SDK: v2.9.0
`
{ [TypeError: must start with number, buffer, array or string]
message: 'must start with number, buffer, array or string',
code: 'TypeError',
time: Sat Jan 28 2017 01:07:18 GMT+0000 (UTC),
statusCode: 200,
retryable: false,
retryDelay: 29.344943910837173 }
TypeError: must start with number, buffer, array or string
at fromObject (buffer.js:141:11)
at new Buffer (buffer.js:62:10)
at BinaryShape.decode64 [as toType] (/var/task/node_modules/aws-sdk/lib/util.js:112:134)
at translateScalar (/var/task/node_modules/aws-sdk/lib/json/parser.js:61:16)
at translate (/var/task/node_modules/aws-sdk/lib/json/parser.js:16:21)
at Object. (/var/task/node_modules/aws-sdk/lib/json/parser.js:29:20)
at Object.each (/var/task/node_modules/aws-sdk/lib/util.js:478:32)
at translateStructure (/var/task/node_modules/aws-sdk/lib/json/parser.js:25:8)
at translate (/var/task/node_modules/aws-sdk/lib/json/parser.js:13:30)
at Object. (/var/task/node_modules/aws-sdk/lib/json/parser.js:29:20)
`
The text was updated successfully, but these errors were encountered: