bugfix/retry_result: 0.0 is False

[rogerlz]

_Enter a good description of whats being changed and WHY

Checklist

• pr title makes sense
• squashed to 1 commit
• added a test case if possible
• if new feature, added to the readme
• ci is happy and green

[ThaoDChan]

Hi,

I encountered the same issue that user Turpinator described on Armchair Discord.

I tested your PR, and it worked, but I observed that z_tilt.applied was set to True after the second probing run out of a total of three runs.

After looking into the code, I believe the condition in check_retry_result can prematurely set applied to True when retry_result is a small positive float:
int(retry_result) == 0 evaluates to True for any retry_result between 0.0 and 1.0, even if error > retry_tolerance
As a result, z_tilt.applied becomes True before probing is completed.

Here's the solution I came up with:

def check_retry_result(self, retry_result):
 if (
     (isinstance(retry_result, str) and retry_result == "done")
     or (isinstance(retry_result, float) and retry_result == 0.0)
 ):
     self.applied = True
 return retry_result

This change ensures that applied is only set to True when retry_result is exactly 0.0, avoiding false positives caused by small float values.

If you have any questions or need further clarification, feel free to reach out.
My Discord username is Kingn00dles.

[turpinator]

I tried the code from @ThaoDChan and QGL is applied as expected.
After a single successful iteration at QGL, it applies.
After multiple iterations at QGL, it applies.
After a single 'non pass' iteration, QGL does not apply (expected).

[rogerlz]

thanks for the patch!