Unexpected error messages in log while test passes

[ikbened]

Hi,

I build a simple RF test (open new page, click on element, wait for title to contain some text) and used your selfheal library. The click action uses a css locator which I made invalid. Although the library finds a fix and my test passes, I noticed some unexpected log errors. Here is my log:

[ ERROR ] Calling method '_start_library_keyword' of listener 'SelfHealing' failed: TimeoutError: locator.evaluate: Timeout 10000ms exceeded.
Call log:
  - waiting for locator('div.navbar-end2 ul.hidden a[href="/contact"]')

SpronQ contact :: Check contact page.                                 Keyword 'Browser.Click' with arguments '['css=div.navbar-end2 ul.hidden a[href="/contact"]']' used on line 47 failed.
Re-trying Keyword 'Click' with arguments '["css=ul.hidden a[href='/contact']"]'.
[ ERROR ] Calling method '_start_library_keyword' of listener 'SelfHealing' failed: IndexError: tuple index out of range
[ ERROR ] Calling method '_start_library_keyword' of listener 'SelfHealing' failed: IndexError: tuple index out of range
[ ERROR ] Calling method '_start_library_keyword' of listener 'SelfHealing' failed: TimeoutError: locator.evaluate: Timeout 10000ms exceeded.
Call log:
  - waiting for locator('should start with')

SpronQ contact :: Check contact page.                                 | PASS |

Are these error messages supposed to appear?

Cheers,
Ed

P.s. this is my first bug report in an open source project. Pls be a little kind to me....

[manykarim]

Hey Ed, thanks a lot for your reported issue and congrats to your first open source bug report 🙏

I need to improve the logging, but I can tell you a bit what's going on.
When a keyword fails, the self healing will try to fix the locator at the end of the keyword execution.
However, at the beginning of the keyword execution (start_library_keyword), the self healing will also check if the used locator was already healed before and if it would currently fail.
Then it will use the already healed locator, which is stored in a dictionary.
It seems like there is some problem with that part.

[manykarim]

ok, I have an idea about a possible root cause for the error.

In my requests to the LLMs (e.g. in browser_healing.py) , I send an argument
response_format = { "type": "json_object" }

I've seen in my local ollama instance, that reasoning models (in my case: deepseek) don't like that parameter and just output garbage (like \n\n\n...)

If that's really the case, I need to add a check in the beginnin, if the provided model is a reasoning model or not.

[manykarim]

Sorry, ignore my comment above.
While the problem I describe is correct, I believe it is a different root cause in your case....

Have you already played around with the Library more?
Does the problem especially happen for that broken locator css=div.navbar-end2 ul.hidden a[href="/contact"] ?