-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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 2022-08-11] [$250] Electron log file not working #9794
Comments
Triggered auto assignment to @MitchExpensify ( |
The latest log I have in my log file is:
So that makes me guess that electron-log was broken in the following release: https://github.com/Expensify/App/releases/tag/1.1.41-6 |
Interesting that release was the one that set up the 2-package structure. see the full diff here: 1.1.40-2...1.1.41-6 cc @kidroca |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @mananjadhav ( |
Current assignee @roryabraham is eligible for the Exported assigner, not assigning anyone new. |
@roryabraham when I worked on the "2-package" structure I needed to check logs, but couldn't find anything under I assumed I was probably doing something incorrectly because I could find no logs there But now that I saw this issue, it might be due to We should probably override that for Desktop main if we want |
@kidroca let me know if you want this assigned to you. Otherwise @MitchExpensify let's double this |
Yes, sounds good, I can post a small webpack config patch to preserve |
📣 @kidroca You have been assigned to this job by @roryabraham! |
@mananjadhav Going to unassign you on this one because it sounds like @kidroca's got this. The fix should be pretty easy to validate. |
I think I'll be ready with a PR tomorrow or the day after |
Cool, thanks @kidroca. Full-disclosure: I'm pretty swamped this week so it might take me a few days to get to the PR. I'll do my best to review it as soon as I can |
Doubled! Upwork job |
Thanks @MitchExpensify – I think since @kidroca is working on this he'll just bill us hourly. Feel free to correct me if I'm wrong @kidroca |
Yes, I'll add the work here under the hourly contract, it's more convenient (💲 Don't tempt me by doubling the price 💲) |
Thanks for the catch @roryabraham! Sounds good @kidroca :D |
It turned out console logs are not stripped from the minified I've added a bunch console statements I've searched a bit more and found the log file in: Line 2 in c5fb877
Here's how electron-log picks the log file location: https://github.com/megahertz/electron-log/blob/HEAD/docs/file.md#appname-string-deprecated
|
Yes! I've got them there
Nope, let's just update the documentation with the new location here and here and maybe add something to the README in the |
BTW I've found out some additional stuff that we can do
Any interest in any of these? |
Sure @kidroca, happy to review PRs for all of those things. Thanks! |
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.1.87-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 2022-08-11. 🎊 |
Thanks for you help with this @kidroca ! I see you've added it to your hourly contract so we're all good here |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Action Performed:
Run a
console.log
in the Electron application.Expected Result:
The log should be added to a log file for the app located at
~/Library/Logs/new.expensify/main.log
Actual Result:
The latest log in my
~/Library/Logs/new.expensify/main.log
file is from 4 months ago.Workaround:
n/a
Platform:
Where is this issue occurring?
Version Number: 1.1.82-3
Reproducible in staging?: yes
Reproducible in production?: yes
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: