Skip to content
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

Closed
1 of 6 tasks
kbecciv opened this issue Sep 20, 2023 · 32 comments
Assignees
Labels
Awaiting Payment Auto-added when associated PR is deployed to production Bug Something is broken. Auto assigns a BugZero manager. Daily KSv2 Engineering External Added to denote the issue can be worked on by a contributor

Comments

@kbecciv
Copy link

kbecciv commented Sep 20, 2023

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!


Action Performed:

  1. Click on the FAB and request money
  2. Choose scan > then Choose file
  3. Choose where you want to request from and click request
  4. Click on the request message on the main chat to open the IOU room
  5. Notice the corners of the scan request container

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?

  • Android / native
  • Android / Chrome
  • iOS / native
  • iOS / Safari
  • MacOS / Chrome / Safari
  • MacOS / Desktop

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
  • Upwork Job URL: https://www.upwork.com/jobs/~0116d11f7e44782d5a
  • Upwork Job ID: 1704583117854482432
  • Last Price Increase: 2023-09-20
  • Automatic offers:
    • fedirjh | Reviewer | 26784222
    • getusha | Contributor | 26784224
    • Ahmed-Abdella | Reporter | 26784225
@kbecciv kbecciv added the DeployBlockerCash This issue or pull request should block deployment label Sep 20, 2023
@dukenv0307
Copy link
Contributor

Proposal

Please 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 moneyRequestPreviewBox style here that contains borderRadius style

style={[styles.moneyRequestPreviewBox, ...props.containerStyles]}

App/src/styles/styles.js

Lines 2725 to 2730 in 52dc94d

moneyRequestPreviewBox: {
backgroundColor: theme.cardBG,
borderRadius: variables.componentBorderRadiusLarge,
maxWidth: variables.sideBarWidth,
width: '100%',
},

But we don't add this to the wrap View of the child container


<View style={[isScanning || props.isWhisper ? styles.reportPreviewBoxHoverBorder : undefined]}>

Because the width of this View is full and we don't have an overflow hidden style, the scan container is not rounded

What changes do you think we should make in order to solve the problem?

We can add overflow: 'hidden' style to moneyRequestPreviewBox style to hide the overflow width of children's container

App/src/styles/styles.js

Lines 2725 to 2730 in 52dc94d

moneyRequestPreviewBox: {
backgroundColor: theme.cardBG,
borderRadius: variables.componentBorderRadiusLarge,
maxWidth: variables.sideBarWidth,
width: '100%',
},

What alternative solutions did you explore? (Optional)

We can add moneyRequestPreviewBox style for the wrap View of the child container


<View style={[isScanning || props.isWhisper ? styles.reportPreviewBoxHoverBorder : undefined]}>

Result

Screenshot 2023-09-20 at 16 23 28

@OSBotify
Copy link
Contributor

👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open StagingDeployCash deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

  1. Identify the pull request that introduced this issue and revert it.
  2. Find someone who can quickly fix the issue.
  3. Fix the issue yourself.

@melvin-bot
Copy link

melvin-bot bot commented Sep 20, 2023

Triggered auto assignment to @bondydaa (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

@s-alves10
Copy link
Contributor

This is a regression of this PR

@bondydaa
Copy link
Contributor

doh thanks for letting us know @getusha @fedirjh can you comment so I can assign?

@bondydaa
Copy link
Contributor

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?

@bondydaa bondydaa added Daily KSv2 and removed DeployBlockerCash This issue or pull request should block deployment Hourly KSv2 labels Sep 20, 2023
@getusha
Copy link
Contributor

getusha commented Sep 20, 2023

doh thanks for letting us know @getusha @fedirjh can you comment so I can assign?

yeah we should handle this one.

@bondydaa bondydaa added the Bug Something is broken. Auto assigns a BugZero manager. label Sep 20, 2023
@melvin-bot
Copy link

melvin-bot bot commented Sep 20, 2023

Triggered auto assignment to @jliexpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

@melvin-bot
Copy link

melvin-bot bot commented Sep 20, 2023

Bug0 Triage Checklist (Main S/O)

  • This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
  • This bug is not a duplicate report (check E/App issues and #expensify-bugs)
    • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
  • This bug is reproducible using the reproduction steps in the OP. S/O
    • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
    • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
  • This issue is filled out as thoroughly and clearly as possible
    • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
  • I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

@bondydaa bondydaa added the External Added to denote the issue can be worked on by a contributor label Sep 20, 2023
@melvin-bot melvin-bot bot changed the title Web - Receipt scan request container corners are not rounded while it is in progress [$500] Web - Receipt scan request container corners are not rounded while it is in progress Sep 20, 2023
@melvin-bot
Copy link

melvin-bot bot commented Sep 20, 2023

Job added to Upwork: https://www.upwork.com/jobs/~0116d11f7e44782d5a

@melvin-bot melvin-bot bot added the Help Wanted Apply this label when an issue is open to proposals by contributors label Sep 20, 2023
@melvin-bot
Copy link

melvin-bot bot commented Sep 20, 2023

Current assignee @jliexpensify is eligible for the External assigner, not assigning anyone new.

@melvin-bot
Copy link

melvin-bot bot commented Sep 20, 2023

Current assignee @fedirjh is eligible for the External assigner, not assigning anyone new.

@melvin-bot
Copy link

melvin-bot bot commented Sep 28, 2023

Based on my calculations, the pull request did not get merged within 3 working days of assignment. Please, check out my computations here:

  • when @getusha got assigned: 2023-09-20 19:48:38 Z
  • when the PR got merged: 2023-09-28 07:05:03 UTC
  • days elapsed: 5

On to the next one 🚀

@melvin-bot melvin-bot bot added Weekly KSv2 Awaiting Payment Auto-added when associated PR is deployed to production and removed Weekly KSv2 labels Oct 2, 2023
@melvin-bot melvin-bot bot changed the title [$500] Web - Receipt scan request container corners are not rounded while it is in progress [HOLD for payment 2023-10-09] [$500] Web - Receipt scan request container corners are not rounded while it is in progress Oct 2, 2023
@melvin-bot
Copy link

melvin-bot bot commented Oct 2, 2023

Reviewing label has been removed, please complete the "BugZero Checklist".

@melvin-bot melvin-bot bot removed the Reviewing Has a PR in review label Oct 2, 2023
@melvin-bot
Copy link

melvin-bot bot commented Oct 2, 2023

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.

  • External issue reporter
  • Contributor that fixed the issue
  • Contributor+ that helped on the issue and/or PR

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:

  • Merged PR within 3 business days of assignment - 50% bonus
  • Merged PR more than 9 business days after assignment - 50% penalty

@melvin-bot
Copy link

melvin-bot bot commented Oct 2, 2023

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] The PR that introduced the bug has been identified. Link to the PR:
  • [@fedirjh] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
  • [@fedirjh] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:
  • [@fedirjh] Determine if we should create a regression test for this bug.
  • [@fedirjh] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
  • [@jliexpensify] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:

@melvin-bot melvin-bot bot added Daily KSv2 and removed Weekly KSv2 Daily KSv2 labels Oct 9, 2023
@jliexpensify
Copy link
Contributor

@fedirjh bump to complete the checklist - I'll pay tomorrow!

@jliexpensify jliexpensify changed the title [HOLD for payment 2023-10-09] [$500] Web - Receipt scan request container corners are not rounded while it is in progress [HOLD for payment 2023-10-10] [$500] Web - Receipt scan request container corners are not rounded while it is in progress Oct 9, 2023
@jliexpensify
Copy link
Contributor

jliexpensify commented Oct 9, 2023

Payment Summary:

Upwork job

Please see this comment for context

@jliexpensify
Copy link
Contributor

Also @fedirjh and @getusha can you accept those offers? Cheers!

@jliexpensify
Copy link
Contributor

BUMPING @fedirjh and @getusha to accept the offers please.

BUMPING @fedirjh to complete the checklist!

@fedirjh
Copy link
Contributor

fedirjh commented Oct 11, 2023

BugZero Checklist:

  • Link to the PR: Fix missing margin between name and request money preview box #27692
  • Link to comment: The author has handled this regression
  • Link to discussion: N/A This is a simple styling bug, no additional discussion is needed.
  • Determine if we should create a regression test for this bug: N/A, this is a little styling bug that doesn’t affect UX, no regression test is needed.

Payment Summary:

@jliexpensify This was handled as a regression for another PR, I think the correct summary should be :

  • Reporter: 50$
  • Contributor: 250$
  • C+: 250$

@jliexpensify
Copy link
Contributor

Thank you @fedirjh ! @getusha please accept the offer so I can pay everyone, thanks!

@getusha
Copy link
Contributor

getusha commented Oct 11, 2023

@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 😄

@jliexpensify
Copy link
Contributor

jliexpensify commented Oct 11, 2023

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

@jliexpensify
Copy link
Contributor

Hmm ok, so - here are the Regression Guidelines:

image

If this is a regression of a regression, then I would imagine the payout would be:

@melvin-bot melvin-bot bot added the Overdue label Oct 16, 2023
@melvin-bot
Copy link

melvin-bot bot commented Oct 17, 2023

@bondydaa, @jliexpensify, @fedirjh, @getusha Eep! 4 days overdue now. Issues have feelings too...

@jliexpensify
Copy link
Contributor

Just confirming - no further regressions here right? If not, I'll move to paying based off this

@melvin-bot melvin-bot bot removed the Overdue label Oct 17, 2023
@fedirjh
Copy link
Contributor

fedirjh commented Oct 17, 2023

no further regressions here right?

Yes.

@jliexpensify
Copy link
Contributor

Everyone paid, job closed!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Awaiting Payment Auto-added when associated PR is deployed to production Bug Something is broken. Auto assigns a BugZero manager. Daily KSv2 Engineering External Added to denote the issue can be worked on by a contributor
Projects
None yet
Development

No branches or pull requests

8 participants