-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Fix address regex #3961
Fix address regex #3961
Conversation
@devinbileck Could you please resolve the conflict caused by a merged PR? 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.
Thanks for fixing this so quickly. I'm testing it now but unfortunately my configuration still fails to pass your validation, I guess the following testcase is not handled by the FQDN regex:
foo.example.com:8333,bar.example.com:8333
Also, probably unrelated to your change, but for some reason IPv6 address btcnodes work on the command line but don't work when set in the GUI - I always set my stuff from the command line but kinda surprised nobody else noticed that bug. |
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 will ACK for now and will submit a separate PR to fix the remaining FQDN regex case
The original implementation of bisq-network#3895 did not validate IPv6 nor FQDN addresses.
ea7f5ce
to
0f71ebb
Compare
☝️ resolved the conflict with master and force pushed it |
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.
utACK - based on #3961 (review)
The original implementation of #3895 did not validate IPv6 nor FQDN addresses.