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

PropertyStream doesn't yield value when service starts later #1111

Open
ids1024 opened this issue Oct 30, 2024 · 0 comments
Open

PropertyStream doesn't yield value when service starts later #1111

ids1024 opened this issue Oct 30, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@ids1024
Copy link
Contributor

ids1024 commented Oct 30, 2024

As mentioned in #1109 (comment).

If a (non-socket activated) service isn't running when a PropertyStream is created, the stream doesn't yield an initial value (as expected), but also doesn't yield a value once a service does start running.

Ideally the stream should also yield any time the name owner is changed.

@zeenix zeenix changed the title PropertyStream yields initial value at start if service is running, but doesn't yield value when service starts later PropertyStream doesn't yield value when service starts later Oct 30, 2024
@zeenix zeenix added the bug Something isn't working label Jan 30, 2025
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

No branches or pull requests

2 participants