Skip to content

Capturing the original error code using the Logger Callback #334

@atrbgithub

Description

@atrbgithub

Hello, lets say a logger callback was implemented, something along the lines of the example here.

Is there a way to inspect the original error code, such as ERR__TRANSPORT: -195

Currently it only seems that the message is exposed to the logger, and not the code. Currently these are logged as errors, when perhaps you might only want to log these as a warn.

Currently the only way to do this seems to be by inspecting the log message string, rather than being able to directly inspect the error code.

It would be helpful if that could be exposed in the extra object.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    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