Skip to content

Monolog with firephp handler doesn't work #46474

@tarlepp

Description

@tarlepp

Symfony version(s) affected

6.1.0

Description

After I updated to Symfony 6.1.0 I get following error:

Typed property Symfony\Bridge\Monolog\Handler\FirePHPHandler::$response must not be accessed before initialization

My config/packages/dev/monolog,yaml:

monolog:
    handlers:
        main:
            type: stream
            path: php://stderr
            level: debug
            channels: ['!event']
        firephp:
            type: firephp
            level: info
        chromephp:
            type: chromephp
            level: info
        console:
            type: console
            process_psr_3_messages: false
            channels: ['!event', '!doctrine', '!console']

Which seems to be correct according to recipe - https://github.com/symfony/recipes/blob/main/symfony/monolog-bundle/3.3/config/packages/dev/monolog.yaml

And if I comment out that firephp handler there all works as expected.

How to reproduce

Use following monolog configuration:

monolog:
    handlers:
        main:
            type: stream
            path: php://stderr
            level: debug
            channels: ['!event']
        firephp:
            type: firephp
            level: info
        chromephp:
            type: chromephp
            level: info
        console:
            type: console
            process_psr_3_messages: false
            channels: ['!event', '!doctrine', '!console']

Possible Solution

No response

Additional Context

No response

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      pFad - Phonifier reborn

      Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

      Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


      Alternative Proxies:

      Alternative Proxy

      pFad Proxy

      pFad v3 Proxy

      pFad v4 Proxy