Closed kbecciv closed 1 year ago
:wave: 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:
Triggered auto assignment to @aldo-expensify (Engineering
), see https://stackoverflow.com/c/expensify/questions/4319 for more details.
Reproduced:
The selectedParticipants
here:
are missing the login
:
@Beamanator do you know if that is expected? I see that the text
contains the email. These accounts did not exist when I created the group with them.
it seems like in Onyx personalDetails
we have two entries for the accounts created with the group, for example:
The account appears under a real ID (11033541), missing the login
key, and under a front end generated ID (4331464817836459) which does have the login
information.
Debugging, I see that the participant is passed around with the real ID 11033541, so when we look in personalDetails
for the login information, it is just not there.
⚠️ 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.
When I created a group w/ a user that didn't exist yet, I saw __fake__
in the LHN (mentioned in linked issue ^). I also noticed I see this in Onyx:
main
, only in StagingAnd this too, due to optimistic accountIDs:
main
and in StagingWhich also leads to Hidden
showing in the report participants page (I know this has been reported elsewhere, i just want to add for complete investigation):
main
and in StagingOn the "Split Bill" -> Confirm page (in main
), I also saw:
Warning: Encountered two children with the same key, .$1=2undefined
(probably because we're keying off logins and the users don't have login
in their personalDetails, but they do have displayName
and accountID
PR up for this: https://github.com/Expensify/App/pull/21113
Assigning @s77rt since they're reviewing the PR 👍 🙏
Removing the blocker label since we merged the PR and are CPing it.
⚠️ 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.
Reviewing
label has been removed, please complete the "BugZero Checklist".
The solution for this issue has been :rocket: deployed to production :rocket: in version 1.3.29-11 and is now subject to a 7-day regression period :calendar:. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2023-06-28. :confetti_ball:
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.
As a reminder, here are the bonuses/penalties that should be applied for any External issue:
The solution for this issue has been :rocket: deployed to production :rocket: in version 1.3.30-5 and is now subject to a 7-day regression period :calendar:. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2023-06-29. :confetti_ball:
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.
As a reminder, here are the bonuses/penalties that should be applied for any External issue:
@Beamanator, @s77rt, @aldo-expensify Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!
Triggered auto assignment to @zanyrenney (Bug
), see https://stackoverflow.com/c/expensify/questions/14418 for more details.
Platforms
in OP are ✅)@zanyrenney I think this just needs payment handling.
@s77rt reviewed the PR https://github.com/Expensify/App/pull/21113 which was fixing this deploy blocker
I'll be out of office next week, I don't think you need any action from me 👋
Going to chat to @Beamanator to understand the latest here!
Hi there! After discussing internally, seeing as technically @s77rt & @narefyev91 both helped test & review that PR and you are both C+ we will be splitting the payment so it does not warrant the full $1000 each. it should be $500 each.
Payment on upwork sent for reporting bonus and C+ work from @s77rt . Closing this one out!
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:
Expected Result:
Selecting/removing one user should not selects/remove all the user on split bill group page
Actual Result:
Selecting/removing one user selects/removes all the user on split bill group page
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: 1.3.29-0
Reproducible in staging?: yes
Reproducible in production?: no
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
https://github.com/Expensify/App/assets/93399543/f94f1ad4-5253-40bb-bd4b-e88d6a95590b
https://github.com/Expensify/App/assets/93399543/fba375a5-8caf-4087-82c1-3901d4b8de87
Expensify/Expensify Issue URL:
Issue reported by: @priya-zha
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1686991867243109
View all open jobs on GitHub