Initializing gauge connection to x framework.jar #1896
Comments
|
Hi guys, We have the same issue as described above. Would be helpful to receive any feedback on how to solve it as it blocks our time a lot |
Hi, I'm having this issue too. |
|
Just wanted to point out that I have tried to replicate this issue since it was first logged, but have been unsuccessful. I will spend some more time on this (since many of you are having trouble because of this), but it's going to be a guessing game without a project for me to replicate the issue. |
Hello sriv, Thank you for taking the time to reproduce this, unfortunately I'm unable to share anything from the project due to sensitive information but if there is anything that you might need such as logs, screenshots, info, let me know and I would gladly post them here. Thank you! |
|
Hi @Displazya and others who faced this issue (@AdrianaVirdol @AlinVezeanu @Sebbiv) - Could you please try out something and let me know if it help?
Please check if this helps fix this issue and Gauge plugins features work well. |
|
Hi @sriv, Unfortunately this did not solve the issue for us. |
|
Hello @sriv, I have tried installing gauge using both .zip and setup in various locations with the same result. Currently for me it is installed (using the setup version) using Admin rights in C:\Program Files\Gauge with full permissions for my user. Prior to this, it was installed using the .zip artifact in C:\Users<user>\gauge. The Gauge Binary Path is set to -> C:\Program Files\Gauge\bin\gauge.exe The issues still occurs :( Thank you, |
|
I have tried multiple combinations of gauge, gauge-java, intellij IDEA, gauge intellij plugin and JDK 11,12,14, 16 for the past few days. I setup a new windows machine, and am on Windows 10. Here's my gauge version: I have tried the sample projects ( None of the above have caused the issue that you have mentioned. So I suspect it could be either related to your environment or project. @Displazya - you should probably not set @Sebbiv / @Displazya - could you try to clone Thank you for your patience. |
|
Hello @sriv, First of all thank you for investigating this issue. It seems that it is an environment issue because the issue is present even in the https://github.com/getgauge/gauge-tests project My gauge -v: Pluginshtml-report (4.0.12) Kind Regards, |
|
Thanks for checking @Sebbiv I noticed that some people have mentioned this from their So, the way gauge-intellij plugin <-> gauge interaction works is like this:
Can you try the below command in one of the gauge projects with this issue?
It should print this in the console:
If for some reason the chosen port is blocked for the given programs (i.e. a firewall) then you could face this issue. |
|
@sriv Found this line in logs "INFO - ks.gauge.GaugeBootstrapService - Using Using the "gauge demon" command results in: Thank you @sriv for taking the time to look into this. |
|
It seems we are close to solving this issue, it looks like the intellij plugin is trying to connect to a different port It is just stuck in a loop connecting to the port but when used the command Thank you very much @sriv |
Signed-off-by: sriv <srikanth.ddit@gmail.com>
Signed-off-by: sriv <srikanth.ddit@gmail.com>
Signed-off-by: sriv <srikanth.ddit@gmail.com>
Signed-off-by: sriv <srikanth.ddit@gmail.com>
|
Could you please use the gauge binary from https://github.com/getgauge/gauge/suites/3016144862/artifacts/68301684 and see if there's any improvement ? I've made some changes, to address a possible condition (thanks to the.stacktrace) |
|
Hello @sriv, I tried copying the Artifact but it did not help. Kind Regards |
|
Hello @sriv, I used the gauge.exe from your last post and the issue remains. With the workaround of using After restarting IntelliJ it worked with a new port: I also get the following in idea.log: Another workaround is to start IntelliJ and disable the Gauge plugin, then restart and reenable it and then restart a third time. When I do this the connection gets established. If I then restart IntelliJ one more time it doesn't work anymore. Are there any other logs or debug output that could help in figuring this out? My IntelliJ version is now the most current: I just had to try starting the gauge daemon 3 times until it worked. I always got: Thanks for the support. |
|
It must be some kind of race condtion. Today I had to execute |
@lochotzke It certainly looks like it. But it's hard for me to be sure without a way to reproduce it. I can make a couple of more changes around this code, if you are ok to test this out. Thanks for debugging this with me, I can imagine this can be quite frustrating. |
|
If you want me to test something just let me know. Thank you |
|
Hello @sriv, I'm available if you want to do some further testing/debugging. I hope this helps, |
|
Thank you for trying this out. Couple of questions:
If you do see this issue with gauve-tests project, I will try to setup a fresh machine with your configuration (as long as it's not too high spec!) |
|
Hello @sriv, I've tested the gauge-test project using the gauge.exe you provided and the same issue occurs. I didn't try to disable/enable the gauge plugin or use the "gauge daemon portFromLog" command either. It might work if tinker with these workarounds but I think it defeats the purpose. This is the log from the start of intelij:
Additional info:
|
|
Hi @Displazya - I think I have a theory (unfortunately, I am unable to simulate this issue myself in any of my environments). What I think is going on here - Gauge is running into a race condition with the file watchers. In the Now, what seems to happen is that the filewatchers seem to get activated before the cache gets built up. I have two ideas to confirm this issue, and I have pushed one to the PR. The first idea is to delay the attaching of the filewatcher. You can get the build here: https://github.com/getgauge/gauge/suites/3111894861/artifacts/71224507 IF you can try and see if this makes any difference, that'd be helpful. thank you! |
|
@sriv i will try it out for a couple more days. so far it looks good. |
|
@lochotzke @Displazya - just wanted to check if the new build is working well for you? If it is, then I'll merge the PR and get a release out. Thanks. |
|
Hello @sriv, We've tested the latest gauge.exe that you provided for the past week and it works really good. No issues encountered! I think its safe to merge the PR. Thank you so much for the effort, you have no idea how much you've helped us. All the best, |
|
Hello @sriv, sorry for responding so late, I had trouble with the new build (company anti-virus had some issues with it). Kind regards |
|
@sriv - the plugin works fine for me. i have switched to a linux vm in the meantime though, because of go issues in my window environment. |
|
Hi @Displazya @Sebbiv @lochotzke - Thank you for your feedback. I will merge this PR then, and you'll be able to use this change in the upcoming release. Thanks again for your patience! |
* ignore events when cache isn't init #1896 Signed-off-by: sriv <srikanth.ddit@gmail.com> * add filewatcher after cache init Signed-off-by: sriv <srikanth.ddit@gmail.com> * bump version -> 1.3.3 Signed-off-by: sriv <srikanth.ddit@gmail.com> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
|
It still stuck on this version Pluginscsharp (0.10.6) |
|
@lirany1 are you able to share any further details to help troubleshoot? |
Yes of course i can like what? |
A sample project to replicate this would be most helpful. But if that's not possible, could you observe your Also, what happens when you run |
|
It's just stuck on connecting to gauge |
|
@lirany1 this should have been fixed in v1.3.3 (https://github.com/getgauge/gauge/releases/tag/v1.3.3) or later. Could you please upgrade gauge and check? (the latest is v1.4.0). |
Yep thanks @sriv seems like it works with 1.4.0 |
|
Good to know! Thanks for the quick response. I'll mark this issue as closed. |
|
Issue started to appear in our projects. I found this thread and after upgrading Gauge the issue persisted. A few debug sessions later I found out that the error cause was that we had a few environment variables in our properties files. Example: |
|
I still have this issue. Gauge version 1.0.7, I'll try to restart Intellij, or change the internet connection. |
Describe the bug
Spec files are not recognized by inteliJ. Ctrl + click on spec results in "Cannot find declaration to go to"
To Reproduce
Steps (or project) to reproduce the behavior:
Log continues until try 10 and stops.
Expected behavior
A clear and concise description of what you expect to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Versions:
Win10 x64
openjdk version "11.0.9.1" 2020-11-04
OpenJDK Runtime Environment AdoptOpenJDK (build 11.0.9.1+1)
OpenJDK 64-Bit Server VM AdoptOpenJDK (build 11.0.9.1+1, mixed mode)
Intelij Ultimate Edition 2020.3.2
203.5981.155
Additional context
Hello everyone,
So this problem is plaguing multiple users including me after performing a fresh install of inteliJ and setting up the project.
Please note the following:
-///////////
INFO - ks.gauge.GaugeBootstrapService - Using
51339as api port to connect to gauge API for project C:\Users\croppedUser\croppedFrameworkPathINFO - ks.gauge.GaugeBootstrapService - Initializing Gauge connection at 51339
///////////
And nothing related to gauge anymore
Does anyone have any suggestion on how to permanently fix this?
Thank you!
The text was updated successfully, but these errors were encountered: