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
{{ message }}
This repository has been archived by the owner. It is now read-only.
I just encountered, a bug when I tried to deploy a new release of my Lambda. You can find the trace below. The weird thing is, when I retried just after, everything went smooth.
Have you encountered any of this yet ?
Thanks !
Unhandled rejection UnknownEndpoint: Inaccessible host: `dynamodb.eu-central-1.amazonaws.com'. This service may not be available in the `eu-central-1' region.
at Request.ENOTFOUND_ERROR (C:\XXXXX\YYYY\ZZZZZ\node_modules\serverless-dynamodb-pitr\node_modules\a
ws-sdk\lib\event_listeners.js:456:46)
at Request.callListeners (C:\XXXXX\YYYY\ZZZZZ\node_modules\serverless-dynamodb-pitr\node_modules\aws
-sdk\lib\sequential_executor.js:105:20)
at Request.emit (C:\XXXXX\YYYY\ZZZZZ\node_modules\serverless-dynamodb-pitr\node_modules\aws-sdk\lib\
sequential_executor.js:77:10)
at Request.emit (C:\XXXXX\YYYY\ZZZZZ\node_modules\serverless-dynamodb-pitr\node_modules\aws-sdk\lib\
request.js:683:14)
at ClientRequest.error (C:\XXXXX\YYYY\ZZZZZ\node_modules\serverless-dynamodb-pitr\node_modules\aws-s
dk\lib\event_listeners.js:295:22)
at ClientRequest.<anonymous> (C:\XXXXX\YYYY\ZZZZZ\node_modules\serverless-dynamodb-pitr\node_modules
\aws-sdk\lib\http\node.js:89:19)
at emitOne (events.js:96:13)
at ClientRequest.emit (events.js:188:7)
at TLSSocket.socketErrorListener (_http_client.js:309:9)
at emitOne (events.js:96:13)
at TLSSocket.emit (events.js:188:7)
at connectErrorNT (net.js:1025:8)
at _combinedTickCallback (internal/process/next_tick.js:80:11)
at process._tickDomainCallback (internal/process/next_tick.js:128:9)
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi everyone,
I just encountered, a bug when I tried to deploy a new release of my Lambda. You can find the trace below. The weird thing is, when I retried just after, everything went smooth.
Have you encountered any of this yet ?
Thanks !
The text was updated successfully, but these errors were encountered: