-
Notifications
You must be signed in to change notification settings - Fork 18
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
Make DBus calls Async (2nd attempt) #608
Open
hoh
wants to merge
45
commits into
main
Choose a base branch
from
ol-dbus-async-v2
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from 42 commits
Commits
Show all changes
45 commits
Select commit
Hold shift + click to select a range
1ebf125
Problem: dbus call were not async
olethanh 13e9e6d
use mypy procotol method for typing
olethanh 421515b
fix CI, specify bus_type
olethanh 0c43547
fix init in async, isort
olethanh fc7d3da
mypy
olethanh f8c9343
dbus fast is not in debian 11
olethanh afbdd0c
Problem: dbus call were not async
olethanh 2a50080
use mypy procotol method for typing
olethanh a77cc0d
fix CI, specify bus_type
olethanh 56f43de
fix init in async, isort
olethanh ee3cfbb
mypy
olethanh dc961fc
dbus fast is not in debian 11
olethanh 4ac9099
Problem: Makefile for publishing example were not working
olethanh 18bb56f
Problem: could not start Instances from command line (#597)
olethanh 84614a5
Solve last CORS issues about duplicated headers (#604)
nesitor 5a01c42
Fix: Diagnostic API was not updated
hoh 4681906
Fix not awaited async call
olethanh e7086b2
Merge remote-tracking branch 'origin/main' into ol-dbus-async-v2
olethanh 314666b
Connect to the bus on demand to avoid having to call setup
olethanh 0c59d47
fix is running requiring async
olethanh 2e2a445
working
olethanh 067d6ee
restore
olethanh eacd7da
revert change to running
olethanh bc496dc
CI check system usage endpoint
olethanh 12743f6
add unit test for system usage
olethanh e58b9ad
add unit test for system usage
olethanh 6174c96
Set up a fresh web_app for each test as required by aiohttp
olethanh f913398
revert local compat change
olethanh fdbc765
remove force settings the loop which was causing problem with future …
olethanh f59cc5f
fix other double loop problems
olethanh 4aa3eb8
Fix inconsistant execution state
olethanh 69ed555
Remove unused loop params
olethanh 6e84b26
Apparently CI also don't have matching arch
olethanh b800612
Fix test description
olethanh 5fe46ac
Problem: allocation endpoints was not tested
olethanh 82398b9
Merge branch 'ol-test-allocation-endpoints' into ol-dbus-async-v2
olethanh 5aabea2
style
olethanh c000350
black
olethanh 975ada6
Fix bug found on debian 11 / python 3.9 droplet
olethanh 0e2ca01
Try another way to fix python 3.9 / Debian 11
olethanh bb6073c
Merge remote-tracking branch 'origin/main' into ol-dbus-async-v2
olethanh f0e7842
Merge remote-tracking branch 'origin/main' into ol-dbus-async-v2
olethanh ad0b397
Merge remote-tracking branch 'origin/main' into ol-dbus-async-v2
olethanh f6ed6ff
Merge remote-tracking branch 'origin/main' into ol-dbus-async-v2
olethanh b02c3c2
Split the systems Protocol in own module
olethanh File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IMO having different ways to check if an instance is running here or at the method used on the
VMExecution
class, can provide some issues in the future, because we don't follow always the same pattern to check it.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Currently in the is_running we actually to have two different check pattern according if we are running systemd or not, which is why I unified the is_running.
However at start up, when we rehydrate, we want to check if the Instance process is actually running an reconnect to it so it's ok to have a different logic there, at least that is munderstanding of it, please correct if I'm wrong
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You are correct, but IMO having the same way to check if a VM is running independently of the method used (systemd or direct) it's better that rehydrate fields and trust on that rehydration.