Skip to content

Fix the initialization of the Locale1 service#612

Merged
imobachgs merged 1 commit intomasterfrom
fix-locale-startup-1
Jun 8, 2023
Merged

Fix the initialization of the Locale1 service#612
imobachgs merged 1 commit intomasterfrom
fix-locale-startup-1

Conversation

@imobachgs
Copy link
Copy Markdown
Contributor

@imobachgs imobachgs commented Jun 8, 2023

Until we find a better way, we need to keep the connection around. Otherwise, it will get dropped.

A better solution might be to pass a copy of the connection instead of the address to each service. But, today, let's keep the API as it is.

* Keep the connection around so it does not get dropped.
@coveralls
Copy link
Copy Markdown

Pull Request Test Coverage Report for Build 5212724549

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 75.998%

Totals Coverage Status
Change from base Build 5212520774: 0.0%
Covered Lines: 5255
Relevant Lines: 6672

💛 - Coveralls

Copy link
Copy Markdown
Contributor

@joseivanlopez joseivanlopez left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@imobachgs imobachgs merged commit 1053ca5 into master Jun 8, 2023
@imobachgs imobachgs deleted the fix-locale-startup-1 branch June 8, 2023 15:17
// When adding more services here, the order might be important.
crate::questions::start_service(ADDRESS).await?;
crate::locale::start_service(ADDRESS).await?;
let _conn = crate::locale::start_service(ADDRESS).await?;
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

btw we should document that we need to store connection, otherwise it will drop whole dbus object. So next time we do not remove it :)

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, we should document it. Additionally, trying the approach I proposed in the description might help.

@imobachgs imobachgs mentioned this pull request Aug 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants