Skip to content

[HOLD for payment 2024-04-05] HIGH: [Performance] Send less user is typing events #38714

Closed

Description

@iwiznia

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

Activity

  1. added
    InternalRequires API changes or must be handled by Expensify staff
    BugSomething is broken. Auto assigns a BugZero manager.
    on Mar 20, 2024
  2. self-assigned this
    on Mar 20, 2024
  3. melvin-bot commented on Mar 20, 2024

    @melvin-bot
  4. melvin-bot commented on Mar 20, 2024

    @melvin-bot

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

  5. melvin-bot commented on Mar 20, 2024

    @melvin-bot

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

  6. quinthar commented on Mar 21, 2024

    @quinthar
    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?

  7. iwiznia commented on Mar 21, 2024

    @iwiznia
    ContributorAuthor

    Yes, we are doing that here

  8. 8 remaining items

  9. 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[/+] on Mar 29, 2024
  10. melvin-bot commented on Mar 29, 2024

    @melvin-bot

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

  11. melvin-bot commented on Mar 29, 2024

    @melvin-bot

    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
  12. melvin-bot commented on Mar 29, 2024

    @melvin-bot

    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:
  13. melvin-bot commented on Apr 5, 2024

    @melvin-bot

    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
  14. iwiznia commented on Apr 10, 2024

    @iwiznia
    ContributorAuthor

    @muttmuure you handling this?

  15. muttmuure commented on Apr 10, 2024

    @muttmuure
    Contributor

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

  16. eVoloshchak commented on Apr 15, 2024

    @eVoloshchak
    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

  17. muttmuure commented on Apr 16, 2024

    @muttmuure
    Contributor

    Updated to $500 thanks!

  18. JmillsExpensify commented on Apr 18, 2024

    @JmillsExpensify
    Contributor

    $500 approved for @eVoloshchak

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.EngineeringInternalRequires API changes or must be handled by Expensify staffWeeklyKSv2

Type

No type

Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions