Skip to content

Default tracepoint logger is set to higher priority then new custom providers #29

Description

@Umaaz

Describe the bug
Creating a new tracepoint logger for deep requires the order to be set to -1 to override the default provider.

To Reproduce
Steps to reproduce the behavior:

  1. Create a new plugin to act as tracepoint logger
  2. register the plugin
  3. it will not be used until the order is set to -1

Expected behavior
Shouldn't need to specify the order on custom plugins to override plugins that do not allow for multiple.

Desktop (please complete the following information):

  • Version [e.g. 22] main@ac1ec83e
  • Python Version [e.g. cpython 3.12] cpython 3.10

Additional context
Add any other context about the problem here.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions