-
Notifications
You must be signed in to change notification settings - Fork 13
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
Errors that occur during launch of AkkaHostedService
get eaten / not logged
#470
Labels
Comments
Aaronontheweb
added
bug
Something isn't working
akka-actor
Core Akka.NET configuration options
labels
Jun 26, 2024
Try adding this:
|
Aaronontheweb
added a commit
to Aaronontheweb/Akka.Hosting
that referenced
this issue
Sep 16, 2024
close akkadotnet#470 - application crashes and exits should always be explicitly logged someplace where they can be seen regardless of logging configuration.
4 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version Information
Version of Akka.NET? v1.5.15
Which Akka.NET Modules? Akka.Hosting
Describe the bug
Have the following code sample:
You can see where I detailed the bugs on there - the
registry.Get<IssueTrackingActor>();
call throws.However, what I see when I run this without the debugger attached is just an immediate process exit with no indication that anything went wrong. This isn't a great user experience and we need to find some way of clearly communicating that a bad thing happened to the end-user.
Crashing the process and fast-exiting is probably ok, but the user has to be given an explanation for why this happened.
Expected behavior
Some kind of error message indicating what the problem was and why my process exited.
Actual behavior
Silent failure.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment
Running via Rider F5 without the debugger attached - this where I get the silent exit.
When running via
dotnet run
on the console I get this instead:Seems like everything else startup up and ran ok there, but still no error message for the failed behavior.
The text was updated successfully, but these errors were encountered: