-
Notifications
You must be signed in to change notification settings - Fork 5k
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: flaky test Vault Decryptor Page is able to decrypt the vault us..
due to empty file load
#26612
Conversation
CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #26612 +/- ##
===========================================
+ Coverage 70.04% 70.09% +0.05%
===========================================
Files 1411 1413 +2
Lines 49205 49254 +49
Branches 13754 13768 +14
===========================================
+ Hits 34463 34524 +61
+ Misses 14742 14730 -12 ☔ View full report in Codecov by Sentry. |
Builds ready [7548864]
Page Load Metrics (77 ± 11 ms)
Bundle size diffs
|
Vault Decryptor Page is able to decrypt the vault us..
due to empty file load
Builds ready [aeba870]
Page Load Metrics (82 ± 9 ms)
Bundle size diffs
|
No dependency changes detected. Learn more about Socket for GitHub ↗︎ 👍 No dependency changes detected in pull request |
a59a0f1
to
aeba870
Compare
}); | ||
|
||
// Retry-logic if file upload fails | ||
if (!fileLoaded) { |
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.
Hi, I have a question about the logic. The value of the fileLoaded
variable will be true if the element "Can not read vault from file" appears. Is this intended? It seems like it should be reversed. But maybe I misunderstood.
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.
hey @chloeYue that's an awesome catch 😍 I've pushed a fix for that.
I'm now trying to see if there could be an alternative way of fixing this on the root cause - based on [this comment] from David (https://consensys.slack.com/archives/CTQAGKY5V/p1724395549815109?thread_ts=1724321902.861359&cid=CTQAGKY5V) If so, I'll update the PR one more time, if not, then we can leave this as a mitigation. I'll share my updates soon 🙏
Quality Gate passedIssues Measures |
Builds ready [5621c96]
Page Load Metrics (81 ± 8 ms)
Bundle size diffs
|
Quality Gate passedIssues Measures |
Builds ready [7f9762f]
Page Load Metrics (74 ± 9 ms)
Bundle size diffs
|
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!
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 !
Description
The vault decrypt test is flaky, at the point where we upload the vault file into the browser.
I added logs for checking the file size, and I saw that when the file failed to upload, the file size was really small.
The problem seemed to start appearing after this PR was merged. The changes doesn't seem related, but it updated a lot of dependencies, some of them related to cryptography/addres derivation packages (see screenshot below) - which could somehow affect somehow the timings.
Fix:
See logic in action:
Notes and future work:
Related issues
Fixes: #26572
Manual testing steps
Screenshots/Recordings
When the error appears, we can see how the file size is really small
19 bytes
.whereas when the test is successful, the file size is bigger
7358117 bytes
.See changes mentioned, after flakiness started appearing:
Pre-merge author checklist
Pre-merge reviewer checklist