MarketSquare / MarketSquare/robotframework-SikuliLibrary
StartSikulli process taking longer than timeout
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 163
- Forks
- 60
- PR merge metrics
- No merged PRs in 30d
Description
Hello, I'm having some troubles when starting sikulli process in Windows 10 machines.
Sometimes, it happens that the start_sikuli_process KW "hangs", and I can only kill it by forcefully killing RF itself.
I'm yet not sure, but it seems that the java process is still there. It does not respect timeout set when importing the library.
My guess is that urlopen(url).read() in line 177 in sikulli.py is being hang, due to "blocking operations like the connection attempt". If I'm correct, setting a timeout in this operation equal to the remaining time to timeout would avoid this issue.
I'm doing more investigation in this issue, so any tips, requests of logs, or something else are greatly appreciated.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in sikuli.py at line 177 and inspect the urlopen(url).read() call within start_sikuli_process. Reproduce the Windows 10 startup hang and verify that the configured timeout is respected when the connection blocks and that the process can be stopped without forcefully killing Robot Framework.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, python
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100