You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
�[1F�[2Kupdating Lambda lambda.updateFunctionCode FunctionName=pfbTilegardenStaging
�[1F�[2Kupdating Lambda lambda.setupRequestListeners
RequestEntityTooLargeException: Request must be smaller than 69905067 bytes for the UpdateFunctionCode operation
at Object.extractError (/opt/pfb/tilegarden/node_modules/aws-sdk/lib/protocol/json.js:52:27)
at Request.extractError (/opt/pfb/tilegarden/node_modules/aws-sdk/lib/protocol/rest_json.js:55:8)
at Request.callListeners (/opt/pfb/tilegarden/node_modules/aws-sdk/lib/sequential_executor.js:106:20)
at Request.emit (/opt/pfb/tilegarden/node_modules/aws-sdk/lib/sequential_executor.js:78:10)
at Request.emit (/opt/pfb/tilegarden/node_modules/aws-sdk/lib/request.js:688:14)
at Request.transition (/opt/pfb/tilegarden/node_modules/aws-sdk/lib/request.js:22:10)
at AcceptorStateMachine.runTo (/opt/pfb/tilegarden/node_modules/aws-sdk/lib/state_machine.js:14:12)
at /opt/pfb/tilegarden/node_modules/aws-sdk/lib/state_machine.js:26:10
at Request. (/opt/pfb/tilegarden/node_modules/aws-sdk/lib/request.js:38:9)
at Request. (/opt/pfb/tilegarden/node_modules/aws-sdk/lib/request.js:690:12) {
code: 'RequestEntityTooLargeException',
time: 2021-06-04T16:22:01.378Z,
requestId: 'f6b07c28-06e2-4750-afc3-fd685047d4a5',
statusCode: 413,
retryable: false,
retryDelay: 2.1909554746327276
}
It worked a few months ago, so something in the dependencies must have grown since then and pushed the package over the size limit. So that's a bummer. We'll have to see if there are any dependencies we can trim or some other way to shrink the package.
The text was updated successfully, but these errors were encountered:
KlaasH
changed the title
Tilegarden lambda package too large
Tilegarden Lambda package too large
Jun 4, 2021
A CI deploy to staging just failed with:
It worked a few months ago, so something in the dependencies must have grown since then and pushed the package over the size limit. So that's a bummer. We'll have to see if there are any dependencies we can trim or some other way to shrink the package.
The text was updated successfully, but these errors were encountered: