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
[HOLD for payment 2024-04-05] HIGH: [Performance] Send less user is typing events #38714
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
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?
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
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:
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:
Activity
melvin-bot commentedon Mar 20, 2024
Job added to Upwork: https://www.upwork.com/jobs/~014119b0bde30a6fc4
melvin-bot commentedon Mar 20, 2024
Triggered auto assignment to Contributor Plus for review of internal employee PR - @eVoloshchak (
Internal)melvin-bot commentedon Mar 20, 2024
Triggered auto assignment to @muttmuure (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.quinthar commentedon Mar 21, 2024
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 commentedon Mar 21, 2024
Yes, we are doing that here
8 remaining items
[-]HIGH: [Performance] Send less user is typing events[/-][+][HOLD for payment 2024-04-05] HIGH: [Performance] Send less user is typing events[/+]melvin-bot commentedon Mar 29, 2024
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon 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:
melvin-bot commentedon 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:
melvin-bot commentedon Apr 5, 2024
Payment Summary
Upwork Job
BugZero Checklist (@muttmuure)
iwiznia commentedon Apr 10, 2024
@muttmuure you handling this?
muttmuure commentedon Apr 10, 2024
@eVoloshchak ready for you to submit a request in New Expensify
eVoloshchak commentedon Apr 15, 2024
@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 commentedon Apr 16, 2024
Updated to $500 thanks!
JmillsExpensify commentedon Apr 18, 2024
$500 approved for @eVoloshchak