Skip to content
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

LogLevel policies not working for new local queue of StickyHandlers #1054

Closed
MarkusTischendorf opened this issue Oct 7, 2024 · 2 comments · Fixed by #1061
Closed

LogLevel policies not working for new local queue of StickyHandlers #1054

MarkusTischendorf opened this issue Oct 7, 2024 · 2 comments · Fixed by #1061
Labels
bug Something isn't working
Milestone

Comments

@MarkusTischendorf
Copy link

When there is an implicit new local queue for StickyHandlers, the logging policies (MessageExecutionLogLevel/MessageSuccessLogLevel) are not working. If I have misunderstood or used something incorrectly, I am very sorry.

builder.Host.UseWolverine(options =>
 {
     options.Policies.MessageExecutionLogLevel(LogLevel.None);
     options.Policies.MessageSuccessLogLevel(LogLevel.None);                                
     options.Discovery.IncludeAssembly(coreAssembly);
 }, ExtensionDiscovery.ManualOnly);
[WolverineHandler]
[StickyHandler("blue")]
public class BlueHandler
{
    [WolverineHandler]
    public void Handle(MyEvent myEvent)
    {
           //...
    }        
}

[WolverineHandler]
[StickyHandler("green")]
public class GreenHandler
{
    [WolverineHandler]
    public void Handle(MyEvent myEvent)
    {
           //...
    }
}
@jeremydmiller jeremydmiller added the bug Something isn't working label Oct 10, 2024
@jeremydmiller
Copy link
Member

@MarkusTischendorf Working on the fix now. Just an oversight.

@jeremydmiller
Copy link
Member

It was really an issue of no policies of any kind catching on the special "sticky" handler chains. About to be resolved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants