Retrieve Pod machine readiness info from get pod API calls #307
Conversation
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
dvejmz
force-pushed
the
get_pod_gpu_availability
branch
from
ff954e3
to
6e0cec0
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Retrieve the following additional properties of a pod (or a set of pods) machine from the runpod GraphQL API when running the
get_podorget_podscalls:This enables use cases where people want to query the readiness of their pods so they can safely and automatically launch them, scale them or send notifications when the readiness status of the pods changes.
I've updated the unit tests and ensured they all pass.
I've also addednest-asyncioto therequirements.txt, as it was missing and without it the unit tests fail. There are some unit test failures present but none of them are related to this change as they are also failing on theHEADofmain.(EDIT: nevermind about the unit tests, I had set up the project incorrectly. All unit tests pass now)