Tconnectsync

Latest version: v0.9.7

Safety actively analyzes 638437 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 2 of 4

0.8.7

What's Changed
* Fix "Unknown therapy event type: Basal" due to new event types being added to Tandem APIs
* Moved remaining logger.warn() statements to logger.warning() by jyaw in https://github.com/jwoglom/tconnectsync/pull/58


**Full Changelog**: https://github.com/jwoglom/tconnectsync/compare/v0.8.5...v0.8.7

0.8.5

This release includes a bugfix which, in certain situations, would result in unnecessary repeated data uploads to Nightscout. If your Nightscout instance stores event timestamps in isoformat with a space between the date and the time instead of a `T` (e.g. `2022-10-01 22:27:10-04:00` instead of `2022-10-01T22:27:10-04:00`), then tconnectsync would upload all of the past day's basal and bolus information rather than only the delta between the most recently uploaded data from tconnectsync. As far as I can tell, this caused minimal impact as these events contained identical data at identical timestamps, and either Nightscout or Mongo deduplicates the data and continues to function properly.

Per https://github.com/jwoglom/tconnectsync/issues/47, some users' Nightscout instances do indeed have proper isoformat timestamps, so tconnectsync now checks Nightscout for both formats of timestamps before returning that no previous bolus/basal objects exist in NS.

**Full Changelog**: https://github.com/jwoglom/tconnectsync/compare/v0.8.4...v0.8.5

0.8.3

What's Changed
* Update README.md by t1diotac in https://github.com/jwoglom/tconnectsync/pull/50
* Replace hand-rolled date format with isoformat(). by rstutsman in https://github.com/jwoglom/tconnectsync/pull/51
* Handle unknown therapy event error when running ciq_therapy_event.py by jyaw in https://github.com/jwoglom/tconnectsync/pull/54
* Handle unknown therapy event error when running ciq_therapy_event.py by jyaw in https://github.com/jwoglom/tconnectsync/pull/53
* fix unknown therapy event error in ciq_therapy_event.py by jyaw in https://github.com/jwoglom/tconnectsync/pull/55

New Contributors
* t1diotac made their first contribution in https://github.com/jwoglom/tconnectsync/pull/50
* rstutsman made their first contribution in https://github.com/jwoglom/tconnectsync/pull/51
* jyaw made their first contribution in https://github.com/jwoglom/tconnectsync/pull/54

Thanks for your help!

**Full Changelog**: https://github.com/jwoglom/tconnectsync/compare/v0.8.2...v0.8.3

0.8.2

* Fixes to --check-login (46)
* Adds timeout to WS2 API endpoints

**Full Changelog**: https://github.com/jwoglom/tconnectsync/compare/v0.8.1...v0.8.2

0.8.1

* Removes use of the WS2 therapytimeline csv endpoint which was causing major synchronization problems due to unreliability (43)

**Full Changelog**: https://github.com/jwoglom/tconnectsync/compare/v0.7.2...v0.8.1

0.7.2

* Support HTTP/HTTPS/SOCKS proxies
* Drop Python 3.6 support (`requests` no longer supports 3.6)
* Tandem HTTP 403 workarounds

**Full Changelog**: https://github.com/jwoglom/tconnectsync/compare/v0.7.1...v0.7.2

Page 2 of 4

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.