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 on Sep 7, 2022. It is now read-only.
When I used serverless-offline-scheduler I couldn't get a response from sns.publish().promise() it's just waiting and nothing did, but when I changed function event to http it worked normally. It's kinda strange, isn't it?
The text was updated successfully, but these errors were encountered:
@ajmath seems like serverless-offline restarts when the scheduler triggers.
i'm on a windows 10 machine, and i'm using SNS offline
this is some of the stack trace
opts {
endpoint: 'http://127.0.0.1:4001',
region: 'ap-southeast-2',
httpOptions: { connectTimeout: 15000, timeout: 5000 }
}
{"message":"error in publish function","level":"error"}
{"message":"{\"message\":\"Connection timed out after 5000ms\",\"code\":\"TimeoutError\",\"time\":\"2020-01-27T07:19:30.893Z\",\"region\":\"ap-southeast-2\",\"hostname\":\"127.0.0.1\",\"retryable\":true}","level":"error"}
"undefined"
Serverless: scheduler: Succesfully run scheduled job: taskDelegator
when I call the same publish function, w/o this scheduler, I get a success.
I think this plugin somehow restarts serverless-offline(based on the stack trace, webpack builds again), then the server started by serverless-offline-sns is prevented to restart.
When I used serverless-offline-scheduler I couldn't get a response from sns.publish().promise() it's just waiting and nothing did, but when I changed function event to http it worked normally. It's kinda strange, isn't it?
The text was updated successfully, but these errors were encountered: