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-09-21] Overlay when RHP is opening is not over the entire page #26390

Closed
mountiny opened this issue Aug 31, 2023 · 22 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 Internal Requires API changes or must be handled by Expensify staff

Comments

@mountiny
Copy link
Contributor

mountiny commented Aug 31, 2023

Problem

When the RHP i sanimating open now, the overlay is not covering the entire page so you can see it animate too

Solution

Make the overlay wider so users cannot see it to be animated.

overlayFade.mp4
Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~01c8489b64c7a71468
  • Upwork Job ID: 1697225734121099264
  • Last Price Increase: 2023-08-31
@mountiny mountiny added Daily KSv2 Internal Requires API changes or must be handled by Expensify staff Bug Something is broken. Auto assigns a BugZero manager. labels Aug 31, 2023
@melvin-bot
Copy link

melvin-bot bot commented Aug 31, 2023

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

@melvin-bot
Copy link

melvin-bot bot commented Aug 31, 2023

Job added to Upwork: https://www.upwork.com/jobs/~01c8489b64c7a71468

@melvin-bot
Copy link

melvin-bot bot commented Aug 31, 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

@melvin-bot
Copy link

melvin-bot bot commented Aug 31, 2023

Current assignee @rushatgabhane is eligible for the Internal assigner, not assigning anyone new.

@melvin-bot
Copy link

melvin-bot bot commented Aug 31, 2023

⚠️ Looks like this issue was linked to a Deploy Blocker here

If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

If a regression has occurred and you are the assigned CM follow the instructions here.

If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

@laurenreidexpensify
Copy link
Contributor

@mountiny can you pop an update here on this one, assume we're focused on this in #26385?

@mountiny
Copy link
Contributor Author

mountiny commented Sep 7, 2023

@laurenreidexpensify correct, pr is ready to be merged, just waiting for the merge freeze to be over

@laurenreidexpensify
Copy link
Contributor

Merge freeze is over now right?

@mountiny
Copy link
Contributor Author

yep, Adam is ooo, asking if someone can update the Pr now

@melvin-bot
Copy link

melvin-bot bot commented Sep 13, 2023

⚠️ Looks like this issue was linked to a Deploy Blocker here

If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

If a regression has occurred and you are the assigned CM follow the instructions here.

If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

@laurenreidexpensify laurenreidexpensify added Weekly KSv2 and removed Daily KSv2 labels Sep 14, 2023
@melvin-bot melvin-bot bot added Weekly KSv2 Awaiting Payment Auto-added when associated PR is deployed to production and removed Weekly KSv2 labels Sep 14, 2023
@melvin-bot melvin-bot bot changed the title Overlay when RHP is opening is not over the entire page [HOLD for payment 2023-09-21] Overlay when RHP is opening is not over the entire page Sep 14, 2023
@melvin-bot melvin-bot bot removed the Reviewing Has a PR in review label Sep 14, 2023
@melvin-bot
Copy link

melvin-bot bot commented Sep 14, 2023

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

@melvin-bot
Copy link

melvin-bot bot commented Sep 14, 2023

The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.69-2 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-09-21. 🎊

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:

  • @rushatgabhane does not require payment (Eligible for Manual Requests)

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 Sep 14, 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:

  • [@mountiny] The PR that introduced the bug has been identified. Link to the PR:
  • [@mountiny] 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:
  • [@mountiny] 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:
  • [@rushatgabhane] Determine if we should create a regression test for this bug.
  • [@rushatgabhane] 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.
  • [@laurenreidexpensify] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:

@melvin-bot melvin-bot bot removed the Weekly KSv2 label Sep 21, 2023
@melvin-bot melvin-bot bot added the Daily KSv2 label Sep 21, 2023
@laurenreidexpensify
Copy link
Contributor

@mountiny am assuming payment for this is $500 for C+ review, no reporting or C work?

@mountiny
Copy link
Contributor Author

@laurenreidexpensify I think that is right, $500 to @rushatgabhane for review and testing

@rushatgabhane
Copy link
Member

WIP ⚠️

  1. The PR that introduced the bug has been identified. Link to the PR:

  2. 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:

  3. 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:

  4. Determine if we should create a regression test for this bug.

  5. 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

@rushatgabhane
Copy link
Member

Created a manual request - https://staging.new.expensify.com/r/4946760350922580

@laurenreidexpensify
Copy link
Contributor

@rushatgabhane have you had a moment to complete teh steps above? Thanks!

@melvin-bot melvin-bot bot added the Overdue label Oct 2, 2023
@laurenreidexpensify
Copy link
Contributor

@rushatgabhane bump ^^

@melvin-bot melvin-bot bot added Overdue and removed Overdue labels Oct 3, 2023
@melvin-bot
Copy link

melvin-bot bot commented Oct 6, 2023

@rushatgabhane, @mountiny, @laurenreidexpensify Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

@mountiny
Copy link
Contributor Author

mountiny commented Oct 6, 2023

I will finish this for Rushat so we can close this. Its coming from this PR #22437, it was a new feature from perspective of navigation, the author fixed the regression so no need to comment on the PR.

I dont think we need regression test for this.

@rushatgabhane can you please request $500 for internal review in NewDot, you can use this issue to track the payment. Closing

@mountiny mountiny closed this as completed Oct 6, 2023
@melvin-bot melvin-bot bot removed the Overdue label Oct 6, 2023
@JmillsExpensify
Copy link

$500 payment approved for @rushatgabhane based on this comment.

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 Internal Requires API changes or must be handled by Expensify staff
Projects
None yet
Development

No branches or pull requests

4 participants