Closed gp201 closed 1 week ago
Hi @gp201, can you complete the following:
Hi @gp201 please assign the required reviewer(s) for this PR. Thanks!
Hi @gp201. Due to recent changes in the "develop" branch, this PR now has a merge conflict. Please follow this link if you need help resolving the conflict, so that the PR can be merged. Thanks!
Hi @gp201, I'm going to mark this PR as stale because it hasn't had any updates for 7 days. If no further activity occurs within 4 days, it will be automatically closed so that others can take up the issue. If you are still working on this PR, please make a follow-up commit within 4 days (and submit it for review, if applicable). Please also let us know if you are stuck so we can help you!
@gp201 PTAL at comment, need your response before I can move forward on it.
@seanlip, @StephenYu2018 Could you review implementation of fixing google module for docker made in commit here. I will add backend tests if approved.
An alternative would be to call install_third_party_libs.main() explicitly and handling docker-specific instructions in install_third_party_libs.py
Unassigning @StephenYu2018 since the review is done.
@jayam04 I believe there is still one prior concern about a browser.pause
statement in an E2E test file that hasn't been addressed yet. It is the only thing stopping me from approving this PR.
@jayam04 I believe there is still one prior concern about a
browser.pause
statement in an E2E test file that hasn't been addressed yet. It is the only thing stopping me from approving this PR.
@StephenYu2018 I know it, currently focusing on other bugs due to which some e2e tests are failing. Once done, I will update browser.pause appropriate solution.
Assigning @U8NWXD, @Lawful2002 for code owner reviews. Thanks!
@seanlip, @StephenYu2018 Some tests are still failing, should I use browser.pause() over there too and create a new issue for same.
@U8NWXD @Lawful2002 PTAL as codeowners, thanks.
@seanlip Created new issue for one e2e test failing. Could you review issue, do I need to add more info? Once done, I will open issues for other 5 failing tests.
Thanks @jayam04 -- the issue looks good, but I have some concerns about merging this with 6 known flakes that are likely to keep cropping up and blocking developers from merging things. It's going to make the dev workflow very tedious if developers have to keep rerunning the tests again and again.
I think it'd still be good to file the issues now, but after that, could you work with folks to try and fix them before we merge this PR? @jnvtnguyen has been doing some flake fixes recently, and might be a good person to ask for tips/help.
Thanks!
I have addressed some of the comments. Will address the remaining by tomorrow:
Unassigning @Lawful2002 since they have already approved the PR.
Hi @U8NWXD,
Apologies for the trouble, and thanks for your patience. Since this PR is time-sensitive, could you quickly check out the other comments?
Right now, I'm focusing on resolving the comments provided in these two discussions:
I've replied to or resolved my responded-to comments
Hi @gp201, I'm going to mark this PR as stale because it hasn't had any updates for 7 days. If no further activity occurs within 4 days, it will be automatically closed so that others can take up the issue. If you are still working on this PR, please make a follow-up commit within 4 days (and submit it for review, if applicable). Please also let us know if you are stuck so we can help you!
Overview
Essential Checklist
Testing doc (for PRs with Beam jobs that modify production server data)
Proof that changes are correct
Proof of changes on desktop with slow/throttled network
Proof of changes on mobile phone
Proof of changes in Arabic language
PR Pointers