Using lld with my project is cumbersome, because each time I create or remove lld session it fails due to TooManyRequestsException. Retrying manually solves the issue.
Stack trace
```
Error: Failed to update add layer to lambda [REDACTED].
at addLayerToLambda (file:///path/to/repo/node_modules/lambda-live-debugger/dist/infraDeploy.mjs:576:15)
at process.processTicksAndRejections (node:internal/process/task_queues:104:5)
at async Promise.all (index 50)
at async Object.applyAddingInfra (file:///path/to/repo/node_modules/lambda-live-debugger/dist/infraDeploy.mjs:348:5)
at async run (file:///path/to/repo/node_modules/lambda-live-debugger/dist/lldebugger.mjs:201:5) {
[cause]: TooManyRequestsException: Rate exceeded
at AwsRestJsonProtocol.handleError (/path/to/repo/node_modules/@aws-sdk/core/dist-cjs/submodules/protocols/index.js:934:27)
at process.processTicksAndRejections (node:internal/process/task_queues:104:5)
at async AwsRestJsonProtocol.deserializeResponse (/path/to/repo/node_modules/@smithy/core/dist-cjs/submodules/protocols/index.js:341:13)
at async AwsRestJsonProtocol.deserializeResponse (/path/to/repo/node_modules/@aws-sdk/core/dist-cjs/submodules/protocols/index.js:918:24)
at async /path/to/repo/node_modules/@smithy/core/dist-cjs/submodules/schema/index.js:25:24
at async /path/to/repo/node_modules/@smithy/core/dist-cjs/index.js:118:20
at async /path/to/repo/node_modules/@smithy/core/dist-cjs/submodules/retry/index.js:172:50
at async /path/to/repo/node_modules/@aws-sdk/core/dist-cjs/submodules/client/index.js:119:26
at async updateLambda (file:///path/to/repo/node_modules/lambda-live-debugger/dist/infraDeploy.mjs:604:5)
at async addLayerToLambda (file:///path/to/repo/node_modules/lambda-live-debugger/dist/infraDeploy.mjs:573:9) {
'$fault': 'client',
'$retryable': undefined,
'$metadata': {
httpStatusCode: 429,
requestId: '[REDACTED]',
extendedRequestId: undefined,
cfId: undefined,
attempts: 3,
totalRetryDelay: 427
},
retryAfterSeconds: undefined,
Type: 'User',
Reason: 'CallerRateLimitExceeded'
}
}
```
I suggest using built-in AWS SDK retry mechanism to make the process more seamless.
Using
lldwith my project is cumbersome, because each time I create or remove lld session it fails due toTooManyRequestsException. Retrying manually solves the issue.Stack trace
``` Error: Failed to update add layer to lambda [REDACTED]. at addLayerToLambda (file:///path/to/repo/node_modules/lambda-live-debugger/dist/infraDeploy.mjs:576:15) at process.processTicksAndRejections (node:internal/process/task_queues:104:5) at async Promise.all (index 50) at async Object.applyAddingInfra (file:///path/to/repo/node_modules/lambda-live-debugger/dist/infraDeploy.mjs:348:5) at async run (file:///path/to/repo/node_modules/lambda-live-debugger/dist/lldebugger.mjs:201:5) { [cause]: TooManyRequestsException: Rate exceeded at AwsRestJsonProtocol.handleError (/path/to/repo/node_modules/@aws-sdk/core/dist-cjs/submodules/protocols/index.js:934:27) at process.processTicksAndRejections (node:internal/process/task_queues:104:5) at async AwsRestJsonProtocol.deserializeResponse (/path/to/repo/node_modules/@smithy/core/dist-cjs/submodules/protocols/index.js:341:13) at async AwsRestJsonProtocol.deserializeResponse (/path/to/repo/node_modules/@aws-sdk/core/dist-cjs/submodules/protocols/index.js:918:24) at async /path/to/repo/node_modules/@smithy/core/dist-cjs/submodules/schema/index.js:25:24 at async /path/to/repo/node_modules/@smithy/core/dist-cjs/index.js:118:20 at async /path/to/repo/node_modules/@smithy/core/dist-cjs/submodules/retry/index.js:172:50 at async /path/to/repo/node_modules/@aws-sdk/core/dist-cjs/submodules/client/index.js:119:26 at async updateLambda (file:///path/to/repo/node_modules/lambda-live-debugger/dist/infraDeploy.mjs:604:5) at async addLayerToLambda (file:///path/to/repo/node_modules/lambda-live-debugger/dist/infraDeploy.mjs:573:9) { '$fault': 'client', '$retryable': undefined, '$metadata': { httpStatusCode: 429, requestId: '[REDACTED]', extendedRequestId: undefined, cfId: undefined, attempts: 3, totalRetryDelay: 427 }, retryAfterSeconds: undefined, Type: 'User', Reason: 'CallerRateLimitExceeded' } } ```I suggest using built-in AWS SDK retry mechanism to make the process more seamless.