-
-
Notifications
You must be signed in to change notification settings - Fork 6
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
panics in library #87
Labels
enhancement
New feature or request
Comments
Hello! This would be a fair thing to implement I think.
I think I haven't really thought about this case 😅
Please go ahead! |
kgilmer
pushed a commit
to kgilmer/runst
that referenced
this issue
Aug 6, 2023
11 tasks
Ready for review at your convenience @orhun 🌷 |
orhun
added a commit
that referenced
this issue
Aug 9, 2023
* fix: fail if cannot be primary notification server on dbus Addresses #87 * refactor(dbus): refactor error handling --------- Co-authored-by: Regolith Linux <regolith.linux@gmail.com> Co-authored-by: Orhun Parmaksız <orhunparmaksiz@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi! This issue is created as directed by
CONTRIBUTING.md
. First, I'm new to rust and found your freedesktop notification server very helpful as a project to hack on while learning the language. I am working on a fork for a DE that provides a different UI treatment for notifications. During testing I've noticed that if another notification dbus server is running, the service starts but does nothing. IMO better behavior would be to abort at this point. I'd be happy to create a PR to add this torunst
if you agree. I'd also be curious to know you reasoning if you thinkrunst
should not abort under this scenario.☮️
The text was updated successfully, but these errors were encountered: