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-04-25] [$500] Chats are not loading in the LHN with Most Recent mode #39380
👋 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.
changed the title [-][$500] Chats are not loading in the LHN with `Most Recent` mode[/-][+][HOLD for payment 2024-04-25] [$500] Chats are not loading in the LHN with `Most Recent` mode[/+]on Apr 18, 2024
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.62-17 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:
[@hayata-suenaga] The PR that introduced the bug has been identified. Link to the PR:
[@hayata-suenaga] 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:
[@hayata-suenaga] 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:
[@hayata-suenaga] Determine if we should create a regression test for this bug.
[@hayata-suenaga] 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.
[@CortneyOfstad] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:
Activity
melvin-bot commentedon Apr 1, 2024
Triggered auto assignment to @CortneyOfstad (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.melvin-bot commentedon Apr 1, 2024
Triggered auto assignment to @hayata-suenaga (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.MelvinBot commentedon Apr 1, 2024
This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989
github-actions commentedon Apr 1, 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:
marcaaron commentedon Apr 1, 2024
@hayata-suenaga can you try to check logs for @iwiznia and see if anything is happening?
This might not need to be an App deploy blocker and could be a Web deploy issue.
Sounds like a backend issue. What do you think?
Looks like there's more context in this thread: https://expensify.slack.com/archives/C049HHMV9SM/p1711986719647329
hayata-suenaga commentedon Apr 1, 2024
Might be from
OpenApp.Checking this log right now
24 remaining items
[-][$500] Chats are not loading in the LHN with `Most Recent` mode[/-][+][HOLD for payment 2024-04-25] [$500] Chats are not loading in the LHN with `Most Recent` mode[/+]melvin-bot commentedon Apr 18, 2024
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Apr 18, 2024
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.62-17 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-04-25. 🎊
melvin-bot commentedon Apr 18, 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:
mvtglobally commentedon Apr 18, 2024
Issue not reproducible during KI retests. (First week)
hayata-suenaga commentedon Apr 18, 2024
The issue was fixed in this PR. I'm going to write a PM soon. Closing this issue