You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[HOLD for payment 2024-05-08] [$250] Profile - Display name is not updating in "Share Somewhere" section #39607
👋 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:
Identify the pull request that introduced this issue and revert it.
I'm looking into this, nothing in the checklist stands out to me that might be something that broke this so having to dive into the code and see what exactly gets called.
okay i don't think it's a problem with the API, i see the response coming back properly with the updated data
And I see in the onyx db that it's been updated there
So this makes me think that for some reason the Share Somewhere component isn't properly subscribing to the onyx data or something so going to take a closer look at that.
I guess what we need is a way to invalidate the option list cache when personal details are updated, if there is a way to do that in the PR can you let me know?
or if that's still to come then maybe we consider this not a blocker?
@bondydaa This seems like a pretty minor bug–and since we've already narrowed down which PR it's coming from I think we can just mark it NAB and have @TMisiukiewicz look into a fix
changed the title [-][$250] Profile - Display name is not updating in "Share Somewhere" section[/-][+][HOLD for payment 2024-05-08] [$250] Profile - Display name is not updating in "Share Somewhere" section[/+]on May 1, 2024
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.68-3 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this 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:
[@hungvu193] The PR that introduced the bug has been identified. Link to the PR:
[@hungvu193] 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:
[@hungvu193] 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:
[@hungvu193] Determine if we should create a regression test for this bug.
[@hungvu193] 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.
[@JmillsExpensify] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:
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:
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: N/A
Determine if we should create a regression test for this bug: No
This is new feature, we can treat it as a follow up of #38207
Activity
melvin-bot commentedon Apr 4, 2024
Triggered auto assignment to @bondydaa (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.github-actions commentedon Apr 4, 2024
👋 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:
kbecciv commentedon Apr 4, 2024
We think that this bug might be related to #vip-vsb
bondydaa commentedon Apr 4, 2024
I'm looking into this, nothing in the checklist stands out to me that might be something that broke this so having to dive into the code and see what exactly gets called.
bondydaa commentedon Apr 4, 2024
okay i don't think it's a problem with the API, i see the response coming back properly with the updated data

And I see in the onyx db that it's been updated there

So this makes me think that for some reason the
Share Somewherecomponent isn't properly subscribing to the onyx data or something so going to take a closer look at that.bondydaa commentedon Apr 4, 2024
Hmm this PR is sus to me after looking at the components involved here: #38207
bondydaa commentedon Apr 4, 2024
okay yes I believe I've confirmed this by testing locally.
checking out
1.4.60-1locally I see the same behavior and then reverting it I can't reproduce it anymore.cc @grgia @hungvu193 @TMisiukiewicz can you take a look here?
bondydaa commentedon Apr 4, 2024
I guess what we need is a way to invalidate the option list cache when personal details are updated, if there is a way to do that in the PR can you let me know?
or if that's still to come then maybe we consider this not a blocker?
makes me think of my favorite tweet 😂 https://twitter.com/codinghorror/status/506010907021828096
jasperhuangg commentedon Apr 4, 2024
@bondydaa This seems like a pretty minor bug–and since we've already narrowed down which PR it's coming from I think we can just mark it NAB and have @TMisiukiewicz look into a fix
52 remaining items
[-][$250] Profile - Display name is not updating in "Share Somewhere" section[/-][+][HOLD for payment 2024-05-08] [$250] Profile - Display name is not updating in "Share Somewhere" section[/+]melvin-bot commentedon May 1, 2024
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon May 1, 2024
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.68-3 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 2024-05-08. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon May 1, 2024
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:
hungvu193 commentedon May 1, 2024
This is new feature, we can treat it as a follow up of #38207
melvin-bot commentedon May 13, 2024
@JmillsExpensify, @bondydaa, @hungvu193, @nkdengineer Huh... This is 4 days overdue. Who can take care of this?
hungvu193 commentedon May 14, 2024
Bump @JmillsExpensify for payment here
JmillsExpensify commentedon May 14, 2024
Payment summary:
JmillsExpensify commentedon May 14, 2024
Both Contributor contracts paid out via Upwork, so I'm closing this issue.