Corrects method name typo in availability checks#179
Merged
Conversation
Aligns method naming for availability checks to ensure consistency and prevent potential runtime errors due to misspelled method names.
dkmstr
approved these changes
May 27, 2026
This file contains hidden or 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
2 participants
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.
This pull request makes a minor change to the Proxmox service classes by renaming the method
is_availabletois_avaliablein bothservice.pyandservice_fixed.pyto maintain consistency.is_availabletois_avaliablein theProxmoxservice implementation (server/src/uds/services/Proxmox/service.py).is_availabletois_avaliablein the fixed Proxmox service implementation (server/src/uds/services/Proxmox/service_fixed.py).DEV Explain
In metapools, if a Proxmox provider went down, changing the name correctly didn't work properly.