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.

Sign up for GitHub

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

Jump to bottom

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

Open

Umaaz opened this issue Feb 5, 2024 · 0 comments

Member

Umaaz commented Feb 5, 2024

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:

Create a new plugin to act as tracepoint logger
register the plugin
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.

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