-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
tor: fix TestReconnectSucceed
#9581
base: master
Are you sure you want to change the base?
tor: fix TestReconnectSucceed
#9581
Conversation
Important Review skippedAuto reviews are limited to specific labels. 🏷️ Labels to auto review (1)
Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
tor/controller_test.go
Outdated
"net" | ||
"net/textproto" | ||
"testing" | ||
|
||
"github.com/lightningnetwork/lnd/lntest/port" |
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.
We're in a submodule and don't have this dependency available (it would create a circular one if we did).
Perhaps we can just copy the NextAvailablePort
function over? A bit of duplication doesn't sound too bad here, especially if it's just test code.
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.
yeah right - guess i'm using go work locally so it never popped up...
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.
actually i think in order to run the new test we need to tag the module tor
?
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.
The unit test will run in make unit-module
. But yes, for the unit cover
flake to be fixed we need to tag and update the tor
submodule.
We now make sure the proxy server is running on a unique port. In addition, we close the old conn before making a new conn.
e7ff4e3
to
a116eef
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.
Thanks for the fix!
We now make sure the proxy server is running on a unique port. In addition, we close the old conn before making a new conn.