-
Notifications
You must be signed in to change notification settings - Fork 161
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
fix: cleanup log output #345
base: dev
Are you sure you want to change the base?
Conversation
@marionbarker would you mind running your scripts to see the diff in log size? Thanks! |
I applied this patch about a day and a half ago to latest Trio - dev (at the time).
From this comment, the prior art was about 3.3k lines/hour, 288k characters/hour. The graphic is the NS site used with this test phone. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Giving my approval based on the fact it works for providing record of Omnipod messages.
Someone else more familiar with these logs should examine the result for other content.
I recommend a Squash & Merge. My history is a lot of trial and error. |
I will have a look at the logs tonight |
@mkellerman The content pf the logging is totally readable and fine with me. I suggest that you give the green marked part another context e.g. like oref, but not middleware. |
@mountrcg, i'm unable to reproduce the autosens logs like you. Mine get trimmed correctly. Maybe something to do with Timezone/Language formatting? Regarding 'Middleware', this is autogenerated by how we call the JavaScriptWorker... I didn't name these individually. |
@marionbarker @mountrcg posted a new fix that might resolve the issue. |
Summary:Log files and time stamps are provided for someone else to review. Configuration:
Medtronic Log:
Omnipod DASH Log:
The Omnipod messages are not affected by the logging changes, the parser still works for code both with and without PR 346 applied. |
Thanks @marionbarker ! I dont get any of those u(xxxx) in my logs, so it's really hard to debug this one on my own. But i did fix the regex to include this pattern. it should be fixed now. |
Downloaded new patch and built to
Both phones are also running changes from PR 353. Below are the log files (so since midnight local on 2024-07-19) acquired around 05:50 am MDT: Pod:
|
MDT logs:
DASH logs:
|
I think this does the expected behaviour! Thanks @marionbarker for all the testing! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can attest that the Omnipod messages come through fine after this update and the parser interprets them.
Someone else needs to agree the logs are otherwise OK.
Both MDT and DASH logs are posted in the comments.
Fix for #272
prepare/autosens.js
,Middleware
)Reference to previous PR #331
New output: