Skip to content
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

Temperature logs from sensors are being duplicated and / or skipped in CCA #318

Open
adamdewey opened this issue Oct 30, 2024 · 0 comments
Labels
Bug Something is borken Severity: High Bugs breaking core functionality or with no/unacceptable workaround. High impact. Next patch release

Comments

@adamdewey
Copy link
Collaborator

adamdewey commented Oct 30, 2024

Describe the bug

CCA is skipping some sensor logs and duplicating others when extracting logs from the sensors.

This is a major issue for the integrity of the solution.

Here is a direct comparison between the sensor and CCA logs:

image

Sometimes the logs can get quite out of sync:

image

To Reproduce
Steps to reproduce the behavior:

  1. Run a sensor for a while
  2. Extract sensor logs using sensor app
  3. Extract CCA logs
  4. Compare

Expected behavior
Sensor and CCA logs should always match exactly.

Smartphone (please complete the following information):

  • Device: Samsung Galaxy Tab A7
  • OS: Android 14
  • CCA Version 0.5.7

Additional context

Logs for the above screenshots can be found here: https://drive.google.com/drive/folders/1tTxh8guAxDNrGB6pZRH2pLkNIwNUC5Al

Also noticed by @louisaw123

image

image

Export of Sensor logs:
C1671B0D_1730231726948_log.csv

Export for CCA logs:
C1671B0D64C9-30-10-2024-09-33-53.csv

Debug logs for CCA for above:
com.msupplycoldchain-2024-10-29.17.log
com.msupplycoldchain-latest.3.log
com.msupplycoldchain-2024-10-29.14.log
com.msupplycoldchain-2024-10-29.15.log
com.msupplycoldchain-2024-10-29.16.log

The suggestion from Andrei is:

  1. Create a new special build with backdate option on the app and then re-pull the logs from the last 7 days for that particular sensor to see if it can be replicated.
  2. If it can, this will be easier to fix
  3. Make a build to have debug logs permanently turned on (there has been issues of it randomly turning off so have not been able to use these logs whenever there is a spike)

This is likely related to #270 , #288 , #289

@adamdewey adamdewey added Bug Something is borken Severity: High Bugs breaking core functionality or with no/unacceptable workaround. High impact. Next patch release labels Oct 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something is borken Severity: High Bugs breaking core functionality or with no/unacceptable workaround. High impact. Next patch release
Projects
None yet
Development

No branches or pull requests

1 participant