Skip to content
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 2024-04-05] HIGH: [Performance] Send less user is typing events #38714

Closed
iwiznia opened this issue Mar 20, 2024 · 15 comments
Closed
Assignees
Labels
Awaiting Payment Auto-added when associated PR is deployed to production Bug Something is broken. Auto assigns a BugZero manager. Engineering Internal Requires API changes or must be handled by Expensify staff Weekly KSv2

Comments

@iwiznia
Copy link
Contributor

iwiznia commented Mar 20, 2024

Reported https://expensify.slack.com/archives/C049HHMV9SM/p1710969968937119

We seem to be sending the UserIsTyping message for every keystroke. This means if I'm in a DM with you, and if I'm typing quickly, I am sending you a continuous stream of messages via Pusher -- which is hammering your client's network stack, Onyx database, and main thread. I think we should ideally:

  • Send the first message the moment you start typing
  • Send a new message every second, so long as you are still typing
Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~014119b0bde30a6fc4
  • Upwork Job ID: 1770576924726861824
  • Last Price Increase: 2024-03-20
Issue OwnerCurrent Issue Owner: @muttmuure
@iwiznia iwiznia added Engineering Daily KSv2 Internal Requires API changes or must be handled by Expensify staff Bug Something is broken. Auto assigns a BugZero manager. labels Mar 20, 2024
@iwiznia iwiznia self-assigned this Mar 20, 2024
Copy link

melvin-bot bot commented Mar 20, 2024

Job added to Upwork: https://www.upwork.com/jobs/~014119b0bde30a6fc4

Copy link

melvin-bot bot commented Mar 20, 2024

Triggered auto assignment to Contributor Plus for review of internal employee PR - @eVoloshchak (Internal)

Copy link

melvin-bot bot commented Mar 20, 2024

Triggered auto assignment to @muttmuure (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

@quinthar
Copy link
Contributor

Incidentally, I think we are sending typing indicators even after we leave the room. Do we explicitly leave the channel of past rooms when leaving the room, or not?

@iwiznia
Copy link
Contributor Author

iwiznia commented Mar 21, 2024

Yes, we are doing that here

@quinthar quinthar changed the title Send less user is typing events HIGH: Send less user is typing events Mar 25, 2024
@quinthar
Copy link
Contributor

Actually it looks like we don't reliably unsubscribe from isTyping events -- it could be that we unsubscribe when switching to another room, but we might not unsubscribe when switching to a non-room page (eg, Settings)

@quinthar quinthar changed the title HIGH: Send less user is typing events HIGH: [Performance] Send less user is typing events Mar 25, 2024
@melvin-bot melvin-bot bot added Weekly KSv2 Awaiting Payment Auto-added when associated PR is deployed to production and removed Weekly KSv2 labels Mar 29, 2024
@melvin-bot melvin-bot bot changed the title HIGH: [Performance] Send less user is typing events [HOLD for payment 2024-04-05] HIGH: [Performance] Send less user is typing events Mar 29, 2024
@melvin-bot melvin-bot bot removed the Reviewing Has a PR in review label Mar 29, 2024
Copy link

melvin-bot bot commented Mar 29, 2024

Reviewing label has been removed, please complete the "BugZero Checklist".

Copy link

melvin-bot bot commented Mar 29, 2024

The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.57-5 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-05. 🎊

For reference, here are some details about the assignees on this issue:

  • @eVoloshchak requires payment through NewDot Manual Requests

Copy link

melvin-bot bot commented Mar 29, 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:

  • [@eVoloshchak] The PR that introduced the bug has been identified. Link to the PR:
  • [@eVoloshchak] 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:
  • [@eVoloshchak] 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:
  • [@eVoloshchak] Determine if we should create a regression test for this bug.
  • [@eVoloshchak] 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.
  • [@muttmuure] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:

Copy link

melvin-bot bot commented Apr 5, 2024

Payment Summary

Upwork Job

BugZero Checklist (@muttmuure)

  • I have verified the correct assignees and roles are listed above and updated the neccesary manual offers
  • I have verified that there are no duplicate or incorrect contracts on Upwork for this job (https://www.upwork.com/ab/applicants/1770576924726861824/hired)
  • I have paid out the Upwork contracts or cancelled the ones that are incorrect
  • I have verified the payment summary above is correct

@melvin-bot melvin-bot bot added the Overdue label Apr 8, 2024
@iwiznia
Copy link
Contributor Author

iwiznia commented Apr 10, 2024

@muttmuure you handling this?

@muttmuure
Copy link
Contributor

@eVoloshchak ready for you to submit a request in New Expensify

@melvin-bot melvin-bot bot removed the Overdue label Apr 10, 2024
@github-project-automation github-project-automation bot moved this from HIGH to CRITICAL in [#whatsnext] #vip-vsb Apr 10, 2024
@eVoloshchak
Copy link
Contributor

@muttmuure, not sure if I'm missing something, shouldn't this be $500 since this is
a) HIGH
b) was created before April 5th?

According to https://expensify.slack.com/archives/C02NK2DQWUX/p1712250884549319

@muttmuure
Copy link
Contributor

Updated to $500 thanks!

@JmillsExpensify
Copy link

$500 approved for @eVoloshchak

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Awaiting Payment Auto-added when associated PR is deployed to production Bug Something is broken. Auto assigns a BugZero manager. Engineering Internal Requires API changes or must be handled by Expensify staff Weekly KSv2
Projects
No open projects
Status: CRITICAL
Development

No branches or pull requests

5 participants