Closed m-natarajan closed 3 days ago
Triggered auto assignment to @mallenexpensify (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.
Triggered auto assignment to @techievivek (AutoAssignerNewDotQuality
)
This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989
Job added to Upwork: https://www.upwork.com/jobs/~019968f6b9ea37c469
Triggered auto assignment to Contributor-plus team member for initial proposal review - @allroundexperts (External
)
Nipping this one in the bud a bit cuz I have a strong feeling it's going to be hard to reproduce. Added to OP
Deliverable
The job is open to proposals. If someone is able to provide reliable reproduction steps, compensation will be $125.
@quinthar also reported this happening here.
This also happens when a workspace member leaves a workspace. Their workspace chat becomes permanently unread. So:
But @kadiealexander reported that she didn't leave the workspace and instead BulkUnsharePolicies.php was used which causes sharePolicy. But I believe leavePolicy also eventually calls sharePolicy so there might be something related there? I don't think I'll be able to take over assignment @techievivek because I have a lot on my plate currently and I just got assigned a new NewDot reliability issue but I'll stay subscribed so that I might be able to help out since I've been doing some work with deletePolicy which is kind of related with archived reports.
I'm also not sure why I'm able to reliably produce this when leaving a workspace but this only occurred for @kadiealexander's workspace chat and not the others that were removed using BulkUnsharePolicies.php. Also cc @MonilBhavsar and @marcaaron if you guys have any ideas.
@danielrvidal, @mallenexpensify, @allroundexperts, @techievivek Whoops! This issue is 2 days overdue. Let's get this updated quick!
I will try to reproduce this based on Srikar's comment here https://github.com/Expensify/App/issues/44108#issuecomment-2186903100
Not overdue, still needs to reproduce this before we can move forward.
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸
@danielrvidal, @mallenexpensify, @allroundexperts, @techievivek Whoops! This issue is 2 days overdue. Let's get this updated quick!
This is still in my account so let me know if anyone needs to hop on a screen share with me to help diagnose. I've also logged in and out since reporting it so it seems persistent.
Main tracking issue here: https://github.com/Expensify/App/issues/44683
@danielrvidal, @mallenexpensify, @allroundexperts, @techievivek 6 days overdue. This is scarier than being forced to listen to Vogon poetry!
I was unable to reproduce this issue after several attempts. Let me ask Applause to try reproducing it based on the steps mentioned here: https://github.com/Expensify/App/issues/44108#issuecomment-2186903100.
@danielrvidal @mallenexpensify @allroundexperts @techievivek this issue was created 2 weeks ago. Are we close to approving a proposal? If not, what's blocking us from getting this issue assigned? Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸
@danielrvidal @mallenexpensify I am unable to reproduce this on my end, and the QA team was also unsuccessful in reproducing the issue https://github.com/Expensify/App/issues/44108#issuecomment-2208838706. What is the best way to move forward here?
Raised price for reproduction steps to $250 and posted in #expensify-open-source https://expensify.slack.com/archives/C01GTK53T8Q/p1720484027137579
@hurali97 seemed to have reproduced it here. Do you think you could lay out the reproduction steps? I think @techievivek can also assign you to this issue if you want to work on this.
Yeah, I can work on it, just waiting for clear reproduction steps.
Asked Ali to take a look from CS. It's possible that this is a dupe
@srikarparsi We have a PR out here which fixes the issue where user was unable to mark a chat as read.
I just have one question, reading through the conversation it looks like there are two separate issues:
The linked PR fixes only the first issue but not the second one as it is addressing this issue specifically.
Let us know if we are on the same page here. If we are, then @rinej maybe able to work on the second issue from Monday.
@techievivek I think the question is for you too
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸
@hurali97
Some chats shouldn't appear in LHN but they are appearing anyway
The second point you've listed is the problem here. There are some chats that appeared unexpectedly. Srikar provided these steps to reproduce the bug, but I wasn't able to reproduce the issue following those steps.
Went down a 🐰🕳 trying to test (and cleaning up LHN in my test account) and wasn't able to reproduce.
I still have the chat with Kadie in my LHN if it helps. Let me know if anyone wants me to do anything to diagnose.
Here is my Onyx State. onyx-state.txt
I think this is a dupe of https://github.com/Expensify/App/issues/44693 so I'm going to close this. But please reopen if I'm mistaken.
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Version Number: Reproducible in staging?: needs reproduction Reproducible in production?: needs reproduction 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 Expensify/Expensify Issue URL: Issue reported by: @danielvidal Slack conversation: https://expensify.slack.com/archives/C05LX9D6E07/p1718638249114319
Deliverable
The job is open to proposals. If someone is able to provide reliable reproduction steps, compensation will be $125.
Action Performed:
Expected Result:
These very old expenses (archived chats)from months ago shouldn't appear in the LHN
Actual Result:
These very old expenses from months ago that re-appeared on the LHN out of nowhere
Workaround:
unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
View all open jobs on GitHub
Upwork Automation - Do Not Edit