Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FrameworkBundle] backport more error information from 2.6 to 2.3 #11856

Merged
merged 1 commit into from Sep 5, 2014

Conversation

xabbuh
Copy link
Member

@xabbuh xabbuh commented Sep 5, 2014

Q A
Bug fix? yes
New feature? no
BC breaks? no
Deprecations? no
Tests pass? yes
Fixed tickets #11724
License MIT
Doc PR

The commit on master was:

server:run command: provide more error information

The server:run command didn't provide many information when the executed
command exited unexpectedly. Now, the process' exit code is passed through
and an error message is displayed.
@xabbuh xabbuh changed the title backport more error information from 2.6 to 2.3 [FrameworkBundle] backport more error information from 2.6 to 2.3 Sep 5, 2014
@romainneutron
Copy link
Contributor

👍

1 similar comment
@stof
Copy link
Member

stof commented Sep 5, 2014

👍

@fabpot
Copy link
Member

fabpot commented Sep 5, 2014

Thank you @xabbuh.

@fabpot fabpot merged commit 87449e0 into symfony:2.3 Sep 5, 2014
fabpot added a commit that referenced this pull request Sep 5, 2014
… to 2.3 (xabbuh)

This PR was merged into the 2.3 branch.

Discussion
----------

[FrameworkBundle] backport more error information from 2.6 to 2.3

| Q             | A
| ------------- | ---
| Bug fix?      | yes
| New feature?  | no
| BC breaks?    | no
| Deprecations? | no
| Tests pass?   | yes
| Fixed tickets | #11724
| License       | MIT
| Doc PR        |

Commits
-------

87449e0 backport more error information from 2.6 to 2.3
@xabbuh xabbuh deleted the issue-11724 branch September 5, 2014 08:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants