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

Implement getting OCI offers #1215

Merged
merged 1 commit into from
May 15, 2024
Merged

Implement getting OCI offers #1215

merged 1 commit into from
May 15, 2024

Conversation

jvstme
Copy link
Collaborator

@jvstme jvstme commented May 13, 2024

This is another part of the Oracle Cloud Infrastructure backend implementation (#1194). Behind the OCI_BACKEND feature flag.

@jvstme jvstme requested a review from r4victor May 13, 2024 14:44
result = {}
for future in as_completed(future_to_region_name):
region_name = future_to_region_name[future]
shape_names = {shape.shape for shape in future.result()}
Copy link
Contributor

Choose a reason for hiding this comment

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

future.result() can throw exceptions. I suggest adding exception handling here.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Apparently we don't do exception handling in backends/<backend>/resources.py for any of the backends, so it is expected that these functions can raise backend-specific exceptions and the caller is responsible for handling them.

I don't see any backend-specific exception handling in <Backend>Compute.get_offers either. All exceptions raised when getting offers are handled and logged by get_offers' caller here.

@jvstme jvstme merged commit 7b5dda4 into master May 15, 2024
15 checks passed
@jvstme jvstme deleted the issue_1194_oci_get_offers branch May 15, 2024 07:21
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.

None yet

3 participants