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
Room - LHN is empty after leaving public room anonymously #44800
Version Number: 9.0.4.0 Reproducible in staging?: y Reproducible in production?: n If this was caught during regression testing, add the test name, ID and link from TestRail: n/a Email or phone of affected tester (no customers): Logs:https://stackoverflow.com/c/expensify/questions/4856 Expensify/Expensify Issue URL: Issue reported by: Applause internal team Slack conversation:
Action Performed:
Log out of ND if logged in.
Navigate to a public room link.
Tap on the room header.
Tap Leave.
Expected Result:
LHN will not be blank after leaving public room anonymously.
Actual Result:
LHN is blank after leaving public room anonymously.
Workaround:
unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
👋 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.
@hayata-suenaga FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors
Seems like the bug will be fixed when the leave button is hidden in the linked PR. Removing the deploy blocker and and closing this issue as the issue is tracked in this issue.
@RachCHopkins, this issue is about a bug that is categorized as a "deploy blocker". These are bugs that are found in the staging New Expensify but those that don't exist on production. This means that the bug was introduced in the code that was recently written. We have to fix these bugs before we deploy the new code to production.
Usually, an internal engineer is assigned to these issues and they handle the issue.
As a bug zero, you can do:
tag internal engineer who was assigned to a deploy blocker issue on New Expensify if they haven't commented on the issue for a while
If there is some contributor who identify themselves as the one introduced the bug, you can assign them so that they can fix the bug (usually, the assigned internal engineer does this, but if they haven't commented on the issue, you can also do that)
In this particular issue, the fix has already been worked on, so I decided to close this issue.
Activity
melvin-bot commentedon Jul 4, 2024
Triggered auto assignment to @RachCHopkins (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.melvin-bot commentedon Jul 4, 2024
Triggered auto assignment to @hayata-suenaga (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.github-actions commentedon Jul 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:
m-natarajan commentedon Jul 4, 2024
@hayata-suenaga FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors
m-natarajan commentedon Jul 4, 2024
We think that this bug might be related to #vip-vsb
situchan commentedon Jul 4, 2024
FYI: we're hiding Leave button in #44560
RachCHopkins commentedon Jul 4, 2024
@hayata-suenaga I'm new to the BugZero team, do you need me to do anything on this?
hayata-suenaga commentedon Jul 4, 2024
Seems like the bug will be fixed when the leave button is hidden in the linked PR. Removing the deploy blocker and and closing this issue as the issue is tracked in this issue.
hayata-suenaga commentedon Jul 4, 2024
@RachCHopkins, this issue is about a bug that is categorized as a "deploy blocker". These are bugs that are found in the staging New Expensify but those that don't exist on production. This means that the bug was introduced in the code that was recently written. We have to fix these bugs before we deploy the new code to production.
Usually, an internal engineer is assigned to these issues and they handle the issue.
As a bug zero, you can do:
In this particular issue, the fix has already been worked on, so I decided to close this issue.