-
Notifications
You must be signed in to change notification settings - Fork 5
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
Feature: Allow User to control their VM #124
Conversation
Explanation: Highlights:
Marksdown:
The response ends with the categorization ('RED'), followed by the highlights and markdown formatting. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #124 +/- ##
=======================================
Coverage ? 84.15%
=======================================
Files ? 27
Lines ? 1130
Branches ? 188
=======================================
Hits ? 951
Misses ? 176
Partials ? 3 ☔ View full report in Codecov by Sentry. |
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.
Left a few comments.
My main remarks are on changing the pattern from callbacks to async generator, and to add typing annotation.
Failed to retrieve llama text: POST 504: 504 Gateway Time-outThe server didn't respond in time. |
Can you add tests on the new code ? |
One place hardcoded `http://`, the other one `https://`.
…l use localhost as domain
Fix: extracts domain from node url instead of sending url Fix: using vmclient sessions in get_logs instead of creating new one
fix: isort issue Fix: mypy issue Fix: black Fix: isort
Fix Fix: using real path server instead of fake server for test Fix: create playload
Isn't this whole PR missing any form of documentation '-'? |
Else tests were breaking.
When "using bundled libsecp256k1", the setup using `/tmp/venv/bin/hatch run testing:test` fails to proceed on Python 3.12. That library `secp256k1` has been unmaintained for more than 2 years now (0.14.0, Nov 6, 2021), and seems to not support Python 3.12. The error in the logs: ``` File "/tmp/pip-build-env-ye8d6ort/overlay/lib/python3.12/site-packages/setuptools/_distutils/dist.py", line 862, in get_command_obj cmd_obj = self.command_obj[command] = klass(self) ^^^^^^^^^^^ TypeError: 'NoneType' object is not callable [end of output] ``` See failing CI run: https://github.com/aleph-im/aleph-sdk-python/actions/runs/9613634583/job/26516767722
Co-authored-by: Olivier Le Thanh Duong <olivier@lethanh.be>
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.
Please wait before merging. I have encountered a few bug while testing them again the CRN.
I will provide fix for them
* Problem: A user cannot initialize an already created confidential VM. Solution: Implement `VmConfidentialClient` class to be able to initialize and interact with confidential VMs. * Problem: Auth was not working Corrections: * Measurement type returned was missing field needed for validation of measurements * Port number was not handled correctly in authentifaction * Adapt to new auth protocol where domain is moved to the operation field (While keeping compat with the old format) * Get measurement was not working since signed with the wrong method * inject_secret was not sending a json * Websocked auth was sending a twice serialized json * update 'vendorized' aleph-vm auth file from source Co-authored-by: Olivier Le Thanh Duong <olivier@lethanh.be>
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.
I have done the modification in the andres-feature-implement_confidential_vm_initialization
branch and merge dinto this one.
For me we can merge this PR. there are still some possible amelioration on the test and doc but these can be done in a sparate PR
Have you open a clickup ticket for that? |
Summary
This feature introduces new capabilities for users to manage their virtual machines (VMs) directly. The following functionalities are included: