From 705a9db65a230013a9118481082d2bb548cd113d Mon Sep 17 00:00:00 2001 From: Vojtech Trefny Date: Fri, 31 May 2024 06:31:52 +0200 Subject: [PATCH 06/10] fix: Fix 'possibly-used-before-assignment' pylint issues (#440) Latest pylint added a new check for values used before assignment. This fixes these issues found in the blivet module. Some of these are false positives, some real potential issues. (cherry picked from commit bfaae50586681bb4b0fcad5df6f6adde2b7c8502) --- library/blivet.py | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/library/blivet.py b/library/blivet.py index d82b86b..a6715d9 100644 --- a/library/blivet.py +++ b/library/blivet.py @@ -642,6 +642,9 @@ class BlivetVolume(BlivetBase): self._device = None return # TODO: see if we can create this device w/ the specified name + # pylint doesn't understand that "luks_fmt" is always set when "encrypted" is true + # pylint: disable=unknown-option-value + # pylint: disable=possibly-used-before-assignment def _update_from_device(self, param_name): """ Return True if param_name's value was retrieved from a looked-up device. """ log.debug("Updating volume settings from device: %r", self._device) @@ -1717,6 +1720,8 @@ class BlivetLVMPool(BlivetPool): if auto_size_dev_count > 0: calculated_thinlv_size = available_space / auto_size_dev_count + else: + calculated_thinlv_size = available_space for thinlv in thinlvs_to_create: -- 2.46.0