-
Notifications
You must be signed in to change notification settings - Fork 26
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
Wait 5s after UI robot types in a config file #1051
Conversation
Let's wait and see how things go with a fix for redhat-developer/lsp4ij#577 |
b0e6ff9
to
94f0d33
Compare
Signed-off-by: Paul Gooderham <turkeyonmarblerye@gmail.com>
94f0d33
to
1dac83f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good and nice to see the green Windows build. Thanks!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes look good and green builds look even better. Can you please add some comments to the sleep lines to explain why they are needed?
To be clear, we believe this PR combined with this fix in LSP4IJ - redhat-developer/lsp4ij#587 - will ultimately resolve the server.env test failure as reported in #945. |
Signed-off-by: Paul Gooderham <turkeyonmarblerye@gmail.com>
Check in tomorrow! 🕥 |
10/31 Linux failure due to Liberty hung error. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. Thanks.
The diagnostic fails to appear in the editor because the robot clicks on the editor tab immediately after typing the value (after the equals. sign). A bug or feature in IntelliJ makes it give up on the unrendered diagnostic when the user turns attention somewhere else.
Here is how I decided on the amount of time to wait. It may take 1s so I doubled it. On Mac it might be slow so I doubled it again and rounded up.
This fix relies on using the LCLS 2.2-SNAPSHOT. I do not include it here because someone else has been testing this and will make a separate pull request. Here is the test result when you do use 2.2-snapshot:
Fixes #945