Skip to content
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

"Add and Run JupyterLab Code Cell" keyword throws error intermittently #58

Closed
chidambaranathan-r opened this issue Mar 8, 2022 · 3 comments

Comments

@chidambaranathan-r
Copy link

robotframework==4.0.3
robotframework-jupyterlibrary==0.3.1
Jupyterlab version: 3.2.8

Observation:

While we try to use the keyword "Add and Run JupyterLab Code Cell", sometimes it works and sometimes it throws the below error:

ElementNotInteractableException: Message: Element <svg> could not be scrolled into view
Stacktrace:
WebDriverError@chrome://remote/content/shared/webdriver/Errors.jsm:183:5
ElementNotInteractableError@chrome://remote/content/shared/webdriver/Errors.jsm:293:5
webdriverClickElement@chrome://remote/content/marionette/interaction.js:156:11
interaction.clickElement@chrome://remote/content/marionette/interaction.js:125:11
clickElement@chrome://remote/content/marionette/actors/MarionetteCommandsChild.jsm:203:24
receiveMessage@chrome://remote/content/marionette/actors/MarionetteCommandsChild.jsm:91:31

Attached the screenshots for reference.
Screenshot_1
Screenshot_2

@chidambaranathan-r chidambaranathan-r changed the title "Add and Run JupyterLab Code Cell" keyword throws error "Add and Run JupyterLab Code Cell" keyword throws error intermittently Mar 8, 2022
@bollwyvl
Copy link
Collaborator

bollwyvl commented Mar 8, 2022

It's probably trying to click on the run button in the notebook behind it. #47 theoretically fixes these, but still has a ways to go.

For now, if you ensure you only have one notebook open, it should work more reliably.

@chidambaranathan-r
Copy link
Author

Thank you for the suggestion @bollwyvl

I used the keyword "Close All JupyterLab Tabs" in all the test case as a teardown, to ensure when a test case runs, it will have its own (one and only) notebook. I guess, it helped to overcome the above challenge that I reported.

@chidambaranathan-r
Copy link
Author

As using "Close All JupyterLab Tabs" solved my issue, closing this comment.
Will follow-up on the #47

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants