-
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 2024-06-28] [$250] Don't show "We might have a problem. Check out " #43536
Comments
Job added to Upwork: https://www.upwork.com/jobs/~01557bbba5e2f56091 |
Triggered auto assignment to @trjExpensify ( |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @mananjadhav ( |
Essentially, we need to revert this PR without altering future changes made to networking like this PR. @tienifr @DylanDylann @cubuspl42 if you could take a look at this, that would be great since you worked on the original PR to add in this functionality. |
@srikarparsi Sure, I can work on this. Feel free to assign me and @DylanDylann (who reviewed the PR) to this issue 🙏 |
@tienifr Please ping me when the PR is ready |
Cool thanks, @mananjadhav reassigning to @DylanDylann since he reviewed the initial PR. |
❌ There was an error making the offer to @DylanDylann for the Contributor role. The BZ member will need to manually hire the contributor. |
❌ There was an error making the offer to @DylanDylann for the Reviewer role. The BZ member will need to manually hire the contributor. |
❌ There was an error making the offer to @tienifr for the Contributor role. The BZ member will need to manually hire the contributor. |
❌ There was an error making the offer to @DylanDylann for the Contributor role. The BZ member will need to manually hire the contributor. |
❌ There was an error making the offer to @DylanDylann for the Reviewer role. The BZ member will need to manually hire the contributor. |
❌ There was an error making the offer to @tienifr for the Contributor role. The BZ member will need to manually hire the contributor. |
Not sure why the automation is failing. @tienifr do you think you can give an ETA for when the PR will be ready? |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.0-9 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-06-28. 🎊 For reference, here are some details about the assignees on 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:
|
Payment Summary
BugZero Checklist (@trjExpensify)
|
👋 checklist time! |
Bump on the checklist, @DylanDylann! |
This is a reverted PR. We don't need the checklist. |
This is a reverted PR. We don't need the checklist. cc @srikarparsi |
Oh cool, so no payment is due as it was a regression revert? |
@trjExpensify The payment should be handled here because this is not a regression. we intended to implement this feature previously but it seems this is unnecessary so the internal team created this issue as a task to revert the previous PR cc @srikarparsi |
Alright cool, gotcha. Payment summary as follows:
I checked in TestRail, and there isn't a regression test for this scenario of the site being down to delete, so we're good there. Offers sent! |
Thanks, I've requested on NewDot |
@trjExpensify I accepted the Upwork offer 🙏 |
Paid, @DylanDylann. Closing! |
$250 approved for @tienifr |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Version Number:
Reproducible in staging?:
Reproducible in production?:
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:
**Slack conversation:https://expensify.slack.com/archives/C05LX9D6E07/p1717834594513299
Action Performed:
Expected Result:
We should only ever see the 'You appear to be offline.' message
Actual Result:
Sometimes, we see the 'We might have a problem. Check out status.expensify.com.' message
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?
Screenshots/Videos
Add any screenshot/video evidence
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @trjExpensifyThe text was updated successfully, but these errors were encountered: