-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[HOLD for payment 2023-10-13] [$500] mWeb-Conversation-User A in offline typing message, User B is shown "user A is typing" #28063
Comments
Triggered auto assignment to @NicMendonca ( |
Bug0 Triage Checklist (Main S/O)
|
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open
|
Triggered auto assignment to @joelbettner ( |
ProposalPlease re-state the problem that we are trying to solve in this issue.The "user is typing" event is broadcasted by a user's client even if the client has force offline mode enabled. What is the root cause of that problem?Pusher sends socket events even if force offline mode is enabled. Lines 315 to 324 in 5aa7f6d
What changes do you think we should make in order to solve the problem?Solution 1 function sendEvent(channelName, eventName, payload) {
// Check to see if we are subscribed to this channel before sending the event. Sending client events over channels
// we are not subscribed too will throw errors and cause reconnection attempts. Subscriptions are not instant and
// can happen later than we expect.
if (!isSubscribed(channelName)) {
return;
}
+ if (shouldForceOffline) {
+ Log.info('[Pusher] Ignoring a send event because shouldForceOffline = true');
+ return;
+ }
// ... rest of the method
} Solution 2
What alternative solutions did you explore? (Optional)None. |
I don't think this is an hourly, since I believe this will only ever happen on staging (I THINK we always hide the TestToolMenu in production...I could be wrong). I don't think this was caused by the recent deploy. I think this has been happening ever since we introduced the Force Offline mode. @izarutskaya is this something that you just came across, or is this test something that happens at every deploy? @neil-marcellini @roryabraham it looks like you are the two fellas who have the most background in the Force Offline mode. Care to weigh in here? |
Correct, I agree this is not a deploy blocker, also I think @neil-marcellini knows about this problem from before, I believe I remember some slack thread about this specifically. |
No, we do not this test at every deploy. This was discovered during another test. Thank you |
Job added to Upwork: https://www.upwork.com/jobs/~01650cee09674fc251 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @ntdiary ( |
^ setting as external |
ProposalPlease re-state the problem that we are trying to solve in this issue. What is the root cause of that problem? What changes do you think we should make in order to solve the problem? Please see the attachments below, for knowing where to add the below code in ComposerWithSuggestions.js file.
On ComposerWithSuggestions.js#216, update the if condition like below
Video Recording |
❌ There was an error making the offer to @ntdiary for the Reviewer role. The BZ member will need to manually hire the contributor. cc @thienlnam |
❌ There was an error making the offer to @akinwale for the Contributor role. The BZ member will need to manually hire the contributor. cc @thienlnam |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.78-4 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 2023-10-13. 🎊 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.
For reference, here are some details about the assignees on this issue: As a reminder, here are the bonuses/penalties that should be applied for any External 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:
|
@akinwale @ntdiary bump on BZ check list ^^ Also can you both apply to the job please? https://www.upwork.com/jobs/~01650cee09674fc251 |
Applied. Thanks! I believe it's the C+ that's supposed to complete the BZ check list. Weird that my name is in there. 😅 |
I guess it's because you are already in C+ as well. 😄 |
Sent you both an offer! |
Accepted. Thanks! |
both paid, thank you! |
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:
User A in offline typing message, User B must not be shown "user A is typing" in conversation page.
Actual Result:
User A in offline typing message, User B is shown "user A is typing" in conversation page.
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: 1.3.73-0
Reproducible in staging?: Y
Reproducible in production?: No "Force offline" mode
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
Bug6211463_2user_shown_user_a_typing.mp4
Bug6211463_offline_android_user_a_typing_shown_to_userb.mp4
Bug6211463_1offline_mweb.mp4
Expensify/Expensify Issue URL:
Issue reported by: Applause-Internal Team
Slack conversation: @
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: