-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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 PR #42892][$250] Text pasted from Slack won't send or disappears in NewDot. #39971
Comments
Triggered auto assignment to @slafortune ( |
Triggered auto assignment to @roryabraham ( |
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
|
@roryabraham been discussing here with @thienlnam that this is specific for Slack it seems so we should not have to hold deploy for this bug |
@m-natarajan can you pls paste the unformatted content of the slack message? initial suspicion is |
📣 @brkdavis! 📣
|
Also happens when trying to copy/paste from https://github.com/Expensify/App/blob/main/contributingGuides/HOW_TO_BECOME_A_CONTRIBUTOR_PLUS.md |
Job added to Upwork: https://www.upwork.com/jobs/~01892e3b8e5931a268 |
making this external |
Moved to Live Markdown project |
This issue has not been updated in over 15 days. @slafortune, @jayeshmangwani, @roryabraham, @kpadmanabhan eroding to Monthly issue. P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do! |
@MelvinBot this is blocked because of the PR that is on hold. @jayeshmangwani / @roryabraham : how should we proceed here? |
@kpadmanabhan We are still waiting for the other contributor to update their PR and get it ready for merging. Until then, we are blocked. |
Exactly. But it has been quite a long wait is my worry. |
@jayeshmangwani @kpadmanabhan , sorry, I'm confused. I've checked links but I'm unsure where we're at. Is it....
Is that right? |
@mallenexpensify in a sense that's correct. |
Yes, that's correct! I had opened the discussion a few days ago for this issue here https://expensify.slack.com/archives/C02NK2DQWUX/p1719300668647629 |
OK.. since @kpadmanabhan was hired and invested a non-immaterial amount of work, compensation should be do. |
@mallenexpensify Generally, we should have given 100% as the PR was almost in a mergeable state, but since the raised PR had one regression found during testing, I would say 50% compensation should be given. |
Thanks @jayeshmangwani . Does that sound good n' fair to you @kpadmanabhan ? |
@mallenexpensify though task was for completing the bug fix, I did a lot more than that following up on other bugs and PRs in the related area. However, I am fine with the suggestion from you and @jayeshmangwani . Sad that my changes couldn't hit production. Looking forward to that in next proposals. |
@kpadmanabhan if you want to provide links and details to the additional work, it's possible that could influence the compensation amount. We always appreciate contributors monitoring other issues/PRs and chiming in when it's helpful. |
@mallenexpensify tagged the wrong contributor 🙂 ; the message was meant for you, @kpadmanabhan. |
and, from CONTRIBUTING.md
@jayeshmangwani, was the regression found during testing before the code was merged? Also, @kpadmanabhan , thanks for the breakdown and context. |
@mallenexpensify : jayesh found it when everything looked good during final review. correct me if i am wrong @jayeshmangwani |
@mallenexpensify Yes, found when testing the PR. |
Since the regression was found before being merged, that would be normal testing. We don't have documentation stating there are penalties for that. Based on that, and @kpadmanabhan 's breakdown above, I think we shoudl compensate 100% here for both @kpadmanabhan and @jayeshmangwani. They were both hired/assigned and started work on the PR. |
Contributor: @kpadmanabhan paid $250 via Upwork Thanks! |
@slafortune @roryabraham Be sure to fill out the Contact List! |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Version Number: 1.4.61-5
Reproducible in staging?: y
Reproducible in production?: n
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: @mallenexpensify
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1712695994757859
Action Performed:
Scenario 1:
Scenario 2:
Expected Result:
Message is sent
Actual Result:
Scenario 1: Message stays in compose box and won't send. Cursor stays at the beginning of the message
Scenario 2: Only the > part of the message sends.
Workaround:
unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Recording.2959.mp4
2024-04-09_10-53-38.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: