Releases: ocariot/data-sync-agent
Releases · ocariot/data-sync-agent
v1.6.1
v1.6.0
Improvements
- Replacement of the complete image of the node by the alpine, which greatly reduces the size of the generated image;
- Update of the dependencies used in the application;
- Removal of
last_sync
from the routePOST /v1/users/{child_id}/fitbit/auth
.
v1.5.9
Adjustments:
- Updated dependencies;
- Updated
Dockerfile
; - Changing mocha configuration file (mocha.opts for
.mocharc.yml
).
v1.5.8
Bug Fixes:
- Fixed process to save synchronized Fitbit resources;
- Fixed mapping of exceptions and errors;
- General adjustments and code improvements.
v1.5.7
Bug fix
- Fixed the error that did not synchronize the Sleep data previous to the current date after notification from Fitbit.
v1.5.6
Bug Fixes:
- Fixed the error that did not exclude all user resources when receiving the UserDeleteEvent event;
- Corrected the error that did not synchronize the physical activities and the sleep records of the current day;
- Fixed the error in mapping the heart rate zones;
- Fixed the error caused by the transformation of dates and time in UTC. Now, the information is not converted, however, the .Z is inserted at the end of the timestamp, so that the iot-tracking service does not convert to the local time zone, it is up to customers to convert when necessary;
- Fixed the error that caused the end_time to be less than the start_date;
- Fixed token revocation process to always return 204, except in cases of non-existent authentication data, invalid user ID or internal error.
v1.5.5
Bug Fixes:
- Fixed bug not syncing physical activity of current day;
- Fixed issue that caused mongo client to issue warnings regarding
reconnectTries
andreconnectInterval
options.
Adjustments
- Updated versions of some dependencies;
- Refactorings in the
UserAuthDataService
class so that functions return a promise correctly.
v1.5.4
Bug Fixes:
- Fixed Fitbit sync error:
- When saving a synchronized resource was being saved with Fitbit id and not ocariot platform.
- Increased from 6 months to 12 months initial synchronization.
v1.5.3
Bug Fixes:
- Fixed bug not publishing last Fitbit sync on message bus when user already existed.
v1.5.2
Bug Fixes:
Bug fixed in /v1/users/{child_id}/fitbit/auth
- The scope of the token is now validated before being saved.