Skip to content

Conversation

@kbond
Copy link
Member

@kbond kbond commented Nov 10, 2017

Q A
Branch? 3.4
Bug fix? yes
New feature? no
BC breaks? no
Deprecations? no
Tests pass? yes
Fixed tickets #24885
License MIT
Doc PR n/a

When the cache is cleared between server:start and server:stop the container used in server:start is no longer valid. Firing the console.terminate event throws an exception. This PR clears the event dispatcher so console.terminate is not fired.

@fabpot
Copy link
Member

fabpot commented Nov 10, 2017

Thank you @kbond.

@fabpot fabpot merged commit 699339e into symfony:3.4 Nov 10, 2017
fabpot added a commit that referenced this pull request Nov 10, 2017
…ed when server:start finishes (kbond)

This PR was merged into the 3.4 branch.

Discussion
----------

[WebServerBundle] Prevent console.terminate from being fired when server:start finishes

| Q             | A
| ------------- | ---
| Branch?       | 3.4
| Bug fix?      | yes
| New feature?  | no
| BC breaks?    | no
| Deprecations? | no
| Tests pass?   | yes
| Fixed tickets | #24885
| License       | MIT
| Doc PR        | n/a

When the cache is cleared between `server:start` and `server:stop` the container used in `server:start` is no longer valid. Firing the `console.terminate` event throws an exception. This PR clears the event dispatcher so `console.terminate` is not fired.

Commits
-------

699339e [WebServerBundle] prevent console.terminate from being fired after stopping server
This was referenced Nov 12, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants