-
-
Notifications
You must be signed in to change notification settings - Fork 152
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
[#513] FIX: Fix error message thrown by selenium exceptions upon wait #512
Conversation
@yashaka apologizes that I did not create issue first, should be linked now. I edited it via GitHub UI without cloning and did not run mypy check as well - although the change is really tiny (I've checked if it's working by editing directly source files in my venv) |
based on the linters and tests, I guess it should be smth like
|
e46acb7
to
31e66b2
Compare
I have run black locally, this check should be passing now. There are ~5 tests that needs to be fixed, as the reason string changed and we do not have |
31e66b2
to
bae38aa
Compare
Modified error_messages tests, also in case there is no original error message we fallback to previous behavior of casting the error to string |
bae38aa
to
d638fcf
Compare
Currently we were casting entire exception to the string (including not readable stacktrace) from selenium to error message. Instead, we should pass just the error message
d638fcf
to
73f2d00
Compare
yes, this was something that I felt was absent... great that you found it! |
[#513] FIX: Fix error message thrown by selenium exceptions upon wait
Great, thanks! Waiting for next release 🤞 |
Currently we were casting entire exception to the string (including not readable stacktrace) from selenium to error message. Instead, we should pass just the error message.
Before:
After: