Open AndreasPizsa opened 4 years ago
Thank you for the issue update. We'll look into this immediately and apologize for the inconvenience.
Additional info: I've had Code Time installed before for a while; could be that Code Time screwed up that file.
That is helpful to know, thank you. Investigating now and will provide more information soon.
We've identified a possible cause and will have a new version of music time and code time available within the day. One last question to confirm some of our understandings, do you think you may have had multiple Atom windows open during install?
We've updated code time and music time with the following versions.
code-time@v4.1.8 music-time@v2.0.7
The session.json file is no longer valid, as you mentioned, and will need to be recreated. Can you delete your ~/.software folder then upgrade? Thank you.
do you think you may have had multiple Atom windows open during install?
I’m not 100% sure, but that’s more than likely.
Can you delete your ~/.software folder then upgrade?
I fixed the malformed JSON instead; it‘s working now, thanks!
It just happened again.
❯ cat ~/.software/session.json
{"wctime":30,"currentDay":"2020-06-23"}"latestPayloadTimestampEndUtc":0}
something seems to keep messing up this file.
code-time 4.1.9 music-time 2.0.8
No exception this time. But neither code-time nor music-time would show up in the Command Palette.
We'll look into this today and let you know as soon as we can. Do you have any other editors using Code Time and Music Time besides Atom? Thank you.
We've updated atom music time and code time to handle read and writes for this type of use case. There may be time when both plugins are utilizing the session.json and corruption would occur. The logic around this will now look into a short lived cache before accessing the file for any info. It will also keep a valid session json in memory but will be replace when either plugin or multiple windows update the session.
code-time@v4.1.11 music-time@v2.0.10
Thank you.
Describe the bug A clear and concise description of what the bug is.
ISSUE TYPE
Steps to reproduce
Expected behavior A clear and concise description of what you expected to happen.
ACTUAL RESULTS
Screenshots If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Additional context Add any other context about the problem here.