Skip OpenAI API health checking is using OpenAI or Azure API #200
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
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.
For now if using OpenAI or Azure API with credentials specified in credentials.yaml passed via SKYNET_CREDENTIALS_PATH env variable - is_ready() will always return False and monitor_candidate_jobs() in modules\ttt\summaries\jobs.py will freeze forever in next cycle:
I've added condition which will return True in such case. This could be non-optimal (or incorrect) solution because using OpenAI/Azure API does not necessary means what local LLMs won't be used. May be (device == 'cpu') condition should be used instead, which more likely means that local LLMs are not supposed to be used.