- Notifications
You must be signed in to change notification settings - Fork1.1k
fix: track JetBrains connections#10968
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
Based on tcp forwarding instead of ssh connections
7948ab5 toe7f9516Comparematifali commentedDec 1, 2023
@code-asher Try |
code-asher commentedDec 1, 2023
Verified it works! 🎉 |
fe83fbd to9dede7fComparecode-asher commentedDec 1, 2023
Ah wait moving back to draft, there seems to be an issue... |
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
9dede7f to9840a69Comparecode-asher commentedDec 1, 2023
The two issues I ran into, just FYI:
I think it is all sorted now, doing some more testing to be sure. |
code-asher commentedDec 1, 2023
OK, verified it all works as expected in a deployment. Test is failing in CI though. Passes for me locally... |
Emyrk commentedDec 1, 2023
Ooof, this test is quite strange too. That sounds annoying to debug... Use |
Co-authored-by: Steven Masley <Emyrk@users.noreply.github.com>
Co-authored-by: Steven Masley <Emyrk@users.noreply.github.com>
Co-authored-by: Steven Masley <Emyrk@users.noreply.github.com>
64ea05d to6e8f235Comparematifali commentedDec 1, 2023
Will this also work for Fleet? |
e79b01c toec59e7eComparecode-asher commentedDec 1, 2023
I am not sure, we will need to test. |
ec59e7e to90e6e88Compare9cf5082 to7fd04cbCompareThe test name only shows up in the process name if you are running thattest directly so we have to spawn a separate process instead.
7fd04cb toa75ed6cComparecode-asher commentedDec 1, 2023
OK, sorted the test. The test name only shows up in the process name if you run that specific test directly, so when we are running the entire suite the name does not show up. What I did was spawn an external process instead. Not sure if I did it in an idiomatic way or if there even is an idiomatic way, with Node I would just We could also try spawning something like |
Emyrk left a comment
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, let's get this in and test it a bit.
Uh oh!
There was an error while loading.Please reload this page.
Fixes#9673
Possibly we will need to find a better string to match on, but this one seems OK to me.
Unit test passes but have not tested an actual deploy yet.