-
Notifications
You must be signed in to change notification settings - Fork 503
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Extracting next engine consistently fails #622
Comments
hi , @dlculver facing the same issue , do you have a fix for this ? |
@DecentMakeover The way I solved it for myself, at least locally, was to find the particular file in the pip installed version of lavague. To get the location of lavague you need to run |
@dlculver thank you , it worked . cheers . |
@dlculver, I have the same issue. I will try your fix locally, but what do you think caused this issue to arise? I was working on a project, and didn't run lavague for several weeks. The version in my project is pinned, so not sure why this just popped up for the first time. |
When I run the WebAgent class to do a task, I consistently run into the following kind of error:
Sometimes this issue is so persistent that even after several retries the error continues. I think this is because the
extract_next_engine
utility function expects to see things like 'Next engine' and the regular expression search is case sensitive. One option would be to ignore case when doing the regular expression search. I think this should be an easy fix and would also like to volunteer to fix it.The text was updated successfully, but these errors were encountered: