- Progress reporting queue is cleared on command completion to prevent stale progress from being sent when pileup occurs [544](https://github.com/opsani/servox/pull/544) - Memory parsing logic treats unitless decimal strings as GiB (aligns with existing float parsing) per the servo protocol [546](https://github.com/opsani/servox/pull/546)
2.2.6
Changed
- A unique identifier for each servo deployment is now supported in configuration and sent with every request to the backend - A unique identifier for each command received from the backend is now retrieved from the response to the WHATS_NEXT request and included on all servo requests for the given command (progress and completion)
2.2.5
Changed
- 404 no longer considered fatal status code - Checks now support exponential backoff - Checks delay configuration now defaults to exponential backoff - Diagnostics reporting disabled by default - Connector discovery now done with importlib.metadata.entry_points instead of deprecated pkg_resources.iter_entry_points
Fixed
- Measurement delay (wait driver only)
2.2.4
Changed
- Default interval of progress updates changed from 5 seconds to 60 - Updated API path used for servo endpoint of optimize solution
2.2.3
Changed
- Update ID of appD config to use optimizerID instead of workloadID