-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
The server:log command does not show logs #32111
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
Comments
@lyrixx since you are the original author of |
Hello, Thanks @javiereguiluz for the ping. I missed it :) This is weird. When I implemented this command, I did not need to use |
I read again everything, and actually Anyway, I like your feeling. IMHO we should display all logs, everytime. And let the user choose what they wants thanks to --filter |
This PR was merged into the 4.4 branch. Discussion ---------- [ServerBundle] Display all logs by default | Q | A | ------------- | --- | Branch? | 4.4 | Bug fix? | no | New feature? | yes | BC breaks? | no | Deprecations? | no | Tests pass? | yes | Fixed tickets | #32111 | License | MIT | Doc PR | Instead of relying on `-vvv` behavior, we display all logs. End user has two ways of filtering now: * with the `--filter` options * by configuring the handler in `config/dev/monolog.yaml` Commits ------- 54b0809 [ServerBundle] Display all logs by default
Symfony version(s) affected: 4.2
Description
The logs are not shown while we launch
server:log
. The only way to show them is to add-vvv
option.How to reproduce
And run
server:log
.Possible Solution
The ConsoleHandler checks the verbosity level. By default the normal verbosity maps to the warning level log. IMO, the
--filter
option should be the only one responsible of the level.symfony/src/Symfony/Bundle/WebServerBundle/Command/ServerLogCommand.php
Line 146 in dca9325
Additional context
The text was updated successfully, but these errors were encountered: