-
Notifications
You must be signed in to change notification settings - Fork 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
[HOLD for payment 2023-10-10] [$500] Web - Receipt scan request container corners are not rounded while it is in progress #27869
Comments
ProposalPlease re-state the problem that we are trying to solve in this issue.Dev - receipt scan request container corners are not rounded while it is in progress What is the root cause of that problem?We add
Lines 2725 to 2730 in 52dc94d
But we don't add this to the wrap
Because the width of this What changes do you think we should make in order to solve the problem?We can add Lines 2725 to 2730 in 52dc94d
What alternative solutions did you explore? (Optional)We can add
Result |
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open
|
Triggered auto assignment to @bondydaa ( |
This is a regression of this PR |
that being said i don't think we need to block the deploy b/c of this so going to remove the blocker, mostly just a style thing right? |
Triggered auto assignment to @jliexpensify ( |
Bug0 Triage Checklist (Main S/O)
|
Job added to Upwork: https://www.upwork.com/jobs/~0116d11f7e44782d5a |
Current assignee @jliexpensify is eligible for the External assigner, not assigning anyone new. |
Current assignee @fedirjh is eligible for the External assigner, not assigning anyone new. |
Based on my calculations, the pull request did not get merged within 3 working days of assignment. Please, check out my computations here:
On to the next one 🚀 |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.75-12 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2023-10-09. 🎊 After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
For reference, here are some details about the assignees on this issue:
As a reminder, here are the bonuses/penalties that should be applied for any External issue:
|
BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
|
@fedirjh bump to complete the checklist - I'll pay tomorrow! |
Payment Summary:
|
BugZero Checklist:
@jliexpensify This was handled as a regression for another PR, I think the correct summary should be :
|
@jliexpensify i don't think i should be getting paid here, this was a regression from a PR fixing a regression from another PR. i don't know how we process that 😄 |
Huh ok...that's not something I have come across before...let me check what we do here and update you both! Slack thread - https://expensify.slack.com/archives/C01SKUP7QR0/p1697061567091469 |
Hmm ok, so - here are the Regression Guidelines: If this is a regression of a regression, then I would imagine the payout would be:
|
@bondydaa, @jliexpensify, @fedirjh, @getusha Eep! 4 days overdue now. Issues have feelings too... |
Just confirming - no further regressions here right? If not, I'll move to paying based off this |
Yes. |
Everyone paid, job closed! |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Action Performed:
Expected Result:
The corners of the scan request container should be rounded
Actual Result:
Receipt scan request container corners are not rounded while it is in progress ( No border radius )
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: 1.3.72.6
Reproducible in staging?: y
Reproducible in production?: n
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Screencast.from.20-09-23.05_08_04.webm
Recording.4629.mp4
Expensify/Expensify Issue URL:
Issue reported by: @Ahmed-Abdella
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1695176494284799
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: