-
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 for payment 2024-06-13] MEDIUM: [$250] Add logging around offline state to help diagnose bugs #40250
Comments
Triggered auto assignment to @sonialiap ( |
This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989 |
@sonialiap Whoops! This issue is 2 days overdue. Let's get this updated quick! |
I can reproduce, but not consistently. Sometimes when I open ND the "you're offline" message appears and then usually clears within 30 seconds. If I open ND, close, and immediately open a new tab with ND the message doesn't appear. It seems to require some time between opening ND in a new tab for it to show as offline |
Job added to Upwork: https://www.upwork.com/jobs/~016051a56c40abfc4a |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @Santhosh-Sellavel ( |
ProposalPlease re-state the problem that we are trying to solve in this issue.Nothing useful in the logs to debug online/offline issues What is the root cause of that problem?We don't have such logs. What changes do you think we should make in order to solve the problem?There're 3 places we're setting offline status via
We should log the full
We should log the full
We can logs the logic we use to determine offline status Those are the core places we need the logs, the specifics of the log content/params can be adjusted in the PR phase. What alternative solutions did you explore? (Optional)Currently we have only true/false network status, if later we decide to have enum/number/string network statuses, then we need to log that value in the same way. |
@sonialiap, @Santhosh-Sellavel Whoops! This issue is 2 days overdue. Let's get this updated quick! |
What's the next step here, and the ETA? |
@sonialiap @Santhosh-Sellavel this issue was created 2 weeks ago. Are we close to approving a proposal? If not, what's blocking us from getting this issue assigned? Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks! |
@nkdengineer's proposal LGTM! C+ Reviewed |
This issue has not been updated in over 15 days. @sonialiap, @Santhosh-Sellavel, @hayata-suenaga, @nkdengineer 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! |
The PR has been merged |
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.79-11 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-13. 🎊 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:
|
This issue not a bug fix. It's about adding a logging
N/A
N/A |
Payment summary Please complete the two steps on the checklist |
@nkdengineer please accept the offer so that I can issue payment |
@sonialiap Could you help to add the |
@sonialiap, just as a note, the PR causes a regression although I'm not familiar with the policy on how regressions affect the bounty amount 🤔 |
Thanks for the flag, @hayata-suenaga. In the case of regression the fee is reduced by 50% (source) I think @nkdengineer 's request is reasonable because this issue was labeled as High April 16, the proposal was posted on April 23 and PR submitted after that. The issue was changed to Medium on May 12. Since the work was done while the issue was labeled as High, I think it's reasonable to update the price to $500. With the regression the price falls to $250 Payment summary remains the same
|
@sonialiap Thank you, I accepted the sent offer 🙇 |
Since this is update is for improving logging, I don't think we need a regression test. Closing |
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: Needs reproduction
Reproducible in staging?: N/A
Reproducible in production?: N/A
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers): @quinthar
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @quinthar
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1712886605520589
Action Performed:
Expected Result:
200 OK
API request should not be showinAdd something to the logs that will help diagnose this
Actual Result:
200 OK
API request appearsI don't see anything useful in the logs. Can we maybe improve the logging around whatever code we use to determine if we're online to output its logic so we can diagnose and fix it.
Workaround:
unknown
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: @sonialiapThe text was updated successfully, but these errors were encountered: