-
Notifications
You must be signed in to change notification settings - Fork 984
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
Setup syncing timer fix #15852
Setup syncing timer fix #15852
Conversation
2b0f9c4
to
fe74fdc
Compare
Jenkins BuildsClick to see older builds (16)
|
Hey @ajayesivan! Thanx for the PR. Please take a look at the following issue. ISSUE 1 Sync code does not expire after 2 minutes and can be successfully used for syncingSteps:
Actual result: error does not appear. Sync code does not expire and can be used after expiration period is up. Expected result: sync code should expire in 2 minutes after being generated. Using expired code should result in error "This sync code has expired". Figma |
69fd115
to
dcd250a
Compare
@ajayesivan I will move PR to CONTRIBUTOR column. Please, move it to E2E column when its ready for re-test. Thank you! |
@pavloburykh This bug was not introduced in this PR, so can we go ahead and merge this PR? I will take care of this separately(#15945). |
Hi @ajayesivan ! Sounds good. Should this PR be retested after rebasing branch? I see there are a lot of new commits in develop which could result in conflicts after rebasing. If re-test is not needed - then you are good to merge. |
006ea5b
to
62cc321
Compare
62cc321
to
8502832
Compare
fixes #15807
status: ready