Adam Hopkins

This happens for me, too

If a map was declared outside of the main handler that stored the created serverless-mysql objects, would that work? ``` const dbMap = new Map() // Main handler function exports.handler...

I've tried setting: ``` context.callbackWaitsForEmptyEventLoop = false ``` And it still doesn't work, but I don't think that I should need to set that since I'm using an async function?

If I do `mysql.quit()` instead of `end`, my function doesn't hang, but obviously that's not great :)

From this link, it looks like maybe this is expected behavior: https://github.com/serverless/serverless/issues/470#issuecomment-205372006 And maybe it should be covered in the documentation?

Yes, anything can be the backend. PHP is just the example.

Yes

@michaelschufi I had the same issue. I had to require the image before passing it into any component, if that's what you mean.

@shadow81627 very cool! Thanks for letting me know. Starred! :)

I'm seeing a similar issue with restart, but also with stop. I see this: `systemd[1]: Stopping My Mojolicious application workers` But the worker doesn't seem to stop unless I kill...