Self update command works, but displays scary error about cli

[grasmash]

This seems relevant: https://github.com/humbug/phar-updater/blob/master/README.md#avoid-post-update-file-includes

Avoid Post Update File Includes

Updating a currently running phar is made trickier since, once replaced, attempts to load files from it within a process originating from an older phar is likely to create an internal corruption of phar error. For example, if you're using Symfony Console and have created an event dispatcher for your commands, the lazy loading of some event classes will have this impact.

The solution is to disable or remove the dispatcher for your self-update command.

In general, when writing your self-update CLI commands, either pre-load any classes likely needed prior to updating, or disable their loading if not essential.

[grasmash]

Looks like the cause is...
https://github.com/acquia/cli/blob/master/bin/acli#L91-L100

[danepowell]

Right now we only use the Event Dispatcher to catch exceptions from Cloud API so it should be safe to disable as part of the self-update command... although, I don't know how to do that exactly.

Just a shot in the dark, but maybe within UpdateCommand::execute() add $this->getApplication()->setDispatcher(NULL);

[grasmash]

I'd like to move the Event Listener to a service or transform it into an Event Subscriber. https://symfony.com/doc/current/event_dispatcher.html#creating-an-event-subscriber

I can't seem to get the events to fire methods correctly.

If we do that, I think it's easier to recognize the command that was run and skip it.

[grasmash]

This is the quick solution: #170

[grasmash]

This is still an issue, though the error is a lot less scary now:

Updated from v1.0.0-beta8 to v1.0.0-rc1
Parse error: syntax error, unexpected end of file in phar:///usr/local/bin/acli/vendor/symfony/console/Event/ConsoleErrorEvent.php on line 79