-
Notifications
You must be signed in to change notification settings - Fork 28.8k
Fix custom-device default forwardPortSuccessRegex #97719
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 custom-device default forwardPortSuccessRegex #97719
Conversation
It looks like this pull request may not have tests. Please make sure to add tests before merging. If you need an exemption to this rule, contact Hixie on the #hackers channel in Chat. If you are not sure if you need tests, consider this rule of thumb: the purpose of a test is to make sure someone doesn't accidentally revert the fix. Ask yourself, is there anything in your PR that you feel it is important we not accidentally revert back to how it was before your fix? Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing. |
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.
I think this would need a test before we can merge.
Sorry, I was not very active on this PR. So yes, I would be happy to add some tests here. Actually my modification made some tests to fail, but these tests were removed in commit 87fe3fe (#98299), as they were failing for another issue, that I believe is actually a bug. I managed to fix this bug and make the test pass, would you mind if I import back these tests ? I'm pushing these modifications, just to detail what I am talking about. |
1796496
to
840fe15
Compare
Oh nice! This is great. |
The analysis failure was fixed upstream, a rebase should fix |
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.
LGTM
Tests were removed in flutter#98299
Having an empty list as postBuildCommand value will trigger an error on JSON parsing: make sure to save a null instead.
9b80bd4
to
0cb9761
Compare
c6402dc
to
394dfce
Compare
Sorry, I still have an issue with the "Linux analyze" test. It complains that I have to "Avoid redundant argument values", but if I remove the
So I explicitly added |
This pull request is not suitable for automatic merging in its current state.
|
@Jasguerrero can you review this one too? |
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.
LGTM
This PR tries to make port forwarding verification on custom devices more reliable, by not relying on behavior that may change across different systems.
Previously we were looking for
Linux
word in target connection banner. Now we ask the remote to print a fixed string ('Port forwarding success`) and look for this given string to ensure the connection was successful.Fix #97641
Pre-launch Checklist
///
).