Restarting server with broken hot-deployed code

[myroslav]

If hot-deployed code with Syntax Error is uploaded to server (via pickup-dir) the error is logged to logs, and that is normal. However rebooting server after that makes that server fail on startup (with Syntax Error in logs) thus making impossible to hot-deploy corrected code to this server. Deployment corrected code to other server doesn't help since server does not reach point when it can accept hot-deployed code, and does not sync hot-deploy state from other servers (See #56).

[dsuch]

Right, for 1.2 I will make it so that hot-deployed modules with syntax errors (but none other) are moved to a separate directory that won't be imported when a server starts up.

For now - please delete any such hot-deployed module manually from work/hot-deploy/current [1]

[1] https://zato.io/docs/admin/guide/install-config/config-server.html#hot-deploy-current-work-dir

[dsuch]

OK, turns out it's much easier and cleaner to simply catch any errors during imports (syntax-related ones including) and log an error message. It was done in 6c85bd9 and was in fact added to the latest hotfixes a moment ago. Thanks again! :-)

https://zato.io/docs/admin/guide/hotfixes.html